Expected adoption timelines and workload impact

Learn about the durations of each adoption stage so you can plan enough time to complete the adoption. To accurately estimate the duration for each task, perform these procedures in a test environment with similar hardware to your production environment.

Set up the Red Hat OpenShift Container Platform (RHOCP) environment and install the Operators before testing.

Important
The durations in the following table were recorded in a test environment that consisted of 228 Compute nodes and 3 Networker nodes. Durations can vary significantly based on the content of your environment, for example, the size of your service databases or the number of services. The durations represent raw execution time. They do not include human operator activity.
Table 1. Duration and impact of adoption stages
Adoption stage Duration Notes

TLS-e migration

  • 3 seconds
  • No impact on running workloads.

Database migration and back-end services deployment

  • 12 minutes
  • No data loss or workload disruption.
  • APIs are offline.

Control plane adoption

  • 21 minutes
  • No data loss or workload disruption.
  • APIs are being started.
  • No Compute hosts are available to schedule workloads until the data plane adoption stage.
  • No network changes should be done until the data plane adoption is complete.

Data plane adoption

  • 60 minutes
  • APIs are online.
  • As Compute hosts are adopted, they become available for workload scheduling.
  • No data loss or workload disruption.

Fast-forward upgrade of Compute services

  • 8 minutes
  • No data loss or workload disruption.

Networker node adoption

  • 9 minutes
  • See the following "Data plane connectivity impact" table for more details about Networker scenarios.
Table 2. Data plane connectivity impact
Scenario Notes

Migrate a 17.1 OVN gateway on the control plane to a RHOCP-hosted OVN gateway

Possible L3 downtime due to the migration of the traffic path to new hosts

Migrate a 17.1 OVN gateway on the control plane to an 18.0 data plane Networker node

No L2/L3 data plane connectivity loss because the traffic path remains unchanged

Migrate a 17.1 OVN gateway on a Networker node to a 18.0 data plane Networker node

No L2/L3 data plane connectivity loss because the traffic path remains unchanged

L3 handled through provider networks

No L2/L3 data plane connectivity loss because the traffic path remains unchanged