Patrick.Sy/website-and-documentation
1
0
Fork 0
forked from DevFW-CICD/website-and-documentation
Code Pull requests Activity
website-and-documentation/content/en/docs/v1/project/plan-in-2024/_index.md
Stephan Lo 43cbd69c9c refactor(docs): migrate existing content to v1 legacy structure 
- Move all existing docs content (concepts, project, solution) to /docs/v1/
- Add legacy banner component to warn users about archived documentation
- Create v1 index page with legacy notice and redirect guidance
- Implement automatic banner display for all v1 paths
- Preserve all original content for reference during migration

This enables incremental content migration while maintaining access to
original documentation.
2025-10-23 14:54:08 +02:00

1.3 KiB
Raw Blame History

title weight description
Plan in 2024 30 The planned project workload in 2024

First Blue Print in 2024

Our first architectural blue print for the IPCEI-CIS Developer Framework derives from Humanitecs Reference Architecture, see links in Blog

alt text

C4 Model

(sources see in ./ressources/architecture-c4)

How to use: install C4lite VSC exension and/or C4lite cli - then open *.c4 files in ./ressources/architecture-c4

First system landscape C4 model:

c4-model

In Confluence

https://confluence.telekom-mms.com/display/IPCEICIS/Architecture

Dimensionierung Cloud für initiales DevFramework

28.08.24, Stefan Bethke, Florian Fürstenberg, Stephan Lo

  1. zuerst viele DevFrameworkPlatformEngineers arbeiten lokal, mit zentralem Deployment nach OTC in einen/max zwei Control-Cluster
  2. wir gehen anfangs von ca. 5 clustern aus
  3. jeder cluster mit 3 Knoten/VM (in drei AvailabilityZones)
  4. pro VM 4 CPU, 16 GB Ram, 50 GB Storage read/write once, PVCs 'ohne limit'
  5. public IPs, plus Loadbalancer
  6. Keycloak vorhanden
  7. Wildcard Domain ?? --> Eher ja

Next Steps: (Vorschlag: in den nächsten 2 Wochen)

  1. Florian spezifiziert an Tobias
  2. Tobias stellt bereit, kubeconfig kommt an uns
  3. wir deployen