OSDOCS Document how to perform boot image updates on vSphere clusters#109084
OSDOCS Document how to perform boot image updates on vSphere clusters#109084mburke5678 wants to merge 5 commits intoopenshift:mainfrom
Conversation
openshift-ci
bot
added
the
size/L
|
🤖 Tue Mar 31 20:45:12 - Prow CI generated the docs preview: |
|
|
||
| . In the vSphere Client, create a template for the OVA image: | ||
| .. From the *Hosts and Clusters* tab, right-click your cluster name and select *Deploy OVF Template*. | ||
| .. On the *Select an OVF* tab, specify the name of the {op-system} OVA file that you downloaded. |
There was a problem hiding this comment.
| .. On the *Select an OVF* tab, specify the name of the {op-system} OVA file that you downloaded. | |
| .. On the *Select an OVF* tab, select the {op-system} OVA file that you downloaded. |
edited it for clarity
| . In the vSphere Client, create a template for the OVA image: | ||
| .. From the *Hosts and Clusters* tab, right-click your cluster name and select *Deploy OVF Template*. | ||
| .. On the *Select an OVF* tab, specify the name of the {op-system} OVA file that you downloaded. | ||
| .. On the *Select a name and folder* tab, set a *Virtual machine name* for your template, such as `Template-{op-system}`. Click the name of your vSphere cluster and select the folder. |
There was a problem hiding this comment.
it might be helpful to include the version of the bootimage in this template name as well, since it doesn't seem like there's another place to tag it
There was a problem hiding this comment.
@djoshy
Such as?
such as
Template-{op-system}-{version}
There was a problem hiding this comment.
I'm unsure if the vcenter system permits all the special characters/length, so perhaps something simple like the RHCOS major.minor (example Template-rhcos-9-6) instead of the whole version string might be a good idea.
There was a problem hiding this comment.
How about using the "such as using the {op-system-first} version number in the image name" wording that we have in the procedure for a few other platforms?
On the Select a name and folder tab, set a Virtual machine name for your template, such as using the {op-system-first} version number in the image name.
There was a problem hiding this comment.
Hmm on second thought could we reword:
On the Select a name and folder tab, set a Virtual machine name for your template. Include the {op-system-first} version in the name (for example, template-rhcos-9.6) to make it easier to identify the {op-system} version when performing future updates.
|
Although this was in the marketplace epic, strictly speaking OCP doesn't use the vsphere marketplace, just standalone so fixing that: /retitle OSDOCS Document how to perform boot image updates on vSphere clusters |
openshift-ci
bot
changed the title
| . In the vSphere Client, create a template for the OVA image: | ||
| .. From the *Hosts and Clusters* tab, right-click your cluster name and select *Deploy OVF Template*. | ||
| .. On the *Select an OVF* tab, specify the name of the {op-system} OVA file that you downloaded. | ||
| .. On the *Select a name and folder* tab, set a *Virtual machine name* for your template, such as `Template-rhcos-x-y`. Click the name of your vSphere cluster and select the folder. |
There was a problem hiding this comment.
Could we also clarify what x-y is in this context?
openshift-ci
bot
added
the
needs-rebase
mburke5678
force-pushed
the
mco-manual-boot-image-vshpere
branch
from
859ee69 to
9c43a24
Compare
openshift-ci
bot
removed
the
needs-rebase
mburke5678
force-pushed
the
mco-manual-boot-image-vshpere
branch
from
9c43a24 to
7c2e59b
Compare
|
@mburke5678: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
lgtm |
4 participants
Incorporate https://gist.github.com/djoshy/8d40754fe078b95701564cf73d9ee2a1 and https://access.redhat.com/articles/7053165#platform-specific-example---vsphere-6
https://redhat.atlassian.net/browse/OSDOCS-18794
Link to docs preview:
Manually updating the boot image on an vSphere cluster -- New module. Final location TBD.
QE review: