-
Epic
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
ACM 2.14 CNV Integration Enhancements (console focus)
-
False
-
None
-
False
-
Not Selected
-
To Do
-
VIRTSTRAT-53 - ACM Virtual Machine view provides details card with links to the source CNV VM console
-
-
50% To Do, 50% In Progress, 0% Done
Epic Goal
...
This Epic is a follow up of: https://issues.redhat.com/browse/ACM-14379
We will close this spike story and start on a new set of spikes for more granular tracking.
ACM-17918 ACM-17914 ACM-17917 ACM-17919
We were able to demonstrate through prototyping that the key questions posed in this spike are possible.
Remaining issues we have identified are identified in this document.
Fleet API compatibility (exploring a technical solution in ACM-17914)
Hub cluster compatibility
UX of where functionality lives
Packaging question of how UI is delivered
Initial discussions with CNV engineering focused on defining the interface between ACM and CNV; we will improve the design of the prototype via ACM-17918 and continue syncing with CNV on a weekly basis
Why is this important?
...
Scenarios
...
Acceptance Criteria
...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- ...
Open questions:
- …
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 - Doc issue opened with a completed template. Separate doc issue
opened for any deprecation, removal, or any current known
issue/troubleshooting removal from the doc, if applicable. - Considerations were made for Extended Update Support (EUS)
