Upgrade the OpenContrail nodes from version 3.2 to 4.1

Upgrade the OpenContrail nodes from version 3.2 to 4.1

Caution

Before proceeding with the upgrade procedure, verify that you have updated DriveTrain including Aptly, Gerrit, Jenkins, Reclass, Salt formulas, and their subcomponents to the current MCP release version. Otherwise, the current MCP product documentation is not applicable to your MCP deployment.

This section describes how to upgrade the OpenContrail nodes of an Ocata- or Pike-based MCP cluster to version 4.1 using the Deploy - upgrade Opencontrail to 4.x pipeline. To update OpenContrail from version 4.0 to 4.1, refer to Update the OpenContrail 4.x nodes.

Note

Upgrade the OpenContrail cluster before the OpenStack upgrade.

Warning

The OpenContrail data plane traffic will be affected during the upgrade procedure since restarting of a vRouter agent leads to connectivity interruption. Plan migrations of the critical workloads accordingly before the vRouter agent restart.

The OpenContrail upgrade to version 4.1 is available only from version 3.2. Therefore, if you have an older OpenContrail version, for example, 3.2.3 or 3.1.1, first update the OpenContrail packages on the OpenContrail nodes to the latest supported 3.2.x version using the Update the OpenContrail 3.2 package procedure.

The high-level workflow of the OpenContrail upgrade pipeline job is as follows:

  1. Verify the OpenContrail services statuses.

  2. Stop the Neutron API that will be unavailable during the whole upgrade procedure.

  3. Back up the Cassandra and ZooKeeper data.

  4. Stop all running OpenContrail analytics services.

  5. Upgrade or update the OpenContrail analytics nodes simultaneously. During upgrade, new Docker containers for the OpenContrail analytics nodes are spawned. During update, the corresponding Docker images are updated.

  6. Upgrade or update the OpenContrail controller nodes. During upgrade, new Docker containers for the OpenContrail controller nodes are spawned. During update, the corresponding Docker images are updated. All nodes are upgraded or updated simultaneously except the one that meantime runs the contrail-control service and is upgraded or updated after other nodes.

  7. Upgrade the OpenContrail packages on the OpenStack controller nodes simultaneously.

  8. Start the Neutron server services.

  9. Upgrade the OpenContrail data plane nodes one by one with the workloads migration if needed since this step implies downtime of the Networking service.

  10. Verify the OpenContrail services statuses.