XML

Word

Printable

Epic Name:
ui-virtcl-create-vm
Acceptance Criteria:

Hide

1. Use virtctl for vm from instanceType creation boilerplate
2. Use virtctl for Service creation for port exposure

Show
1. Use virtctl for vm from instanceType creation boilerplate 2. Use virtctl for Service creation for port exposure
Epic Status:
To Do
Feature Link:
CNV-25728 - GA and Instance Types by default
Parent Link:
CNV-25728GA and Instance Types by default
Hierarchy Progress Bar:

100% To Do, 0% In Progress, 0% Done
Target Version:

CNV v4.16.0

Goal

The UI should be implemented in a way, that ensures to stay compatible with the CLI.

User Stories

As a developer I want to be sure that it does not matter if I created the VM via UI or CLI.

List of things not included in this epic, to alleviate any doubt raised during the grooming process.

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	<link or reference to Polarion>
QE	Automated tests merged	<link or reference to automated tests>
DOC	Downstream documentation merged	<link to meaningful PR>

depends on

CNV-21977 TP: CLI for creating VMs using instanceType API

is related to

CNV-30930 [docs] VM YAML can be improved by the usage of instancetypes

CNV-27329 [UI] Cover more flows of disk based VM creation

relates to

CNV-27314 [UI][UX] showing cli command to create VM