Epic: whole-migration harness: data, job streams, interfaces, performance, security, cutover

Abierto
  • ¿Algo no está bien?
#4,514 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
20/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Área
backend

Línea de trabajo

Start by reading this epic and the related issues #3803, #4493, #4508, and #4050 to understand the existing scan and coverage work. The issue asks for each migration area to be filed as its own issue when work starts; there is no specific file or test to begin with. Done means the separate work is scoped and its evidence can report into the #4493 coverage page.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement epic legacy-modernization testing

Why. Program-logic equivalence is only part of a migration. Each part below fits the same scan, generate or capture, compare, evidence, ratchet pattern, and should report into the #4493 coverage page.

Parts (suggested order):

  1. Data migration (VSAM, EBCDIC): convert each dataset, then round-trip it and compare byte for byte. Also reconcile counts, check key integrity, check EBCDIC/packed-decimal conversion field by field, and generate edge records (high-values, low-values, bad signs). Reuses the scan's layouts.
  2. JCL job streams: #4508.
  3. Interface contracts: inventory every file, queue (MQ), CICS link, DB2 table and transfer at the estate boundary, then record or generate traffic at each boundary and compare old versus new.
  4. The answer key on z/OS: #4050.
  5. Performance budgets: the same workloads old versus new (throughput, latency, the batch window), measured against a z/OS baseline (SMF). Budgets and regression gates, not byte equality.
  6. Security (RACF): extract transaction/dataset access per program, map RACF profiles to the new model, and test the same allow/deny decisions.
  7. Cutover by parallel run: shadow-mode production traffic through both systems with live comparison. The go/no-go stays human, fed by the evidence.

File each part as its own issue when it starts. Related: #3803, #4493.

Lenguaje dominante
Python
Estrellas
57
Forks
11
Merge medio
1 h 35 min
PR fusionados (30 d)
975

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de squid-protocol/gitgalaxy

Todos los issues de squid-protocol/gitgalaxy

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.