Skip to content

Commit b7519cd

Browse files
authored
Merge pull request #44575 from openshift-cherrypick-robot/cherry-pick-44106-to-enterprise-4.10
[enterprise-4.10] CNV-15967: Auto update boot sources change
2 parents 9c1d687 + c13240e commit b7519cd

File tree

3 files changed

+11
-0
lines changed

3 files changed

+11
-0
lines changed

modules/virt-about-vms-and-boot-sources.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,8 @@ Virtual machines consist of a virtual machine definition and one or more disks t
1212

1313
Every virtual machine template requires a boot source, which is a fully configured virtual machine disk image including configured drivers. Each virtual machine template contains a virtual machine definition with a pointer to the boot source. Each boot source has a predefined name and namespace. For some operating systems, a boot source is automatically provided. If it is not provided, then an administrator must prepare a custom boot source.
1414

15+
Provided boot sources are updated automatically to the latest version of the operating system. For auto-updated boot sources, persistent volume claims (PVCs) are created with the cluster's default storage class. If you select a different default storage class after configuration, you must delete the existing data volumes in the cluster namespace that are configured with the previous default storage class.
16+
1517
To use the boot sources feature, install the latest release of {VirtProductName}. The namespace `openshift-virtualization-os-images` enables the feature and is installed with the {VirtProductName} Operator.
1618
Once the boot source feature is installed, you can create boot sources, attach them to templates, and create virtual machines from the templates.
1719

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

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -43,6 +43,11 @@ There are four methods for selecting and adding a boot source in the web console
4343
.. Optional: Enter a name for *Source provider* to associate the name with this template.
4444

4545
.. 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.
46+
+
47+
[NOTE]
48+
====
49+
Provided boot sources are updated automatically to the latest version of the operating system. For auto-updated boot sources, persistent volume claims (PVCs) are created with the cluster's default storage class. If you select a different default storage class after configuration, you must delete the existing data volumes in the cluster namespace that are configured with the previous default storage class.
50+
====
4651

4752
.. Optional: *Advanced Storage settings*: Click *Access mode* and select an access mode for the persistent volume:
4853

virt/virtual_machines/virtual_disks/virt-creating-and-using-boot-sources.adoc

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,10 @@ include::_attributes/common-attributes.adoc[]
66

77
toc::[]
88

9+
A boot source contains a bootable operating system (OS) and all of the configuration settings for the OS, such as drivers.
10+
11+
You use a boot source to create virtual machine templates with specific configurations. These templates can be used to create any number of available virtual machines.
12+
913
include::modules/virt-about-vms-and-boot-sources.adoc[leveloffset=+1]
1014

1115
include::modules/virt-importing-rhel-image-boot-source-web.adoc[leveloffset=+1]

0 commit comments

Comments
 (0)