mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-07 09:46:53 +01:00
91 lines
3.1 KiB
Plaintext
91 lines
3.1 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * virt/virtual_machines/virt-edit-vms.adoc
|
|
// * virt/vm_templates/virt-editing-vm-template.adoc
|
|
|
|
// Establishing conditionals so content can be re-used for editing VMs
|
|
// and VM templates.
|
|
|
|
// The ifeval statements use the context of the assembly in which the module
|
|
// is included to declare 1) an attribute, and 2) the content of the {object}
|
|
// and {object-gui} variables used throughout. We need two variables because
|
|
// the object is lower case, but the gui elements are capitalized.
|
|
|
|
ifeval::["{context}" == "virt-editing-vm-template"]
|
|
:virt-vm-template:
|
|
:object: virtual machine template
|
|
:object-gui: Templates
|
|
:object-vm-details: Template details
|
|
endif::[]
|
|
|
|
ifeval::["{context}" == "virt-edit-vms"]
|
|
:virt-vm:
|
|
:object: virtual machine
|
|
:object-gui: VirtualMachines
|
|
:object-vm-details: VirtualMachine details
|
|
endif::[]
|
|
|
|
:_content-type: PROCEDURE
|
|
[id="virt-editing-vm-web_{context}"]
|
|
|
|
= Editing a {object} in the web console
|
|
|
|
You can edit a {object} by using the {product-title} web console or the command line interface.
|
|
|
|
ifdef::virt-vm-template[]
|
|
Editing a {object} does not affect virtual machines already created from that template.
|
|
endif::virt-vm-template[]
|
|
|
|
.Procedure
|
|
|
|
. Navigate to *Virtualization* -> *{object-gui}* in the web console.
|
|
|
|
ifdef::virt-vm[]
|
|
. Select a {object} to open the *{object-vm-details}* page.
|
|
|
|
. Click any field that has the pencil icon, which indicates that the field is editable. For example, click the current *Boot mode* setting, such as BIOS or UEFI, to open the *Boot mode* window and select an option from the list.
|
|
endif::virt-vm[]
|
|
ifdef::virt-vm-template[]
|
|
. Click the {kebab} Options menu beside a {object} and select the object to edit.
|
|
|
|
. To edit a Red Hat template, click the {kebab} Options menu, select *Clone* to create a custom template, and then edit the custom template.
|
|
+
|
|
[NOTE]
|
|
====
|
|
*Edit boot source reference* is disabled if the template's data source is managed by the `DataImportCron` custom resource or if the template does not have a data volume reference.
|
|
====
|
|
endif::virt-vm-template[]
|
|
|
|
. Click *Save*.
|
|
|
|
// Using the attributes we declared earlier, we can have different lines after
|
|
// the procedure that will be included in the different assemblies.
|
|
|
|
ifdef::virt-vm[]
|
|
[NOTE]
|
|
====
|
|
If the {object} is running, changes to *Boot Order* or *Flavor* will not take effect until you restart the {object}.
|
|
|
|
You can view pending changes by clicking *View Pending Changes* on the right side of the relevant field. The *Pending Changes* banner at the
|
|
top of the page displays a list of all changes that will be applied when the {object} restarts.
|
|
====
|
|
endif::virt-vm[]
|
|
|
|
// Unsetting the attributes/variables used in the module or else they will stay active
|
|
// subsequent modules in the assembly and topic_map.
|
|
// Attributes set with an ifeval statement need to be unset with an ifeval statement.
|
|
|
|
ifeval::["{context}" == "virt-edit-vms"]
|
|
:virt-vm!:
|
|
:object!:
|
|
:object-gui!:
|
|
:object-vm-details!:
|
|
endif::[]
|
|
|
|
ifeval::["{context}" == "virt-editing-vm-template"]
|
|
:virt-vm-template!:
|
|
:object!:
|
|
:object-gui!:
|
|
:object-vm-details!:
|
|
endif::[]
|