Repository navigation
tests/ci: add k-orc (ORC) integration - #47
Conversation
|
I had this running through an internal, agent-driven pipeline (it needed too many other internal PR to run the plain pipeline without many merges first). I asked the agent to generate the proof of work: The k-orc (ORC) integration tests are workingThe k-orc feature (added on pattern branch Evidence — CI test run: 18/18 passedEvidence — k-orc Applications and ORC-managed OpenStack resourcesEvidence — a real VM was booted through ORCThe server is ACTIVE with a fixed IP on the ORC-managed network — |
6192ae4 to
415379a
Compare
CI-only integration deploying the OpenStack Resource Controller from its official Helm charts and a steady-state smoke stack (Flavor, Image, Network, Subnet, Port, Server) managed through ORC. The pytest suite creates the k-orc Argo CD Application from a template in tests/ci/k-orc/, pointing it at the pattern's own repository. Applications are labeled validatedpatterns.io/ci-feature and excluded from the pattern inventory assertions. Generated-By: rits/zai-org/glm-5-3
415379a to
b04dcea
Compare
|
I had to rebase the change against |
|
looks ok , approved |
|
on my side I don't have an approval permission button, but overall it's approved |
CI-only integration deploying the OpenStack Resource Controller from its official Helm charts and a steady-state smoke stack (Flavor, Image, Network, Subnet, Port, Server) managed through ORC.
The pytest suite creates the k-orc Argo CD Application from a template in tests/ci/k-orc/, pointing it at the pattern's own repository. Applications are labeled validatedpatterns.io/ci-feature and excluded from the pattern inventory assertions.
Generated-By: rits/zai-org/glm-5-3