Removing wizard references and other fixes.

Author: apinnick

modules/virt-about-qemu-guest-agent-web.adoc

@@ -6,11 +6,11 @@
 [id="About-the-qemu-guest-agent-web_{context}"]
 = About the QEMU guest agent information in the web console
 
-When the QEMU guest agent is installed, the *Details* pane within the *Virtual Machine Overview* tab and the *Details* tab display information about the hostname, operating system, time zone, and logged in users.
+When the QEMU guest agent is installed, the *Overview* and *Details* tabs on the *VirtualMachine details* page displays information about the hostname, operating system, time zone, and logged in users.
 
-The *Virtual Machine Overview* shows information about the guest operating system installed on the virtual machine. The *Details* tab displays a table with information for logged in users. The *Disks* tab displays a table with information for file systems.
+The *VirtualMachine details* page shows information about the guest operating system installed on the virtual machine. The *Details* tab displays a table with information for logged in users. The *Disks* tab displays a table with information for file systems.
 
 [NOTE]
 ====
-If the QEMU guest agent is not installed, the *Virtual Machine Overview* tab and the *Details* tab display information about the operating system that was specified when the virtual machine was created.
+If the QEMU guest agent is not installed, the *Overview* and the *Details* tabs display information about the operating system that was specified when the virtual machine was created.
 ====

modules/virt-about-vm-templates.adoc

@@ -3,7 +3,7 @@
 // * virt/vm_templates/virt-creating-vm-template.adoc
 
 :_content-type: CONCEPT
-[id="virt-understanding-vm-templates-web_{context}"]
+[id="virt-about-vm-templates_{context}"]
 = About virtual machine templates
 
 Preconfigured Red Hat virtual machine templates are listed in the *Virtualization* -> *Templates* page. These templates are available for different versions of Red Hat Enterprise Linux, Fedora, Microsoft Windows 10, and Microsoft Windows Servers. Each Red Hat virtual machine template is preconfigured with the operating system image, default settings for the operating system, flavor (CPU and memory), and workload type (server).
@@ -17,14 +17,9 @@ The *Templates* page displays four types of virtual machine templates:
 
 You can use the filters in the template *Catalog* to sort the templates by attributes such as boot source availability, operating system, and workload.
 
-[NOTE]
-====
-You cannot edit or delete *Red Hat Supported* or *Red Hat Provided* templates. You can only edit or delete custom virtual machine templates that were created by users.
-====
-
-Using a Red Hat template is convenient because the template is already preconfigured. When you select a Red Hat template to create your own custom template, the *Create Virtual Machine Template* wizard prompts you to add a boot source if a boot source was not added previously. Then, you can either save your custom template or continue to customize it and save it.
+You cannot edit or delete a *Red Hat Supported* or *Red Hat Provided* template. You can clone the template, save it as a custom virtual machine template, and then edit it.
 
-You can also select the *Create Virtual Machine Template* wizard directly and create a custom virtual machine template. The wizard prompts you to provide configuration details for the operating system, flavor, workload type, and other settings. You can add a boot source and continue to customize your template and save it.
+You can also create a custom virtual machine template by editing a YAML file example.
 
 [IMPORTANT]
 ====

modules/virt-adding-a-boot-source-web.adoc

@@ -6,7 +6,7 @@
 [id="virt-adding-a-boot-source-web_{context}"]
 = Adding a boot source for a virtual machine template
 
-A boot source can be configured for any virtual machine template that you want to use for creating virtual machines or custom templates. When virtual machine templates are configured with a boot source, they are labeled *Available* on the *Templates* page. After you add a boot source to a template, you can create a new virtual machine from the template.
+A boot source can be configured for any virtual machine template that you want to use for creating virtual machines or custom templates. When virtual machine templates are configured with a boot source, they are labeled *Source available* on the *Templates* page. After you add a boot source to a template, you can create a new virtual machine from the template.
 
 There are four methods for selecting and adding a boot source in the web console:
 
@@ -29,31 +29,20 @@ There are four methods for selecting and adding a boot source in the web console
 .Procedure
 
 . In the {product-title} console, click *Virtualization* -> *Templates* from the side menu.
-
-. Click *Add source* for the template that you want to configure.
-
-. In the *Add boot source to template* window, click *Select boot source*, select a method for creating a persistent volume claim (PVC): *Upload local file*, *URL*, *Clone*, or *Registry*.
-
-. Optional: Click *This is a CD-ROM boot source* to mount a CD-ROM and use it to install the operating system on to an empty disk. The additional empty disk is automatically created and mounted by {VirtProductName}. If the additional disk is not needed, you can remove it when you create the virtual machine.
-
+. Click the options menu beside a template and select *Edit boot source*.
+. Click *Add disk*.
+. In the *Add disk* window, select *Use this disk as a boot source*.
+. Enter the disk name and select a *Source*, for example, *Blank (creates PVC)* or *Use an existing PVC*.
 . Enter a value for *Persistent Volume Claim size* to specify the PVC size that is adequate for the uncompressed image and any additional space that is required.
-
-.. Optional: Enter a name for *Boot source* to associate the name with this template.
-
-.. Optional: *Advanced Storage settings*: Click *Storage class* and select the storage class that is used to create the disk. Typically, this storage class is the default storage class that is created for use by all PVCs.
+. Select a *Type*, for example, *Disk*, which is required for hot-plugging, or *CD-ROM*.
+. Optional: Click *Storage class* and select the storage class that is used to create the disk. Typically, this storage class is the default storage class that is created for use by all PVCs.
 +
 [NOTE]
 ====
 Provided boot sources are updated automatically to the latest version of the operating system. For auto-updated boot sources, persistent volume claims (PVCs) are created with the cluster's default storage class. If you select a different default storage class after configuration, you must delete the existing data volumes in the cluster namespace that are configured with the previous default storage class.
 ====
 
-.. Optional: *Advanced Storage settings*: Click *Access mode* and select an access mode for the persistent volume:
-
-* *Single User (RWO)* mounts the volume as read-write by a single node.
-* *Shared Access (RWX)* mounts the volume as read-write by many nodes.
-* *Read Only (ROX)* mounts the volume as read-only by many nodes.
-
-.. Optional: *Advanced Storage settings*: Click *Volume mode* if you want to select *Block* instead of the default value *Filesystem*. {VirtProductName} can statically provision raw block volumes. These volumes do not have a file system, and can provide performance benefits for applications that either write to the disk directly or implement their own storage service.
+. Optional: Clear *Apply optimized StorageProfile settings* to edit the access mode or volume mode.
 
 . Select the appropriate method to save your boot source:
 
@@ -63,4 +52,4 @@ Provided boot sources are updated automatically to the latest version of the ope
 
 .. Click *Save and clone* if you cloned an existing PVC.
 
-Your custom virtual machine template with a boot source is listed in the *Templates* page, and you can create virtual machines by using this template.
+Your custom virtual machine template with a boot source is listed on the *Catalog* page. You can use this template to quick create a virtual machine.

modules/virt-assign-vgpu-passthrough-to-vm.adoc

@@ -3,33 +3,29 @@
 // * virt/virtual_machines/advanced_vm_management/virt-configuring-vgpu-passthrough.adoc
 
 [id="virt-assign-vgpu-passthrough-to-vm_{context}"]
-= Assigning vGPU passthrough to virtual machines
+= Assigning vGPU passthrough devices to a virtual machine
 
-Use the {product-title} web console to assign vGPU devices to your virtual machines.
+Use the {product-title} web console to assign vGPU passthrough devices to your virtual machine.
 
 .Prerequisites
 
-* Ensure your cluster and virtual machines are deployed in a bare metal environment. At this time, no other environments are supported.
+* The virtual machine must be stopped.
 
 .Procedure
 
-. Assign a virtual GPU device to your virtual machine:
-.. In the {product-title} web console, click *Virtualization -> Virtual Machines* from the side menu.
-.. Select the virtual machine to which you want to assign the device.
-.. Click the *Details* tab:
-* The *Hardware Devices* field includes links to add or remove *GPU devices* and *Host devices*.
-* Assigning a vGPU using *GPU devices* enables VNC console access for the attached virtual GPU. Assigning a vGPU using *Host Devices* does not enable VNC console access.
-* Use the minus icon to remove an existing hardware device.
-* You can only add or remove devices from your virtual machine when it is stopped.
-.. Click the pencil icon and use the pop-up windows to add or remove devices, selecting the appropriate hardware resource names.
-.. Click *Save*.
+. In the {product-title} web console, click *Virtualization -> VirtualMachines* from the side menu.
+. Select the virtual machine to which you want to assign the device.
+. On the *Details* tab, click *GPU devices*.
++
+If you add a vGPU device as a host device, you cannot access the device with VNC console.
+
+. Click *Add GPU device*, enter the *Name* and select the device from the *Device name* list.
+. Click *Save*.
 . Click the *YAML* tab to verify that the new devices have been added to your cluster configuration in the `hostDevices` section.
 
 [NOTE]
 ====
-You can add hardware devices to virtual machines using the {product-title} web console when you create a virtual machine or create a virtual machine using a  template that you customize. You cannot add devices to pre-supplied boot source templates for specific operating systems, such as Windows 10 or RHEL 7.
-
-To add or remove hardware devices to a custom template that you create, click the *Advanced* tab in the Create Virtual Machine wizard and click *Hardware devices*. Use the minus icon to remove an existing hardware device. You can only add or remove devices from your virtual machine when it is stopped.
+You can add hardware devices to virtual machines created from customized templates or a YAML file. You cannot add devices to pre-supplied boot source templates for specific operating systems, such as Windows 10 or RHEL 7.
 
-To display resources that are connected to your cluster, click *Compute -> Hardware Devices* from the side menu.
+To display resources that are connected to your cluster, click *Compute* -> *Hardware Devices* from the side menu.
 ====

modules/virt-cancelling-vm-migration-web.adoc

@@ -6,16 +6,11 @@
 [id="virt-cancelling-vm-migration-web_{context}"]
 = Cancelling live migration of a virtual machine instance in the web console
 
-You can cancel a live migration of the virtual machine instance using the Options menu {kebab} found on each virtual machine on the *VirtualMachines* page or from the *Actions* menu on the *VirtualMachine details* page.
+You can cancel the live migration of a virtual machine instance in the web console.
 
 .Procedure
 
 . In the {product-title} console, click *Virtualization* -> *VirtualMachines* from the side menu.
 
-. You can cancel the migration from this screen, which makes it easier to perform actions on multiple virtual machines, or from the
-*VirtualMachine details* page where you can view comprehensive details of the selected virtual machine:
+. Click the Options menu {kebab} beside a virtual machine and select *Cancel Migration*.
 
-* Click the Options menu {kebab} at the end of virtual machine and select *Cancel Virtual Machine Migration*.
-* Select a virtual machine name to open the *VirtualMachine details* page and click *Actions* -> *Cancel Virtual Machine Migration*.
-
-. Click *Cancel Migration* to cancel the virtual machine live migration.

modules/virt-creating-a-vm-from-a-template-with-an-attached-boot-source.adoc

@@ -6,13 +6,11 @@
 [id="virt-creating-a-vm-from-a-template-with-an-attached-boot-source_{context}"]
 = Creating a virtual machine from a template with an attached boot source
 
-After you add a boot source to a template, you can create a new virtual machine from the template.
+After you add a boot source to a template, you can create a virtual machine from the template.
 
 .Procedure
 
-. In the {product-title} web console, click *Virtualization* -> *VirtualMachines* in the side menu.
-. Click *Create* and select *Virtual Machine with Wizard*.
-. In the *Select a template* step, select an OS from the Operating System list that has the *(Source available)* label next to the OS and version name. The *(Source available)* label indicates that a boot source is available for this OS.
-. Click *Review and Confirm*.
-. Review your virtual machine settings and edit them, if required.
-. Click *Create Virtual Machine* to create your virtual machine. The *Successfully created virtual machine* page is displayed.
+. In the {product-title} web console, click *Virtualization* -> *Catalog* in the side menu.
+. Select the updated template and click *Quick create VirtualMachine*.
++
+The *VirtualMachine details* is displayed with the status *Starting*.

modules/virt-creating-vm-wizard-web.adoc

@@ -10,17 +10,13 @@ Deleting a virtual machine template permanently removes it from the cluster.
 
 [NOTE]
 ====
-You can delete virtual machine templates that were created by using a Red Hat template or the *Create Virtual Machine Template* wizard. Preconfigured virtual machine templates that are provided by Red Hat cannot be deleted.
+You can delete customized virtual machine templates. You cannot delete Red Hat-supplied templates.
 ====
 
 .Procedure
 
 . In the {product-title} console, click *Virtualization* -> *Templates* from the side menu.
 
-. Select the appropriate method to delete a virtual machine template:
+. Click the Options menu {kebab} of a template and select *Delete template*.
 
-* Click the Options menu {kebab} of the template to delete and select *Delete Template*.
-
-* Click the template name to open the *Details* page and then click *Actions* -> *Delete Template*.
-
-. In the confirmation pop-up window, click *Delete* to permanently delete the template.
+. Click *Delete*.

modules/virt-deleting-template-web.adoc

@@ -6,21 +6,14 @@
 [id="virt-editing-vmis-web_{context}"]
 = Editing a standalone virtual machine instance using the web console
 
-You can edit annotations and labels for a standalone virtual machine instance (VMI) using the web console. Other items displayed in the *Details* page for a standalone VMI are not editable.
+You can edit the annotations and labels of a standalone virtual machine instance (VMI) using the web console. Other fields are not editable.
 
 .Procedure
 
-. Click *Virtualization* -> *VirtualMachines* from the side menu.
+. In the {product-title} console, click *Virtualization* -> *VirtualMachines* from the side menu.
 
-. Click the name of a standalone VMI to open the *Virtual Machine Instance Overview* screen.
+. Select a standalone VMI to open the *VirtualMachineInstance details* page.
 
-. Click the *Details* tab.
+. On the *Details* tab, click the pencil icon beside *Annotations* or *Labels*.
 
-. Click the pencil icon that is located on the right side of *Annotations*.
-
-. Make the relevant changes and click *Save*.
-
-[NOTE]
-====
-To edit labels for a standalone VMI, click *Actions* and select *Edit Labels.* Make the relevant changes and click *Save*.
-====
+. Make the relevant changes and click *Save*.