Discuss and roughly mock up what the OpenShift Virtualization experience might look like within an "All Clusters" perspective of the Hybrid Console in the near-term, and how it could be improved in the medium and long-term.

Discuss dependencies, questions, and risks with stakeholders to make sure this approach would be suitable to level OpenShift Virtualization up to a multi-cluster level.

Questions
How does this look in the virtual machine list?
How does this look in the template list?
How does it look in the vm/template details page and overview page?
How would this look in the high level virtualization>Overview page?

More thoughts from PD-985

It would be good to think of an example of how multicluster could surface in the console.

We could take OpenShift Virtualization as an example:

Workloads > Virtualization > Overview
Could we show clusters on the inventory card? Or show multi-cluster on the status or permissions card?

Workloads > Virtualization > Virtual Machines

In the list view could we show which cluster a VM belongs to?

When creating a VM could we choose which cluster to create it on? (This would be both for admin and dev)

In the details view of the VM show the parent cluster (would we be able to migrate VMs from one cluster to another easily?)

Workloads > Virtualization > Templates

Could templates be multi-cluster? 

Outcomes

• Use case brainstorming Mural

Links

• OpenShift Hybrid Console Roadmap