{rhos_long_noacro} {rhos_curr_ver} adoption overview

Adoption is the process of migrating a {rhos_prev_long} ({OpenStackShort}) {rhos_prev_ver} overcloud to a {rhos_long_noacro} {rhos_curr_ver} data plane. To ensure that you understand the entire adoption process and how to sufficiently prepare your {OpenStackShort} environment, review the prerequisites, adoption process, and post-adoption tasks.

Guidelines for planning the adoption

When planning to adopt a {rhos_long} {rhos_curr_ver} environment, consider the scope of the change. An adoption is similar in scope to a data center upgrade. Different firmware levels, hardware vendors, hardware profiles, networking interfaces, storage interfaces, and so on affect the adoption process and can cause changes in behavior during the adoption.

Review the following guidelines to adequately plan for the adoption and increase the chance that you complete the adoption successfully:

All commands in the adoption documentation are examples. Do not copy and paste the commands without understanding what the commands do.

  • To minimize the risk of an adoption failure, reduce the number of environmental differences between the staging environment and the production sites.

  • If the staging environment is not representative of the production sites, or a staging environment is not available, then you must plan to include contingency time in case the adoption fails.

  • Review your custom {rhos_prev_long} ({OpenStackShort}) service configuration at every major release.

    • Every major release upgrades through multiple OpenStack releases.

    • Each major release might deprecate configuration options or change the format of the configuration.

  • Prepare a Method of Procedure (MOP) that is specific to your environment to reduce the risk of variance or omitted steps when running the adoption process.

  • You can use representative hardware in a staging environment to prepare a MOP and validate any content changes.

    • Include a cross-section of firmware versions, additional interface or device hardware, and any additional software in the representative staging environment to ensure that it is broadly representative of the variety that is present in the production environments.

    • Ensure that you validate any Red Hat Enterprise Linux update or upgrade in the representative staging environment.

  • Use Satellite for localized and version-pinned RPM content where your data plane nodes are located.

  • In the production environment, use the content that you tested in the staging environment.

Adoption process overview

Familiarize yourself with the steps of the adoption process and the optional post-adoption tasks.

Main adoption process

  1. Migrate your existing databases to the new control plane.

  2. Adopt your Red Hat OpenStack Platform 17.1 control plane services to the new RHOSO 18.0 deployment

  3. Adopt the RHOSO 18.0 data plane.