-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
iso-flow
-
False
-
-
False
-
To Do
-
80% To Do, 0% In Progress, 20% Done
-
---
-
---
Goal
The UI detects that the PVC contains an iso and adopts the UI accordingly.
User Stories
- As a Developer, I want create a new VM by installing from an ISO image, so that I can avoid the usage of prepared cloud images and go on with my traditional workflow.
- another user story
Non-Requirements
- List of things not included in this epic, to alleviate any doubt raised during the grooming process.
Notes
- During upload, the PVC might be labeled as an iso
- If the label is set, the UI can prepare the yaml in another way.
Done Checklist
Who | What | Reference |
---|---|---|
DEV | Upstream roadmap issue (or individual upstream PRs) | <link to GitHub Issue> |
DEV | Upstream documentation merged | <link to meaningful PR> |
DEV | gap doc updated | <name sheet and cell> |
DEV | Upgrade consideration | <link to upgrade-related test or design doc> |
DEV | CEE/PX summary presentation | label epic with cee-training and add a <link to your support-facing preso> |
QE | Test plans in Polarion | https://polarion.engineering.redhat.com/polarion/#/project/CNV/workitem?id=CNV-11425 |
QE | Automated tests merged | https://gitlab.cee.redhat.com/cnv-qe/kubevirt-ui/-/merge_requests/798 |
DOC | Downstream documentation merged | <link to meaningful PR> |
- is related to
-
CNV-27323 [UI] Support ISO installation flow in disk-based UI
- New
-
CNV-48519 Iso-Flow: Boot disk size should be applied to the root disk
- Closed
-
CNV-48521 Iso-Flow: Root disk is hard coded to SATA
- Closed
-
CNV-48524 Iso-Flow: add
- Closed
- split from
-
CNV-27329 [UI] Cover more flows of disk based VM creation
- Closed
- links to
- mentioned on
(2 links to, 2 mentioned on)