-
Notifications
You must be signed in to change notification settings - Fork 1.9k
CNV-94223: Document the custom configuration workflow for creating a VM #117147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
a29210d
47151ee
c6ea186
6c83022
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,54 @@ | ||
| // Module included in the following assemblies: | ||
| // | ||
| // * virt/creating_vm/virt-creating-vms-web.adoc | ||
|
|
||
| :_mod-docs-content-type: PROCEDURE | ||
| [id="virt-creating-vm-custom-configuration-web_{context}"] | ||
| = Create a VM with custom configuration by using the web console | ||
|
|
||
| [role="_abstract"] | ||
| You can use the *Custom configuration* workflow in the web console to create a virtual machine (VM) by selecting a guest operating system, boot source, compute resources, and advanced settings. | ||
|
|
||
| Use this workflow when no existing template matches your requirements, when you need a specific combination of compute, storage, and network settings, or when you want to boot from a custom disk image. | ||
|
|
||
| .Prerequisites | ||
|
|
||
| * You have access to the {product-title} web console. | ||
| * You have the required permissions to create VMs in the target project. | ||
|
|
||
| .Procedure | ||
|
|
||
| . In the {product-title} web console, navigate to *Virtualization* -> *VirtualMachines*. | ||
| . Click *Create*. | ||
| . On the *Deployment details* page, select the creation method, enter general information, and define the location: | ||
| .. Select *Custom configuration*. | ||
| .. In the *Name* field, enter a name for the VM. You can also click the refresh icon to generate a name automatically. | ||
| .. Optional: Enter a *Description* for the VM. | ||
| .. Review the *Location* to verify the target cluster, project, and folder. To change the location, click the edit icon. | ||
| .. Click *Next*. | ||
| . On the *Guest operating system* page, specify the operating system: | ||
| .. Select the guest operating system, such as *RHEL*, *Microsoft Windows*, or *Other Linux*. | ||
| .. Select the operating system version from the *Guest operating system type* list. | ||
| .. Click *Next*. | ||
| . On the *Boot source* page, specify the boot volume: | ||
| .. Select *Boot volume* to use an existing boot volume or add a new one, or select *No boot source* to assign an empty disk that you can configure later. | ||
| .. If you selected *Boot volume*, select an existing volume from the list, or click *Add volume* to configure a new boot volume. | ||
| .. Click *Next*. | ||
| . On the *Compute resources* page, define the instance type: | ||
| .. Select an instance type series, such as *General purpose* or *Compute Exclusive*. | ||
| .. Select the vCPU and memory size from the drop-down list. | ||
| .. Click *Next*. | ||
| . On the *Customization* page, optionally configure advanced settings by navigating the following tabs: | ||
| + | ||
| * *Details*: Configure the *Hostname*, *Headless mode*, *Guest system log access*, and *Deletion protection*. | ||
| * *Storage*: Add or modify storage disks. | ||
| * *Network*: Add additional network interfaces. | ||
| * *Scheduling*: Configure scheduling requirements and the run strategy. | ||
| * *SSH*: Configure SSH key settings. | ||
| * *Initial run*: Define *Cloud-init* or *Sysprep* initialization scripts. | ||
| * *Metadata*: Add *Labels* and *Annotations*. | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. As I remember, the "Metadata" tab title has been changed to "Labels and annotations," if we want to refer to each tab consistently by its displayed name
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @mayarub I had actually run through the flow in the console earlier today and double-checked. This is a screenshot from a 4.22.2 cluster:
Are you sure? |
||
| + | ||
| Click *Next*. | ||
| . On the *Review and create* page, review the VM configuration: | ||
| .. Optional: Select the *Start this VirtualMachine after creation* checkbox. | ||
| .. Click *Create VirtualMachine*. | ||
This file was deleted.
This file was deleted.
This file was deleted.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,19 @@ | ||
| :_mod-docs-content-type: ASSEMBLY | ||
| [id="virt-creating-vms-web"] | ||
| = Create virtual machines by using the web console | ||
| include::_attributes/common-attributes.adoc[] | ||
| :context: virt-creating-vms-web | ||
|
|
||
| toc::[] | ||
|
|
||
| [role="_abstract"] | ||
| You can create virtual machines (VMs) by using the {product-title} web console. The web console creation wizard provides workflows for custom configuration, creating a VM from a template, and cloning an existing VM. | ||
|
|
||
| // Custom configuration procedure (CNV-94223) | ||
| include::modules/virt-creating-vm-custom-configuration-web.adoc[leveloffset=+1] | ||
|
|
||
| // Template-based creation procedure (CNV-94224) | ||
|
|
||
| // Clone existing VM procedure (CNV-94225) | ||
|
|
||
| // VM creation considerations reference (CNV-94226) |
This file was deleted.

There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Users can also navigate to create virtual machine wizard via right-click on a project and select "Create VirtualMachine" option. When they do, the selected project is automatically pre-filled in the Location section of the Deployment details step.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure we want to document alternate ways of reaching the wizard. We're shifting away from documenting every single button/option and focusing on the main customer journeys. I'll discuss with our content strategist abut whether we think there's added value to including this alternate.