1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-06 06:46:26 +01:00
Files
openshift-docs/modules/virt-editing-vm-web.adoc

74 lines
2.5 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: Virtual Machine Template
endif::[]
ifeval::["{context}" == "virt-edit-vms"]
:virt-vm:
:object: virtual machine
:object-gui: Virtual Machine
endif::[]
[id="virt-editing-vm-web_{context}"]
= Editing a {object} in the web console
Edit select values of a {object} in the *{object-gui} Overview* screen
of the web console by clicking on the pencil icon next to the relevant field.
Other values can be edited using the CLI.
.Procedure
. Click *Workloads* -> *Virtualization* from the side menu.
. Click the *{object-gui}s* tab.
. Select a {object} to open the *{object-gui} Overview* screen.
. Click the *Details* tab.
. Click the pencil icon to make a field editable.
. Make the relevant changes and 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-template[]
Editing a virtual machine template will not affect virtual machines already created from that template.
endif::virt-vm-template[]
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!:
endif::[]
ifeval::["{context}" == "virt-editing-vm-template"]
:virt-vm-template!:
:object!:
:object-gui!:
endif::[]