Merge pull request #57756 from apinnick/CNV-27405-vm-config-tab

CNV-27405: VM configuration tab

Author: apinnick

_topic_maps/_topic_map.yml

@@ -3566,8 +3566,6 @@ Topics:
     File: virt-installing-qemu-guest-agent
   - Name: Viewing the QEMU guest agent information for virtual machines
     File: virt-viewing-qemu-guest-agent-web
-  - Name: Managing config maps, secrets, and service accounts in virtual machines
-    File: virt-managing-configmaps-secrets-service-accounts
   - Name: Installing VirtIO driver on an existing Windows virtual machine
     File: virt-installing-virtio-drivers-on-existing-windows-vm
   - Name: Installing VirtIO driver on a new Windows virtual machine

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

@@ -11,13 +11,15 @@ ifeval::["{context}" == "virt-edit-vms"]
 :object: virtual machine
 :object-gui: VirtualMachines
 :object-vm-overview: VirtualMachine details
+:tab: Configuration -> Disks
 endif::[]
 
 ifeval::["{context}" == "virt-editing-vm-template"]
 :virt-vm-template:
 :object: virtual machine template
 :object-gui: Templates
 :object-vm-overview: Template details
+:tab: Disks
 endif::[]
 
 :_content-type: PROCEDURE
@@ -31,11 +33,11 @@ Use this procedure to add a virtual disk to a {object}.
 
 . Click *Virtualization* -> *{object-gui}* from the side menu.
 
-. Select a {object} to open the *{object-vm-overview}* screen.
+. Select a {object} to open the *{object-vm-overview}* page.
 
-. Click the *Disks* tab and then click *Add disk*.
+. On the *{tab}* tab, click *Add disk*.
 
-. In the *Add disk* window, specify the *Source*, *Name*, *Size*, *Type*, *Interface*, and *Storage Class*.
+. Specify the *Source*, *Name*, *Size*, *Type*, *Interface*, and *Storage Class*.
 
 .. 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.
 

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

@@ -8,13 +8,15 @@ ifeval::["{context}" == "virt-edit-vms"]
 :object: virtual machine
 :object-gui: VirtualMachines
 :object-vm-overview: VirtualMachine details
+:tab: Configuration -> Network interfaces
 endif::[]
 
 ifeval::["{context}" == "virt-editing-vm-template"]
 :virt-vm-template:
 :object: virtual machine template
 :object-gui: Templates
 :object-vm-overview: Template details
+:tab: Network interfaces
 endif::[]
 
 :_content-type: PROCEDURE
@@ -28,11 +30,9 @@ Use this procedure to add a network interface to a {object}.
 
 . Click *Virtualization* -> *{object-gui}* from the side menu.
 
-. Select a {object} to open the *{object-vm-overview}* screen.
+. Select a {object} to open the *{object-vm-overview}* page.
 
-. Click the *Network Interfaces* tab.
-
-. Click *Add Network Interface*.
+. On the *{tab}* tab, click *Add Network Interface*.
 
 . In the *Add Network Interface* window, specify the *Name*, *Model*, *Network*, *Type*, and *MAC Address* of the network interface.
 

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

@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 //
-// * virt/virtual_machines/virt-managing-configmaps-secrets-service-accounts.adoc
+// * virt/virtual_machines/virt-edit-vms.adoc
 
 :_content-type: PROCEDURE
 [id="virt-adding-secret-configmap-service-account-to-vm_{context}"]
@@ -11,7 +11,7 @@ You add a secret, config map, or service account to a virtual machine by using t
 
 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.
+If the virtual machine is running, changes do not take effect until you restart the virtual machine. The newly added resources are marked as pending changes at the top of the page.
 
 .Prerequisites
 
@@ -20,20 +20,16 @@ If the virtual machine is running, changes will not take effect until you restar
 .Procedure
 
 . Click *Virtualization* -> *VirtualMachines* from the side menu.
-
 . Select a virtual machine to open the *VirtualMachine details* page.
-
-. In the *Environment* tab, click *Add Config Map, Secret or Service Account*.
-
+. Click *Configuration* -> *Environment*.
+. Click *Add Config Map, Secret or Service Account*.
 . Click *Select a resource* and select a resource 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*.
 
 .Verification
 
-. 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.
+. On the *VirtualMachine details* page, click *Configuration* -> *Disks* and verify that the resource is displayed in the list of disks.
 
 . Restart the virtual machine by clicking *Actions* -> *Restart*.
 

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

@@ -10,12 +10,14 @@ ifeval::["{context}" == "virt-dedicated-resources-vm-template"]
 :virt-vm-template:
 :object: virtual machine template
 :object-gui: Template
+:tab: Scheduling
 endif::[]
 
 ifeval::["{context}" == "virt-dedicated-resources-vm"]
 :virt-vm:
 :object: virtual machine
 :object-gui: VirtualMachine
+:tab: Configuration -> Scheduling
 endif::[]
 
 :_content-type: PROCEDURE
@@ -28,7 +30,7 @@ You enable dedicated resources for a {object} in the *Details* tab. Virtual mach
 
 . In the {product-title} console, click *Virtualization* -> *{object-gui}s* from the side menu.
 . Select a {object} to open the *{object-gui} details* page.
-. On the *Scheduling* tab, click the pencil icon beside *Dedicated Resources*.
+. On the *{tab}* tab, click the edit icon beside *Dedicated Resources*.
 . Select *Schedule this workload with dedicated resources (guaranteed policy)*.
 . Click *Save*.
 

modules/virt-edit-cdrom-vm.adoc

@@ -14,8 +14,8 @@ Before generalizing the VM, you must ensure the `sysprep` tool cannot detect an
 
 . In the {product-title} console, click *Virtualization* -> *VirtualMachines*.
 . Select a Windows VM to open the *VirtualMachine details* page.
-. Click the *Disks* tab.
-. Click the Options menu {kebab} for the `sysprep` disk and select *Detach*.
+. Click *Configuration* -> *Disks*.
+. Click the Options menu {kebab} beside the `sysprep` disk and select *Detach*.
 . Click *Detach*.
 . Rename `C:\Windows\Panther\unattend.xml` to avoid detection by the `sysprep` tool.
 

modules/virt-enabling-dedicated-resources.adoc

@@ -17,7 +17,7 @@ Hot plug virtual disks that you want to attach to a virtual machine instance (VM
 
 . Select the running virtual machine to which you want to hot plug a virtual disk.
 
-. On the *VirtualMachine details* page, click the *Disks* tab.
+. On the *VirtualMachine details* page, click *Configuration* -> *Disks*.
 
 . Click *Add disk*.
 

modules/virt-generalizing-windows-sysprep.adoc

@@ -14,9 +14,7 @@ Hot unplug virtual disks that you want to detach from a virtual machine instance
 .Procedure
 
 . Click *Virtualization* -> *VirtualMachines* from the side menu.
-
 . Select the running virtual machine with the disk you want to hot unplug to open the *VirtualMachine details* page.
-
-. On the *Disks* tab, click the Options menu {kebab} of the virtual disk that you want to hot unplug.
-
+. Click *Configuration* -> *Disks*.
+. Click the Options menu {kebab} beside the virtual disk that you want to hot unplug and select *Detach*.
 . Click *Detach*.