You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<!-- markdownlint-disable MD041 -->
#### What this PR does / why we need it
This document designs a reference scenario demonstrating OCM's core
value proposition: **modeling, signing, transporting, and deploying a
multi-service product into an air-gapped sovereign cloud environment**.
The scenario uses two genuinely interdependent services:
- **sovereign-notes**: A minimal Go web service that stores notes in
PostgreSQL
- **PostgreSQL**: The official postgres image, deployed via manifests
Both are packaged as OCM components, signed, transferred through an
air-gap via CTF, and bootstrapped on a local kind cluster using the OCM
Kubernetes controllers with KRO, Flux/Argo.
#### Which issue(s) this PR fixes
<!--
Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
-->
This gives us a new reference scenario that integrates us with Apeiro
and the World.
fixopen-component-model/ocm-project#842
Note that this itself is not finished until fully integrated. Especially
integration into Apeiro is higher level and conceptual than our OCM
delivery scenario.
Note also that this delivery scenario itself is not fully ready, and
many APIs are pseudo-coded in by me. As I understand them more, I gain
more understanding of the APIs as well so these things might change. The
core delivery scenario should be rather stable however
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
* **New Features**
* Added a sovereign conformance scenario: deployable Notes service +
PostgreSQL, Helm charts, OpenAPI/ORD metadata, product orchestration,
and end‑to‑end task automation for build/sign/air‑gap/import/deploy.
* **Tests**
* CI now exposes image tags and includes a reusable Conformance
workflow/job to run the end‑to‑end scenario.
* **Documentation**
* Added conformance README, scenario USAGE, detailed ADR/design doc,
runbooks and contribution guidance.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
---------
Signed-off-by: Jakob Möller <jakob.moeller@sap.com>
Signed-off-by: Jakob Möller <contact@jakob-moeller.com>
This directory contains conformance tests and reference scenarios that validate OCM's core capabilities and design principles.
4
+
5
+
## Purpose
6
+
7
+
Conformance testing ensures that OCM implementations correctly handle:
8
+
9
+
- Component modeling and construction
10
+
- Signing and verification workflows
11
+
- Cross-registry transport and localization
12
+
- Air-gap deployment scenarios
13
+
- Integration with cloud-native ecosystem tools
14
+
15
+
## Structure
16
+
17
+
-`scenarios/` - Reference implementation scenarios that demonstrate end-to-end OCM workflows
18
+
- Each scenario includes:
19
+
- Complete working implementation
20
+
- Conformance test suite
21
+
- Documentation and setup instructions
22
+
- CI/CD automation
23
+
24
+
## Current Scenarios
25
+
26
+
-[`sovereign/`](./scenarios/sovereign) - Demonstrates modeling, signing, transporting, and deploying a multi-service product into an air-gapped sovereign cloud environment (ADR-0013)
27
+
28
+
## Running Conformance Tests based on a scenario
29
+
30
+
```bash
31
+
cd scenarios/sovereign
32
+
task run
33
+
```
34
+
35
+
## Contributing
36
+
37
+
When adding new conformance scenarios:
38
+
39
+
1. Create scenario directory under `scenarios/`
40
+
2. Include complete working implementation
41
+
3. Add conformance test suite in `tests/conformance/`
42
+
4. Document setup and validation steps
43
+
5. Update this README
44
+
45
+
Each scenario should validate specific OCM capabilities and serve as a reference implementation for users adopting OCM.
0 commit comments