Migrate all repos into monorepo context folders
Bahn: aisupport, Analyse-O2C-C2S, awesome-bahn-mcp-servers, beam-mcp,
Confluence_Bot, db-planet-mcp-server, O2C-Harness, project-audit,
Projekt-KIQ-HP, teamlandkarte-mcp
Dhive: Jury-Voting
Privat: CV, NoteGraph (NOTE: NoteGraph needs complete redo after consolidation)
Shared: AI-Orchestrator, OrgMyLife, power_skills_and_more
Shared/references: symphony (read-only)
Bahn repos remain available as independent remotes - this monorepo
pulls them in via subtree, the originals are untouched.
This commit is contained in:
@@ -0,0 +1,524 @@
|
||||
# Technische Roadmap 2026
|
||||
|
||||
> Confluence Page ID: 578171282
|
||||
> Version: 10
|
||||
> Pfad: /pathOS/Roadmap Bestellsystem/Technische Roadmap 2026
|
||||
> Labels:
|
||||
|
||||
---
|
||||
|
||||
## Technische Roadmap â pathOS (Bestellsystem Zugfahrt)
|
||||
|
||||
Stand: 20.04.2026
|
||||
## Legende
|
||||
|
||||
| |
|
||||
Symbol |
|
||||
Bedeutung
|
||||
| |
|
||||
🔴 |
|
||||
MUSS UKA/GELV (Voraussetzungen UKA & GELV sowie notwendige Betriebsstabilisierung)
|
||||
| |
|
||||
🟡 |
|
||||
MUSS 2026 (Upgrades, Richtlinien, Security, Aufwandsreduktion)
|
||||
| |
|
||||
🟢 |
|
||||
SOLL
|
||||
| |
|
||||
âï¸ |
|
||||
In Arbeit (Implementation / Validierung)
|
||||
| |
|
||||
📋 |
|
||||
Zu erledigen (Funnel / Analysis)
|
||||
## 1. Infrastruktur & Plattform
|
||||
|
||||
| |
|
||||
# |
|
||||
Thema |
|
||||
Ticket |
|
||||
Status |
|
||||
Prio |
|
||||
PI
|
||||
| |
|
||||
1.1 |
|
||||
Umstellung auf neuen Schnitt von Kubernetes-Clustern & -Namespaces |
|
||||
O2CBS-1049 |
|
||||
âï¸ Implementation |
|
||||
🔴 |
|
||||
PI 40
|
||||
| |
|
||||
1.2 |
|
||||
Anbindung an Netcool (Betriebsüberwachung) |
|
||||
O2CBS-677 |
|
||||
📋 Funnel |
|
||||
🔴 |
|
||||
PI 40/PI 41
|
||||
| |
|
||||
1.3 |
|
||||
Laufzeit-Artefakte aus ECR statt Artifactory (SAT/ABN/PROD) |
|
||||
O2CBS-736 |
|
||||
📋 Funnel |
|
||||
🔴 |
|
||||
PI 41
|
||||
| |
|
||||
1.4 |
|
||||
Deployment nur noch aus einem Bestellsystem-Projekt möglich machen |
|
||||
â |
|
||||
â |
|
||||
🟡 |
|
||||
PI 41
|
||||
| |
|
||||
1.5 |
|
||||
Umstellung auf Unprivileged Container |
|
||||
O2CBS-1070 |
|
||||
📋 Funnel |
|
||||
🟡 |
|
||||
PI 42
|
||||
| |
|
||||
1.6 |
|
||||
Alternative Lösung für AppMesh (AWS EOL 2026) |
|
||||
O2CBS-555 |
|
||||
📋 Funnel |
|
||||
🟡 |
|
||||
PI 42
|
||||
| |
|
||||
1.7 |
|
||||
Verwendung von Network-Policies zur Netzwerksegmentierung |
|
||||
â |
|
||||
â |
|
||||
🟡 |
|
||||
PI 43
|
||||
| |
|
||||
1.8 |
|
||||
Umstellung der CNP-Repos auf helm |
|
||||
â |
|
||||
â |
|
||||
🟡 |
|
||||
PI 43
|
||||
## 2. Betrieb
|
||||
|
||||
| |
|
||||
# |
|
||||
Thema |
|
||||
Ticket |
|
||||
Status |
|
||||
Prio |
|
||||
PI
|
||||
| |
|
||||
2.1 |
|
||||
Vereinfachung Staging |
|
||||
â |
|
||||
â |
|
||||
🔴 |
|
||||
PI 41
|
||||
| |
|
||||
2.2 |
|
||||
Automatisierung Release & Deployment |
|
||||
â |
|
||||
â |
|
||||
🟡 |
|
||||
PI 41
|
||||
| |
|
||||
2.3 |
|
||||
Einbau DHI (Hardened Images) |
|
||||
â |
|
||||
â |
|
||||
🟡 |
|
||||
PI 41
|
||||
| |
|
||||
2.4 |
|
||||
Custom-Lösungen ausbauen und durch Standards ersetzen (Pipelines & Deployments) |
|
||||
â |
|
||||
â |
|
||||
🟡 |
|
||||
PI 42
|
||||
## 3. Sicherheit & Compliance
|
||||
|
||||
| |
|
||||
# |
|
||||
Thema |
|
||||
Ticket |
|
||||
Status |
|
||||
Prio |
|
||||
PI
|
||||
| |
|
||||
3.1 |
|
||||
Security-Groups auf egress-Ebene (Anforderung an CNP, benötigt für UKA) |
|
||||
â |
|
||||
â |
|
||||
🔴 |
|
||||
PI 41
|
||||
| |
|
||||
3.2 |
|
||||
Konzept für Passwort-/Secret-Rotation (CNP-API-Admin, Flyway, App-Secrets, DB-Restore) |
|
||||
â |
|
||||
â |
|
||||
🔴 |
|
||||
PI 41
|
||||
| |
|
||||
3.3 |
|
||||
Cert-Manager für Zertifikatsverwaltung verwenden |
|
||||
â |
|
||||
â |
|
||||
🟡 |
|
||||
PI 41
|
||||
| |
|
||||
3.4 |
|
||||
Secrets-Manager für Secrets verwenden (statt Environments) |
|
||||
â |
|
||||
â |
|
||||
🟡 |
|
||||
PI 42
|
||||
| |
|
||||
3.5 |
|
||||
Signieren von Nachrichten und Daten (intern) |
|
||||
O2CBS-763 |
|
||||
📋 Funnel |
|
||||
🟡 |
|
||||
PI 42
|
||||
| |
|
||||
3.6 |
|
||||
Nachrichtensignaturen mit Nachbarsystemen (TPN, KOMBau, TBV, Archivierung, Abrechnung, Stationsportal) |
|
||||
O2CBS-668 |
|
||||
📋 Funnel |
|
||||
🟡 |
|
||||
PI 43
|
||||
## 4. Observability & Monitoring
|
||||
|
||||
| |
|
||||
# |
|
||||
Thema |
|
||||
Ticket |
|
||||
Status |
|
||||
Prio |
|
||||
PI
|
||||
| |
|
||||
4.1 |
|
||||
Umsetzung Monitoring-Konzept (PI 39/40) |
|
||||
O2CBS-722 |
|
||||
âï¸ Implementation |
|
||||
🔴 |
|
||||
PI 40/PI 41/PI 42
|
||||
| |
|
||||
4.2 |
|
||||
Tracing in Produktivumgebung (Nachfolge-Enabler) |
|
||||
O2CBS-784 |
|
||||
📋 Funnel |
|
||||
🟡 |
|
||||
PI 42
|
||||
| |
|
||||
4.3 |
|
||||
Optimierung von Tracing-Daten und der damit verbundenen Datenmengen |
|
||||
â |
|
||||
â |
|
||||
🟢 |
|
||||
PI 44
|
||||
| |
|
||||
4.4 |
|
||||
Tracing in Systemtest und SIT integrieren |
|
||||
â |
|
||||
â |
|
||||
🟢 |
|
||||
PI 44
|
||||
## 5. Resilienz & Disaster Recovery
|
||||
|
||||
| |
|
||||
# |
|
||||
Thema |
|
||||
Ticket |
|
||||
Status |
|
||||
Prio |
|
||||
PI
|
||||
| |
|
||||
5.1 |
|
||||
Camunda Point-in-Time-Recovery |
|
||||
O2CBS-689 |
|
||||
âï¸ Validierung auf Staging |
|
||||
🔴 |
|
||||
PI 39/PI 40
|
||||
| |
|
||||
5.2 |
|
||||
Desaster-Recovery-Test 3 |
|
||||
O2CBS-576 |
|
||||
âï¸ Validierung auf Staging |
|
||||
🔴 |
|
||||
PI 39/PI 40
|
||||
| |
|
||||
5.3 |
|
||||
Notfall-Recovery-Test - Wiederanlaufplan nach Desaster (kompletter Neuaufbau Prod-gleicher Umgebung) |
|
||||
â |
|
||||
â |
|
||||
🔴 |
|
||||
PI 40/PI 41
|
||||
| |
|
||||
5.4 |
|
||||
RegelmäÃiger Datenabgleich TPN <> PathOS |
|
||||
â |
|
||||
â |
|
||||
🟡 |
|
||||
PI 40/PI 41
|
||||
| |
|
||||
5.5 |
|
||||
Runbook: Störfallszenarien erweitern |
|
||||
O2CBS-733 |
|
||||
📋 Funnel |
|
||||
🟡 |
|
||||
PI 41
|
||||
| |
|
||||
5.6 |
|
||||
Backup & Recovery von Kafka-Topics |
|
||||
â |
|
||||
â |
|
||||
🟢 |
|
||||
PI 43
|
||||
## 6. Architektur & Schnittstellen
|
||||
|
||||
| |
|
||||
# |
|
||||
Thema |
|
||||
Ticket |
|
||||
Status |
|
||||
Prio |
|
||||
PI
|
||||
| |
|
||||
6.1 |
|
||||
ADR 72: Anbindung von TraPo und C&R |
|
||||
O2CBS-1040 |
|
||||
📋 Analysis |
|
||||
🔴 |
|
||||
PI 40/41
|
||||
| |
|
||||
6.2 |
|
||||
Aufhebung bidirektionaler Abhängigkeit CI/TTK â SV (ADR-56) |
|
||||
O2CBS-306 |
|
||||
âï¸ Validierung auf Staging |
|
||||
🟡 |
|
||||
PI 40
|
||||
| |
|
||||
6.3 |
|
||||
Konzeption Vertragsdaten-Verteiler prüfen (Anbindung Stationsportal) |
|
||||
â |
|
||||
â |
|
||||
🟡 |
|
||||
PI 40
|
||||
| |
|
||||
6.4 |
|
||||
Versionierung von APIs (intern & extern) |
|
||||
â |
|
||||
â |
|
||||
🟡 |
|
||||
PI 41
|
||||
| |
|
||||
6.5 |
|
||||
Resilienz ggü. unzuverlässigen externen Schnittstellen verbessern |
|
||||
â |
|
||||
â |
|
||||
🟡 |
|
||||
PI 41
|
||||
| |
|
||||
6.6 |
|
||||
Projekt-Strukturen harmonisieren |
|
||||
â |
|
||||
â |
|
||||
🟢 |
|
||||
PI 42
|
||||
| |
|
||||
6.7 |
|
||||
Gitlab-Repositories restrukturieren |
|
||||
â |
|
||||
â |
|
||||
🟢 |
|
||||
PI 42
|
||||
| |
|
||||
6.8 |
|
||||
CI: Retry-Mechanismus für Ausgangsnachrichten mit Kafka |
|
||||
O2CBS-415 |
|
||||
📋 Analysis |
|
||||
🟢 |
|
||||
PI 44
|
||||
## 7. Datenbank, Datenmodell & Migration
|
||||
|
||||
| |
|
||||
# |
|
||||
Thema |
|
||||
Ticket |
|
||||
Status |
|
||||
Prio |
|
||||
PI
|
||||
| |
|
||||
7.1 |
|
||||
Auftrags-Verwaltung-Trasse: Full-Table-Scans vermeiden (Optimierung API/DB-Modell auf Lesen von Daten) |
|
||||
â |
|
||||
â |
|
||||
🔴 |
|
||||
PI 41
|
||||
| |
|
||||
7.2 |
|
||||
Partitionierung der Daten nach Fahrplanjahr (Produktive Umsetzung bis spätestens März 2027) |
|
||||
â |
|
||||
â |
|
||||
🟡 |
|
||||
PI 42
|
||||
| |
|
||||
7.3 |
|
||||
TDM-Nachrichten in DB auf aktuelle Version migrieren |
|
||||
O2CBS-418 |
|
||||
📋 Funnel |
|
||||
🟡 |
|
||||
PI 42
|
||||
| |
|
||||
7.4 |
|
||||
Stammdaten: Performance-Probleme beim Strecken-Import (Ordnungsrahmen-API) |
|
||||
â |
|
||||
â |
|
||||
🟢 |
|
||||
PI 43
|
||||
## 8. Framework-Modernisierung
|
||||
|
||||
| |
|
||||
# |
|
||||
Thema |
|
||||
Ticket |
|
||||
Status |
|
||||
Prio |
|
||||
PI
|
||||
| |
|
||||
8.1 |
|
||||
Upgrade auf Spring Boot 4 (EOL Spring Boot 3.5: Juni 2026) |
|
||||
O2CBS-1001 |
|
||||
📋 Funnel |
|
||||
🔴 |
|
||||
PI 40
|
||||
| |
|
||||
8.2 |
|
||||
Upgrade auf Camunda 8.8 (inkl. PITR) |
|
||||
â |
|
||||
â |
|
||||
🔴 |
|
||||
PI 41
|
||||
| |
|
||||
8.3 |
|
||||
Upgrade auf JUnit 6 |
|
||||
O2CBS-1002 |
|
||||
📋 Funnel |
|
||||
🟡 |
|
||||
PI 40
|
||||
| |
|
||||
8.4 |
|
||||
Upgrade auf Camunda 8.9 (inkl. PITR) |
|
||||
â |
|
||||
â |
|
||||
🟡 |
|
||||
PI 42
|
||||
## 9. Qualitätssicherung & Test
|
||||
|
||||
| |
|
||||
# |
|
||||
Thema |
|
||||
Ticket |
|
||||
Status |
|
||||
Prio |
|
||||
PI
|
||||
| |
|
||||
9.1 |
|
||||
Weiterentwicklung Testvorgehen Systemtest und SIT (ADR-70) |
|
||||
O2CBS-673 |
|
||||
âï¸ Implementation |
|
||||
🔴 |
|
||||
PI 40/PI 41
|
||||
| |
|
||||
9.2 |
|
||||
LuP Neo: Umsetzung Neu-Konzeption |
|
||||
O2CBS-640 |
|
||||
📋 Analysis |
|
||||
🔴 |
|
||||
PI 41
|
||||
| |
|
||||
9.3 |
|
||||
Automatisierter Test der Portal-UI auf Internationalisierungsfähigkeit (Zahlen, Datumsfelder) |
|
||||
â |
|
||||
â |
|
||||
🟡 |
|
||||
PI 41
|
||||
| |
|
||||
9.4 |
|
||||
Systemtests: Refactoring in Anlehnung an KITs von SV |
|
||||
O2CBS-353 |
|
||||
📋 Funnel |
|
||||
🟢 |
|
||||
PI 43
|
||||
| |
|
||||
9.5 |
|
||||
Bereitstellung von Testdaten im Bestellsystem |
|
||||
O2CBS-423 |
|
||||
📋 Analysis |
|
||||
🟢 |
|
||||
PI 43
|
||||
| |
|
||||
9.6 |
|
||||
Browser-Kompatibilität: Edge-/Chrome-/Firefox-Tests automatisieren |
|
||||
â |
|
||||
â |
|
||||
🟢 |
|
||||
PI 43
|
||||
| |
|
||||
9.7 |
|
||||
KITs in Projekten harmonisieren und qualitativ verbessern |
|
||||
â |
|
||||
â |
|
||||
🟢 |
|
||||
PI 43
|
||||
## 10. Dokumentation
|
||||
|
||||
| |
|
||||
# |
|
||||
Thema |
|
||||
Ticket |
|
||||
Status |
|
||||
Prio |
|
||||
PI
|
||||
| |
|
||||
10.1 |
|
||||
Ausarbeitung des Runbooks (PI 38) |
|
||||
O2CBS-732 |
|
||||
âï¸ Implementation |
|
||||
🔴 |
|
||||
PI 41
|
||||
| |
|
||||
10.2 |
|
||||
Neuerstellung Runbook basierend auf neuem Template |
|
||||
â |
|
||||
â |
|
||||
🟡 |
|
||||
PI 41/42
|
||||
## Zusammenfassung nach Priorität
|
||||
|
||||
| |
|
||||
Priorität |
|
||||
Anzahl
|
||||
| |
|
||||
🔴 MUSS UKA/GELV |
|
||||
17
|
||||
| |
|
||||
🟡 MUSS 2026 |
|
||||
24
|
||||
| |
|
||||
🟢 SOLL |
|
||||
12
|
||||
| |
|
||||
Gesamt |
|
||||
53
|
||||
## Zusammenfassung nach Status
|
||||
|
||||
| |
|
||||
Status |
|
||||
Anzahl
|
||||
| |
|
||||
âï¸ In Arbeit (Implementation / Validierung) |
|
||||
7
|
||||
| |
|
||||
📋 Zu erledigen (Funnel / Analysis) |
|
||||
16
|
||||
| |
|
||||
Kein Ticket |
|
||||
30
|
||||
Reference in New Issue
Block a user