-
Epic
-
Resolution: Done
-
Blocker
-
None
-
Define an architecture to support and manage Ansible cloud services
-
False
-
False
-
To Do
-
ACM-1078 - Provide ACM as the supporting infrastructure to the RH cloud services
-
0
-
0%
Epic Goal
- Provide an architecture that allows SD team to deliver their code on Kubernetes platform.
- ACM/MCE will be part of the path to supporting an Ansible cloud service on Azure.
- What are the necessary components from ACM/MCE to support an Ansible cloud service?
Why is this important?
- ACM/MCE as a key element into RH's delivery of cloud services.
Scenarios
- ...
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ACM running and monitoring at least a few of the preview services that are being deployed
- when an SRE can leverage ACM to diagnose and solve a problem with a running service.
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
Open questions:
- Is this KCP?
- We need to define success criteria / exit criteria.
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
- DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
- DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>
