Skip to content

Commit 36ec506

Browse files
apinnickapinnick
authored
Merge pull request #48203 from apinnick/BZ2110179-remove-workloads-ui
BZ2110179: Update UI procedures for top-level Virt
2 parents afbf54c + 7a1ae32 commit 36ec506

File tree

54 files changed

+232
-325
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

54 files changed

+232
-325
lines changed

‎modules/virt-about-vm-templates.adoc‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,9 @@
66
[id="virt-understanding-vm-templates-web_{context}"]
77
= About virtual machine templates
88

9-
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).
9+
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).
1010

11-
The *Templates* tab displays four types of virtual machine templates:
11+
The *Templates* page displays four types of virtual machine templates:
1212

1313
* *Red Hat Supported* templates are fully supported by Red Hat.
1414
* *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
1919

2020
[NOTE]
2121
====
22-
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.
22+
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.
2323
====
2424

2525
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‎

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,11 +11,9 @@ Add items to a boot order list by using the web console.
1111

1212
.Procedure
1313

14-
. Click *Workloads* -> *Virtualization* from the side menu.
14+
. Click *Virtualization* -> *VirtualMachines* from the side menu.
1515

16-
. Click the *Virtual Machines* tab.
17-
18-
. Select a virtual machine to open the *Virtual Machine Overview* screen.
16+
. Select a virtual machine to open the *VirtualMachine details* page.
1917

2018
. Click the *Details* tab.
2119

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

Lines changed: 8 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -9,15 +9,15 @@
99
ifeval::["{context}" == "virt-edit-vms"]
1010
:virt-vm:
1111
:object: virtual machine
12-
:object-gui: Virtual Machines
13-
:object-vm-overview: Virtual Machine Overview
12+
:object-gui: VirtualMachines
13+
:object-vm-overview: VirtualMachine details
1414
endif::[]
1515

1616
ifeval::["{context}" == "virt-editing-vm-template"]
1717
:virt-vm-template:
1818
:object: virtual machine template
1919
:object-gui: Templates
20-
:object-vm-overview: VM Template Details
20+
:object-vm-overview: Template details
2121
endif::[]
2222

2323
:_content-type: PROCEDURE
@@ -29,19 +29,17 @@ Use this procedure to add a virtual disk to a {object}.
2929

3030
.Procedure
3131

32-
. Click *Workloads* -> *Virtualization* from the side menu.
33-
34-
. Click the *{object-gui}* tab.
32+
. Click *Virtualization* -> *{object-gui}* from the side menu.
3533

3634
. Select a {object} to open the *{object-vm-overview}* screen.
3735

38-
. Click the *Disks* tab.
36+
. Click the *Disks* tab and then click *Add disk*.
3937

40-
. In the *Add Disk* window, specify the *Source*, *Name*, *Size*, *Type*, *Interface*, and *Storage Class*.
38+
. In the *Add disk* window, specify the *Source*, *Name*, *Size*, *Type*, *Interface*, and *Storage Class*.
4139

42-
.. 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.
40+
.. 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.
4341

44-
.. 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.
42+
.. 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.
4543

4644
. Click *Add*.
4745

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

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,15 +6,15 @@
66
ifeval::["{context}" == "virt-edit-vms"]
77
:virt-vm:
88
:object: virtual machine
9-
:object-gui: Virtual Machines
10-
:object-vm-overview: Virtual Machine Overview
9+
:object-gui: VirtualMachines
10+
:object-vm-overview: VirtualMachine details
1111
endif::[]
1212

1313
ifeval::["{context}" == "virt-editing-vm-template"]
1414
:virt-vm-template:
1515
:object: virtual machine template
1616
:object-gui: Templates
17-
:object-vm-overview: VM Template Details
17+
:object-vm-overview: Template details
1818
endif::[]
1919

2020
:_content-type: PROCEDURE
@@ -26,9 +26,7 @@ Use this procedure to add a network interface to a {object}.
2626

2727
.Procedure
2828

29-
. Click *Workloads* -> *Virtualization* from the side menu.
30-
31-
. Click the *{object-gui}* tab.
29+
. Click *Virtualization* -> *{object-gui}* from the side menu.
3230

3331
. Select a {object} to open the *{object-vm-overview}* screen.
3432

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

Lines changed: 9 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -6,14 +6,14 @@
66
[id="virt-adding-a-boot-source-web_{context}"]
77
= Adding a boot source for a virtual machine template
88

9-
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.
9+
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.
1010

1111
There are four methods for selecting and adding a boot source in the web console:
1212

1313
* *Upload local file (creates PVC)*
14-
* *Import via URL (creates PVC)*
15-
* *Clone existing PVC (creates PVC)*
16-
* *Import via Registry (creates PVC)*
14+
* *URL (creates PVC)*
15+
* *Clone (creates PVC)*
16+
* *Registry (creates PVC)*
1717
1818
.Prerequisites
1919
* 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
2828
2929
.Procedure
3030

31-
. In the {VirtProductName} console, click *Workloads* -> *Virtualization* from the side menu.
31+
. In the {product-title} console, click *Virtualization* -> *Templates* from the side menu.
3232

33-
. Click the *Templates* tab.
33+
. Click *Add source* for the template that you want to configure.
3434

35-
. Identify the virtual machine template for which you want to configure a boot source and click *Add source*.
36-
37-
. 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*.
35+
. 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*.
3836

3937
. 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.
4038

4139
. 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.
4240

43-
.. Optional: Enter a name for *Source provider* to associate the name with this template.
41+
.. Optional: Enter a name for *Boot source* to associate the name with this template.
4442

4543
.. 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.
4644
+
@@ -65,4 +63,4 @@ Provided boot sources are updated automatically to the latest version of the ope
6563

6664
.. Click *Save and clone* if you cloned an existing PVC.
6765

68-
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.
66+
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‎

Lines changed: 12 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -7,50 +7,34 @@
77

88
= Adding a secret, config map, or service account to a virtual machine
99

10-
Add a secret, config map, or service account to a virtual machine by using the {product-title} web console.
10+
You add a secret, config map, or service account to a virtual machine by using the {product-title} web console.
11+
12+
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.
13+
14+
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.
1115

1216
.Prerequisites
1317

1418
* The secret, config map, or service account that you want to add must exist in the same namespace as the target virtual machine.
1519

1620
.Procedure
1721

18-
. Click *Workloads* -> *Virtualization* from the side menu.
22+
. Click *Virtualization* -> *VirtualMachines* from the side menu.
1923

20-
. Click the *Virtual Machines* tab.
24+
. Select a virtual machine to open the *VirtualMachine details* page.
2125

22-
. Select a virtual machine to open the *Virtual Machine Overview* screen.
26+
. In the *Environment* tab, click *Add Config Map, Secret or Service Account*.
2327

24-
. Click the *Environment* tab.
28+
. Click *Select a resource* and select a resource from the list. A six character serial number is automatically generated for the selected resource.
2529

26-
. Click *Select a resource* and select a secret, config map, or service account from the list. A six character serial number is automatically
27-
generated for the selected resource.
30+
. Optional: Click *Reload* to revert the environment to its last saved state.
2831

2932
. Click *Save*.
3033

31-
. Optional. Add another object by clicking *Add Config Map, Secret or Service Account*.
32-
33-
[NOTE]
34-
====
35-
.. You can reset the form to the last saved state by clicking *Reload*.
36-
37-
.. 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.
38-
39-
.. 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
40-
for both the *Environment* and *Disks* tab in the *Pending Changes* banner at the top of the page.
41-
42-
====
43-
4434
.Verification
4535

46-
. From the *Virtual Machine Overview* page, click the *Disks* tab.
47-
48-
. Check to ensure that the secret, config map, or service account is included in the list of disks.
49-
50-
. Optional. Choose the appropriate method to apply your changes:
51-
52-
.. If the virtual machine is running, restart the virtual machine by clicking *Actions* -> *Restart Virtual Machine*.
36+
. 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.
5337

54-
.. If the virtual machine is stopped, start the virtual machine by clicking *Actions* -> *Start Virtual Machine*.
38+
. Restart the virtual machine by clicking *Actions* -> *Restart*.
5539

5640
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‎

Lines changed: 9 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -6,21 +6,16 @@
66
[id="virt-cancelling-vm-migration-web_{context}"]
77
= Cancelling live migration of a virtual machine instance in the web console
88

9-
You can cancel a live migration of the virtual machine instance using the
10-
Options menu {kebab} found on each virtual machine in the
11-
*Virtualization* -> *Virtual Machines* tab, or from the *Actions* menu
12-
available on all tabs in the *Virtual Machine Overview* screen.
9+
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.
1310

1411
.Procedure
1512

16-
. In the {VirtProductName} console, click *Workloads* -> *Virtualization* from the side menu.
17-
. Click the *Virtual Machines* tab.
18-
. You can cancel the migration from this screen, which makes it easier to
19-
perform actions on multiple virtual machines, or from the
20-
*Virtual Machine Overview* screen where you can view comprehensive details
21-
of the selected virtual machine:
22-
** Click the Options menu {kebab} at the end of virtual machine and select
23-
*Cancel Virtual Machine Migration*.
24-
** Select a virtual machine name to open the *Virtual Machine Overview*
25-
screen and click *Actions* -> *Cancel Virtual Machine Migration*.
13+
. In the {product-title} console, click *Virtualization* -> *VirtualMachines* from the side menu.
14+
15+
. You can cancel the migration from this screen, which makes it easier to perform actions on multiple virtual machines, or from the
16+
*VirtualMachine details* page where you can view comprehensive details of the selected virtual machine:
17+
18+
* Click the Options menu {kebab} at the end of virtual machine and select *Cancel Virtual Machine Migration*.
19+
* Select a virtual machine name to open the *VirtualMachine details* page and click *Actions* -> *Cancel Virtual Machine Migration*.
20+
2621
. Click *Cancel Migration* to cancel the virtual machine live migration.

‎modules/virt-connecting-vnc-console.adoc‎

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,13 +7,12 @@
77
= Connecting to the VNC console
88

99
Connect to the VNC console of a running virtual machine from the *Console* tab
10-
in the *Virtual Machine Overview* screen of the web console.
10+
on the *VirtualMachine details* page of the web console.
1111

1212
.Procedure
1313

14-
. In the {VirtProductName} console, click *Workloads* -> *Virtualization* from the side menu.
15-
. Click the *Virtual Machines* tab.
16-
. Select a virtual machine to open the *Virtual Machine Overview* page.
14+
. In the {product-title} console, click *Virtualization* -> *VirtualMachines* from the side menu.
15+
. Select a virtual machine to open the *VirtualMachine details* page.
1716
. Click the *Console* tab. The VNC console opens by default.
1817
. Optional: Open the VNC console in a separate window by clicking *Open Console in New Window*.
1918
. Optional: Send key combinations to the virtual machine by clicking *Send Key*.

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -15,9 +15,9 @@ Use this procedure to complete the following tasks:
1515
* Attaching the boot source to a custom template
1616
1717
.Procedure
18-
. In the {VirtProductName} console, click *Workloads* > *Virtualization* from the side menu.
19-
. Click the *Templates* tab.
20-
. 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.
18+
19+
. In the {product-title} console, click *Virtualization* -> *Templates* from the side menu.
20+
. 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.
2121
. In the window, click the *Customize source* link.
2222
. Click *Continue* in the *About boot source customization* window to proceed with customization after reading the information provided about the boot source customization process.
2323
. 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‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,8 @@ After you add a boot source to a template, you can create a new virtual machine
1010

1111
.Procedure
1212

13-
. In the {product-title} web console, click *Workloads > Virtualization* in the side menu.
14-
. From the *Virtual Machines* tab or the *Templates* tab, click *Create* and select *Virtual Machine with Wizard*.
13+
. In the {product-title} web console, click *Virtualization* -> *VirtualMachines* in the side menu.
14+
. Click *Create* and select *Virtual Machine with Wizard*.
1515
. 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.
1616
. Click *Review and Confirm*.
1717
. Review your virtual machine settings and edit them, if required.

0 commit comments

Comments
 (0)