Stephan Lo
3239cfbc62
Renamed resources/likec4 to resources/edp-likec4 to better reflect that this directory contains the Enterprise Developer Platform architecture models, not documentation platform architecture. Extended element kinds in edp-likec4/models/spec.c4 to support documentation platform modeling: - Added person, tool, process, repository element kinds - These allow modeling of documentation workflows and processes Consolidated webcomponent generation: - Combined both architecture projects (edp-likec4 and doc-likec4) into a single webcomponent output at static/js/likec4-webcomponent.js - Updated Taskfile.yml to generate from edp-likec4 directory - Removed duplicate webcomponent script loading in head-end.html - Fixed CustomElementRegistry duplicate registration issue Embedded TeleNeoOffice corporate fonts: - Added font files to static/fonts/ and static/ root - Required for correct rendering of diagrams in webcomponent - Fonts are embedded in webcomponent but also served from Hugo static paths - Fixed 404 errors for font loading Updated architecture documentation: - Fixed markdown linting issues (trailing spaces, fence spacing) - Updated all references from resources/likec4 to resources/edp-likec4 - Enhanced setup.md with correct directory structure This refactoring enables: 1. Clear separation between EDP architecture and documentation platform models 2. Single consolidated webcomponent containing all architecture views 3. Proper font loading for corporate branding in diagrams 4. Foundation for future architecture documentation expansion Breaking changes: None (paths updated in documentation)
74 lines
2.3 KiB
Text
74 lines
2.3 KiB
Text
// Deployment model
|
|
deployment {
|
|
|
|
cloud otc-edpFoundry 'OTC EDP Foundry Central Service clusters' {
|
|
description '
|
|
OTC environments for the central EDP Foundry services. This is kubernetes clusters and other infrastructure like nodes and vms, and optionally platform services. All is set up by IaC terraform and edpbuilder.
|
|
|
|
A tenant is a folder in Foundry-Config-Forgejo. On merge triggers reconciliation to EDP.
|
|
Optionally we will have a WebUI/API/CLI
|
|
'
|
|
technology 'OTC'
|
|
|
|
kubernetes cce 'OTC CCE' {
|
|
description 'OTC Container Cluster Engine'
|
|
icon tech:kubernetes
|
|
technology 'Kubernetes'
|
|
|
|
cluster internalServices 'EDP Foundry Internal Services' {
|
|
instanceOf edp.argoCD
|
|
instanceOf edp.forgejo {
|
|
-> workflowSetupEDPInfrastructure.forgejoRunner 'invokes'
|
|
-> workflowSetupArgoCDInfrastructure.forgejoRunner 'invokes'
|
|
}
|
|
instanceOf edp.externalSecrets
|
|
instanceOf edp.openbao
|
|
instanceOf edp.ingressNginx
|
|
}
|
|
|
|
cluster centralObservability 'EDP Foundry Central Observability' {
|
|
instanceOf edp.grafana
|
|
instanceOf edp.prometheus
|
|
instanceOf edp.loki
|
|
}
|
|
}
|
|
computeressource workflowSetupEDPInfrastructure 'EDP infrastructure Workflow' {
|
|
description 'EDP infrastructure Workflow'
|
|
|
|
instanceOf forgejoRunner {
|
|
-> forgejoRunnerWorker 'runs'
|
|
}
|
|
instanceOf forgejoRunnerWorker {
|
|
-> edpworkflow 'executes'
|
|
}
|
|
instanceOf edpworkflow {
|
|
-> otc-edp-per-tenant.cce.edp 'deploys edp to otc.cce'
|
|
-> otc-edp-per-tenant.cloudServices 'deploys edp to otc.paas'
|
|
|
|
}
|
|
}
|
|
|
|
computeressource workflowSetupArgoCDInfrastructure 'EDP ArgoCD Workflow' {
|
|
description 'EDP Setup ArgoCD Workflow'
|
|
instanceOf forgejoRunner {
|
|
-> forgejoRunnerWorker 'runs'
|
|
}
|
|
instanceOf forgejoRunnerWorker {
|
|
-> edpworkflow 'executes'
|
|
}
|
|
instanceOf edpworkflow {
|
|
-> otc-edp-per-tenant.cce.argoCD
|
|
|
|
}
|
|
}
|
|
|
|
computeressource forgejoRunnerInfrastructure 'EDP ForgejoRunner infrastructure' {
|
|
description 'Infrastructure for Forgejo runners like pods, vms, lxds, etc'
|
|
instanceOf forgejoRunner {
|
|
-> cce.internalServices.forgejo 'registers'
|
|
}
|
|
}
|
|
|
|
}
|
|
}
|
|
|