Merge pull request #48203 from apinnick/BZ2110179-remove-workloads-ui

BZ2110179: Update UI procedures for top-level Virt

Author: apinnick

modules/virt-about-vm-templates.adoc

@@ -6,9 +6,9 @@
 [id="virt-understanding-vm-templates-web_{context}"]
 = About virtual machine templates
 
-Preconfigured Red Hat virtual machine templates are listed in the *Templates* tab within the *Virtualization* 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).
+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).
 
-The *Templates* tab displays four types of virtual machine templates:
+The *Templates* page displays four types of virtual machine templates:
 
 * *Red Hat Supported* templates are fully supported by Red Hat.
 * *User Supported* templates are *Red Hat Supported* templates that were cloned and created by users.
@@ -19,7 +19,7 @@ You can use the filters in the template *Catalog* to sort the templates by attri
 
 [NOTE]
 ====
-In the *Templates* tab, 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.
+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.

modules/virt-add-boot-order-web.adoc

@@ -11,11 +11,9 @@ Add items to a boot order list by using the web console.
 
 .Procedure
 
-. Click *Workloads* -> *Virtualization* from the side menu.
+. Click *Virtualization* -> *VirtualMachines* from the side menu.
 
-. Click the *Virtual Machines* tab.
-
-. Select a virtual machine to open the *Virtual Machine Overview* screen.
+. Select a virtual machine to open the *VirtualMachine details* page.
 
 . Click the *Details* tab.
 

modules/virt-add-disk-to-vm.adoc

@@ -9,15 +9,15 @@
 ifeval::["{context}" == "virt-edit-vms"]
 :virt-vm:
 :object: virtual machine
-:object-gui: Virtual Machines
-:object-vm-overview: Virtual Machine Overview
+:object-gui: VirtualMachines
+:object-vm-overview: VirtualMachine details
 endif::[]
 
 ifeval::["{context}" == "virt-editing-vm-template"]
 :virt-vm-template:
 :object: virtual machine template
 :object-gui: Templates
-:object-vm-overview: VM Template Details
+:object-vm-overview: Template details
 endif::[]
 
 :_content-type: PROCEDURE
@@ -29,19 +29,17 @@ Use this procedure to add a virtual disk to a {object}.
 
 .Procedure
 
-. Click *Workloads* -> *Virtualization* from the side menu.
-
-. Click the *{object-gui}* tab.
+. Click *Virtualization* -> *{object-gui}* from the side menu.
 
 . Select a {object} to open the *{object-vm-overview}* screen.
 
-. Click the *Disks* tab.
+. Click the *Disks* tab and then click *Add disk*.
 
-. In the *Add Disk* window, specify the *Source*, *Name*, *Size*, *Type*, *Interface*, and *Storage Class*.
+. In the *Add disk* window, specify the *Source*, *Name*, *Size*, *Type*, *Interface*, and *Storage Class*.
 
-.. Advanced: You can enable preallocation if you use a blank disk source and require maximum write performance when creating data volumes. To do so, select the *Enable preallocation* checkbox.
+.. Optional: You can enable preallocation if you use a blank disk source and require maximum write performance when creating data volumes. To do so, select the *Enable preallocation* checkbox.
 
-.. Optional: In the *Advanced* list, specify the *Volume Mode* and *Access Mode* for the virtual disk. If you do not specify these parameters, the system uses the default values from the `kubevirt-storage-class-defaults` config map.
+.. Optional: You can clear *Apply optimized StorageProfile settings* to change the *Volume Mode* and *Access Mode* for the virtual disk. If you do not specify these parameters, the system uses the default values from the `kubevirt-storage-class-defaults` config map.
 
 . Click *Add*.
 

modules/virt-add-nic-to-vm.adoc

@@ -6,15 +6,15 @@
 ifeval::["{context}" == "virt-edit-vms"]
 :virt-vm:
 :object: virtual machine
-:object-gui: Virtual Machines
-:object-vm-overview: Virtual Machine Overview
+:object-gui: VirtualMachines
+:object-vm-overview: VirtualMachine details
 endif::[]
 
 ifeval::["{context}" == "virt-editing-vm-template"]
 :virt-vm-template:
 :object: virtual machine template
 :object-gui: Templates
-:object-vm-overview: VM Template Details
+:object-vm-overview: Template details
 endif::[]
 
 :_content-type: PROCEDURE
@@ -26,9 +26,7 @@ Use this procedure to add a network interface to a {object}.
 
 .Procedure
 
-. Click *Workloads* -> *Virtualization* from the side menu.
-
-. Click the *{object-gui}* tab.
+. Click *Virtualization* -> *{object-gui}* from the side menu.
 
 . Select a {object} to open the *{object-vm-overview}* screen.
 

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

@@ -6,14 +6,14 @@
 [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* in the *Templates* tab. 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 *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:
 
 * *Upload local file (creates PVC)*
-* *Import via URL (creates PVC)*
-* *Clone existing PVC (creates PVC)*
-* *Import via Registry (creates PVC)*
+* *URL (creates PVC)*
+* *Clone (creates PVC)*
+* *Registry (creates PVC)*
 
 .Prerequisites
 * To add a boot source, you must be logged in as a user with the `os-images.kubevirt.io:edit` RBAC role or as an administrator. You do not need special privileges to create a virtual machine from a template with a boot source added.
@@ -28,19 +28,17 @@ There are four methods for selecting and adding a boot source in the web console
 
 .Procedure
 
-. In the {VirtProductName} console, click *Workloads* -> *Virtualization* from the side menu.
+. In the {product-title} console, click *Virtualization* -> *Templates* from the side menu.
 
-. Click the *Templates* tab.
+. Click *Add source* for the template that you want to configure.
 
-. Identify the virtual machine template for which you want to configure a boot source and click *Add source*.
-
-. 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*, *Import via URL*, *Clone existing PVC*, or *Import via Registry*.
+. 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.
 
 . 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 *Source provider* to associate the name with this template.
+.. 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.
 +
@@ -65,4 +63,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* tab, and you can create virtual machines by using this template.
+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.

modules/virt-adding-secret-configmap-service-account-to-vm.adoc

@@ -7,50 +7,34 @@
 
 = Adding a secret, config map, or service account to a virtual machine
 
-Add a secret, config map, or service account to a virtual machine by using the {product-title} web console.
+You add a secret, config map, or service account to a virtual machine by using the {product-title} web console.
+
+These resources are added to the virtual machine as disks. You then mount the secret, config map, or service account as you would mount any other disk.
+
+If the virtual machine is running, changes will not take effect until you restart the virtual machine. The newly added resources are marked as pending changes for both the *Environment* and *Disks* tab in the *Pending Changes* banner at the top of the page.
 
 .Prerequisites
 
 * The secret, config map, or service account that you want to add must exist in the same namespace as the target virtual machine.
 
 .Procedure
 
-. Click *Workloads* -> *Virtualization* from the side menu.
+. Click *Virtualization* -> *VirtualMachines* from the side menu.
 
-. Click the *Virtual Machines* tab.
+. Select a virtual machine to open the *VirtualMachine details* page.
 
-. Select a virtual machine to open the *Virtual Machine Overview* screen.
+. In the *Environment* tab, click *Add Config Map, Secret or Service Account*.
 
-. Click the *Environment* tab.
+. Click *Select a resource* and select a resource from the list. A six character serial number is automatically generated for the selected resource.
 
-. Click *Select a resource* and select a secret, config map, or service account from the list. A six character serial number is automatically
-generated for the selected resource.
+. Optional: Click *Reload* to revert the environment to its last saved state.
 
 . Click *Save*.
 
-. Optional. Add another object by clicking *Add Config Map, Secret or Service Account*.
-
-[NOTE]
-====
-.. You can reset the form to the last saved state by clicking *Reload*.
-
-.. The *Environment* resources are added to the virtual machine as disks. You can mount the secret, config map, or service account as you would mount any other disk.
-
-.. If the virtual machine is running, changes will not take effect until you restart the virtual machine. The newly added resources are marked as pending changes
-for both the *Environment* and *Disks* tab in the *Pending Changes* banner at the top of the page.
-
-====
-
 .Verification
 
-. From the *Virtual Machine Overview* page, click the *Disks* tab.
-
-. Check to ensure that the secret, config map, or service account is included in the list of disks.
-
-. Optional. Choose the appropriate method to apply your changes:
-
-.. If the virtual machine is running, restart the virtual machine by clicking *Actions* -> *Restart Virtual Machine*.
+. On the *VirtualMachine details* page, click the *Disks* tab and verify that the secret, config map, or service account is included in the list of disks.
 
-.. If the virtual machine is stopped, start the virtual machine by clicking *Actions* -> *Start Virtual Machine*.
+. Restart the virtual machine by clicking *Actions* -> *Restart*.
 
 You can now mount the secret, config map, or service account as you would mount any other disk.

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

@@ -6,21 +6,16 @@
 [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 in the
-*Virtualization* -> *Virtual Machines* tab, or from the *Actions* menu
-available on all tabs in the *Virtual Machine Overview* screen.
+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.
 
 .Procedure
 
-. In the {VirtProductName} console, click *Workloads* -> *Virtualization* from the side menu.
-. Click the *Virtual Machines* tab.
-. You can cancel the migration from this screen, which makes it easier to
-perform actions on multiple virtual machines, or from the
-*Virtual Machine Overview* screen where you can view comprehensive details
-of the selected virtual machine:
-** 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 *Virtual Machine Overview*
-screen and click *Actions* -> *Cancel Virtual Machine Migration*.
+. 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} 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-connecting-vnc-console.adoc

@@ -7,13 +7,12 @@
 = Connecting to the VNC console
 
 Connect to the VNC console of a running virtual machine from the *Console* tab
-in the *Virtual Machine Overview* screen of the web console.
+on the *VirtualMachine details* page of the web console.
 
 .Procedure
 
-. In the {VirtProductName} console, click *Workloads* -> *Virtualization* from the side menu.
-. Click the *Virtual Machines* tab.
-. Select a virtual machine to open the *Virtual Machine Overview* page.
+. In the {product-title} console, click *Virtualization* -> *VirtualMachines* from the side menu.
+. Select a virtual machine to open the *VirtualMachine details* page.
 . Click the *Console* tab. The VNC console opens by default.
 . Optional: Open the VNC console in a separate window by clicking *Open Console in New Window*.
 . Optional: Send key combinations to the virtual machine by clicking *Send Key*.

modules/virt-creating-a-custom-image-boot-source-web.adoc

@@ -15,9 +15,9 @@ Use this procedure to complete the following tasks:
 * Attaching the boot source to a custom template
 
 .Procedure
-. In the {VirtProductName} console, click *Workloads* > *Virtualization* from the side menu.
-. Click the *Templates* tab.
-. Click the link in the *Source provider* column for the template you want to customize. A window displays, indicating that the template currently has a *defined* source.
+
+. In the {product-title} console, click *Virtualization* -> *Templates* from the side menu.
+. Click the link in the *Boot source* column for the template you want to customize. A window displays, indicating that the template currently has a *defined* source.
 . In the window, click the *Customize source* link.
 . Click *Continue* in the *About boot source customization* window to proceed with customization after reading the information provided about the boot source customization process.
 . On the *Prepare boot source customization* page, in the *Define new template* section:

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

@@ -10,8 +10,8 @@ After you add a boot source to a template, you can create a new virtual machine
 
 .Procedure
 
-. In the {product-title} web console, click *Workloads > Virtualization* in the side menu.
-. From the *Virtual Machines* tab or the *Templates* tab, click *Create* and select *Virtual Machine with Wizard*.
+. 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.