Epic Goal

...

1. Saved search for Virtual Machines across the fleet of OCP clusters on the left hand nav.
2. Additional Virtual Machine actions inside those search results
3. Launch out to the remote cluster console from those results

Why is this important?

...

Meet our objectives of offering a competitive virtual machine strategy.

Scenarios

...

This is part of meeting our CNV commitments to showing VirtualMachines across your fleet of clusters

1. Virtual Machines are accessible as a top tier LIST in the ACM console: via Search
2. Basic actions can be take: start, stop, restart, destroy, & migrate
   1. Create a backend process for teams to leverage search and take actions
   2. Should use existing tools
3. Launch out

Acceptance Criteria

...

1. Saved Search is a tree branch off of the left hand Search NAV.
2. Actions are implemented
   1. Start
   2. Stop
   3. Restart
   4. (SPIKE) Destroy (one/many)
   5. (SPIKE) Migrate (move)
   6. Launch out

Dependencies (internal and external)

1. Search is moved to the left hand nav top level.

Previous Work (Optional):

1. There are extra details provided and a saved search for CNV virtualMachines

Open questions:

1. …

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.