updated post-adoption task #1179
Conversation
| * Optional: Run tempest to verify that the entire adoption process is working properly. For more information, see link:{defaultURL}/validating_and_troubleshooting_the_deployed_cloud/index[Validating and troubleshooting the deployed cloud]. | ||
| * Optional: Perform a minor update from RHEL 9.2 to 9.4. You can perform a minor update any time after you complete the adoption procedure. For more information, see link:{defaultURL}/updating_your_environment_to_the_latest_maintenance_release/index[Updating your environment to the latest maintenance release]. | ||
| * Optional: Run tempest to verify that the entire adoption process is working properly. For more information, see link:https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/validating_and_troubleshooting_the_deployed_cloud/index[Validating and troubleshooting the deployed cloud]. | ||
| * After adoption, {rhos_long} data plane nodes run Red Hat Enterprise Linux (RHEL) 9.2. The data plane nodes can remain on RHEL 9.2; however, you must perform a system update for full functionality. You can perform a system update any time after you complete the adoption procedure. For more information about updating your environment, see link:https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/updating_your_environment_to_the_latest_maintenance_release/index[Updating your environment to the latest maintenance release]. |
There was a problem hiding this comment.
'for full functionality'
Can we rather say something more like 'to use the full feature set from the release' or perhaps 'for full feature functionality' ?
There was a problem hiding this comment.
Can we also specifically mention that the system update can be done in a separate maintenance window?
Something like 'the system update can be deferred to another maintenance window'.
Lastly, I think it makes sense to also state that the system updates can be done NodeSet by NodeSet?
We have some wording from the split update documentation that we can reuse or incorporate here that covers all these points.
There was a problem hiding this comment.
In addition to enabling the full feature set, updating the data plane nodes to RHEL 9.4 aligns the environment with the maximum support lifecycle of Red Hat OpenStack Services on OpenShift. This could be called out as another reason to plan the system update after adoption.
klgill
force-pushed
the
docs-revise-post-adoption-task
branch
2 times, most recently
from
0386f23 to
a05f2ef
Compare
klgill
force-pushed
the
docs-revise-post-adoption-task
branch
from
c472a49 to
5397664
Compare
klgill
force-pushed
the
docs-revise-post-adoption-task
branch
from
5397664 to
244ab1b
Compare
| * Optional: Run tempest to verify that the entire adoption process is working properly. For more information, see link:{defaultURL}/validating_and_troubleshooting_the_deployed_cloud/index[Validating and troubleshooting the deployed cloud]. | ||
| * Optional: Perform a minor update from RHEL 9.2 to 9.4. You can perform a minor update any time after you complete the adoption procedure. For more information, see link:{defaultURL}/updating_your_environment_to_the_latest_maintenance_release/index[Updating your environment to the latest maintenance release]. | ||
| * Optional: Run tempest to verify that the entire adoption process is working correctly. For more information, see link:https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/validating_and_troubleshooting_the_deployed_cloud/index[Validating and troubleshooting the deployed cloud]. | ||
| * After adoption, {rhos_long} data plane nodes run Red Hat Enterprise Linux (RHEL) 9.2. The data plane nodes can remain on RHEL 9.2; however, you must perform a system update to use the full feature set from the release, and to align your environment with the maximum support lifecycle of {rhos_acro}. |
There was a problem hiding this comment.
@pnavarro What do you think of the latest change on line 28?
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
openshift-merge-bot
bot
merged commit 8386d79
into
openstack-k8s-operators:main
4 participants
https://issues.redhat.com/browse/OSPRH-17349