Merge pull request #62342 from apinnick/fix-create-vms

"Creating VMs" cleanup

Author: apinnick

modules/odc-creating-vms.adoc

@@ -4,13 +4,13 @@
 
 :_content-type: PROCEDURE
 [id="virt-creating-vm-cli_{context}"]
-= Using the CLI to create a virtual machine
+= Creating a virtual machine by using the command line
 
-You can create a virtual machine from a `virtualMachine` manifest.
+You can create a virtual machine (VM) by using the command line.
 
 .Procedure
 
-. Edit the `VirtualMachine` manifest for your VM. For example, the following manifest configures a {op-system-base-full} VM:
+. Edit the `VirtualMachine` manifest for your VM. The following example configures a {op-system-base-full} VM:
 +
 .Example manifest for a {op-system-base} VM
 [source,yaml]

modules/virt-creating-vm-cli.adoc

@@ -6,30 +6,25 @@
 [id="virt-creating-vm-instancetype_{context}"]
 = Creating a virtual machine from an instance type
 
-You can use common instance types to install and edit customized instance types and preferences to create a virtual machine (VM).
+You create a virtual machine (VM) from an instance type by using the {product-title} web console.
 
 :FeatureName: Creating a virtual machine from an instance type
 include::snippets/technology-preview.adoc[]
 
 .Procedure
 
-. In the web console, navigate to *Virtualization* -> *Catalog* -> *InstanceTypes*.
-
-. Select a volume to boot from.
+. In the web console, navigate to *Virtualization* -> *Catalog* and click the *InstanceTypes* tab.
 
+. Select a bootable volume.
 +
 [NOTE]
 ====
-The volumes list shows only volumes that exist in the `openshift-virtualization-os-images` namespace and have the `instancetype.kubevirt.io/default-preference` label.
+The volume table only lists volumes in the `openshift-virtualization-os-images` namespace that have the `instancetype.kubevirt.io/default-preference` label.
 ====
 
-. Select an instance type from the 'InstanceType' list.
-
-. Select the 'InstanceType' size based on the VM's available CPUs and memory.
-
-. Optional: Edit the *VirtualMachine details*. You can edit the SSH key during this step under *Advanced settings*.
+. Click an instance type tile and select the configuration appropriate for your workload.
 
-. Optional: Clear the *Start this VirtualMachine after creation* checkbox to prevent the VM from starting automatically.
+. Optional: Expand *Advanced settings* to add a static public SSH key to the VM.
 
 . Click *Create VirtualMachine*.
 

modules/virt-creating-vm-custom-template.adoc

@@ -0,0 +1,30 @@
+// Module included in the following assemblies:
+//
+// * virt/virtual_machines/virt-create-vms.adoc
+
+:_content-type: PROCEDURE
+[id="virt-creating-vm-template_{context}"]
+= Creating a virtual machine from a template
+
+You can create a virtual machine (VM) from a template with an available boot source by using the {product-title} web console.
+
+.Procedure
+
+. Click *Virtualization* -> *Catalog* in the side menu.
+
+. Click *Boot source available* to filter templates with boot sources.
++
+The catalog displays the default templates. Click *All Items* to view all available templates for your filters.
+
+. Click a template tile to view its details.
+
+. Click *Quick create VirtualMachine* to create a VM from the template.
++
+Optional: Update parameters such as the VM name or disk source:
+
+.. Click *Customize VirtualMachine*.
+.. Edit the parameters and click *Next*.
+.. Click *Create VirtualMachine*.
++
+The *VirtualMachine details* page displays the provisioning status.
+

modules/virt-creating-vm-instancetype.adoc

@@ -4,9 +4,9 @@
 
 :_content-type: PROCEDURE
 [id="virt-creating-vm-yaml-web_{context}"]
-= Pasting in a pre-configured YAML file to create a virtual machine
+= Creating a virtual machine from a YAML file
 
-Create a virtual machine by writing or pasting a YAML configuration file. A valid `example` virtual machine configuration is provided by default whenever you open the YAML edit screen.
+You can create a virtual machine by writing or pasting a YAML configuration file in the {product-title} web console. A valid `example` virtual machine configuration is provided by default whenever you open the YAML edit screen.
 
 If your YAML configuration is invalid when you click *Create*, an error message indicates the parameter in which the error occurs. Only one error is shown at a time.
 

modules/virt-creating-vm-quick-start-web.adoc

@@ -6,11 +6,10 @@
 [id="virt-storage-wizard-fields-web_{context}"]
 = Storage fields
 
-[cols="5a,3a,5a"]
+[cols="1a,3a"]
 |===
-|Name |Selection |Description
+|Field |Description
 
-.6+|Source
 |Blank (creates PVC)
 |Create an empty disk.
 
@@ -30,60 +29,50 @@
 |Upload content from a container located in a registry accessible from the cluster. The container disk should be used only for read-only filesystems such as CD-ROMs or temporary virtual machines.
 
 |Name
-|
 |Name of the disk. The name can contain lowercase letters (`a-z`), numbers (`0-9`), hyphens (`-`), and periods (`.`), up to a maximum of 253 characters. The first and last characters must be alphanumeric. The name must not contain uppercase letters, spaces, or special characters.
 
 |Size
-|
 |Size of the disk in GiB.
 
 |Type
-|
 |Type of disk. Example: Disk or CD-ROM
 
 |Interface
-|
 |Type of disk device. Supported interfaces are *virtIO*, *SATA*, and *SCSI*.
 
 |Storage Class
-|
 |The storage class that is used to create the disk.
 |===
 
 [id="virt-storage-wizard-fields-advanced-web_{context}"]
 [discrete]
 == Advanced storage settings
 
-The following advanced storage settings are optional and available for *Blank*, *Import via URL*, and *Clone existing PVC* disks.  Before {VirtProductName} 4.11, if you do not specify these parameters, the system uses the default values from the `kubevirt-storage-class-defaults` config map. In {VirtProductName} 4.11 and later, the system uses the default values from the xref:../../virt/virtual_machines/virtual_disks/virt-creating-data-volumes.adoc#virt-customizing-storage-profile_virt-creating-data-volumes[storage profile].
+The following advanced storage settings are optional and available for *Blank*, *Import via URL*, and *Clone existing PVC* disks.
 
-[NOTE]
-====
-Use storage profiles to ensure consistent advanced storage settings when provisioning storage for {VirtProductName}.
-
-To manually specify *Volume Mode* and *Access Mode*, you must clear the *Apply optimized StorageProfile settings* checkbox, which is selected by default.
-====
+If you do not specify these parameters, the system uses the default storage profile values.
 
-[cols="5a,3a,3a,5a",options="header"]
+[cols="1a,1a,3a",options="header"]
 |===
-|Name |Mode description |Parameter |Parameter description
+|Parameter |Option |Parameter description
 
 .2+|Volume Mode
 
-.2+|Defines whether the persistent volume uses a formatted file system or raw block state. Default is *Filesystem*.
 |Filesystem
 |Stores the virtual disk on a file system-based volume.
 |Block
 |Stores the virtual disk directly on the block volume. Only use `Block` if the underlying storage supports it.
-.3+|Access Mode
-.3+|Access mode of the persistent volume.
+
+.2+|Access Mode
 |ReadWriteOnce (RWO)
 |Volume can be mounted as read-write by a single node.
 |ReadWriteMany (RWX)
 |Volume can be mounted as read-write by many nodes at one time.
 [NOTE]
 ====
-This is required for some features, such as live migration of virtual machines between nodes.
+This mode is required for live migration.
 ====
+
 |ReadOnlyMany (ROX)
 |Volume can be mounted as read only by many nodes.
 |===

modules/virt-creating-vm-template.adoc

@@ -3,11 +3,12 @@
 // * virt/virtual_machines/virt-create-vms.adoc
 
 [id="virt-vm-storage-volume-types_{context}"]
-= Virtual machine storage volume types
+= Storage volume types
 
-[cols="1a,1a"]
+.Storage volume types
+[cols="1a,3a"]
 |===
-|Storage volume type |Description
+|Type |Description
 
 |ephemeral
 |A local copy-on-write (COW) image that uses a network volume as a read-only backing store. The backing volume must be a *PersistentVolumeClaim*. The ephemeral image is created when the virtual machine starts and stores all writes locally. The ephemeral image is discarded when the virtual machine is stopped, restarted, or deleted. The backing volume (PVC) is not mutated in any way.