Upgrading Cisco ACI and OSP

Guidelines for Upgrading Cisco APIC and OSP

The OpenStack plug-in is released with Cisco Application Policy Infrastructure Controller APIC releases, and therefore uses the same semantic version as Cisco APIC. For example, the 5.1(1) plug-in is provided with the Cisco APIC 5.1(1) release. Generally, the OpenStack plug-in releases are tested against the matching Cisco APIC release, as well as the previous Long Term Support (LTS) Cisco APIC release. However, a given plug-in release may be compatible with additional Cisco APIC releases. See the Cisco ACI Virtualization Compatibility Matrix to verify that the version of the plug-in used is compatible with the version of Cisco APIC.

See the Cisco ACI Virtualization Compatibility Matrix for information about compatible Cisco APIC and Red Hat OSP releases.

Pre-upgrade Guidelines

Upgrade the Cisco Application Centric Infrastructure (ACI) plug-in.

For more information about the compatibility of the plug-in with various OpenStack versions, see the Cisco ACI Virtualization Compatibility Matrix.

Post-upgrade Guidelines

After you upgrade the Cisco Application Centric Infrastructure (ACI) fabric, you can optionally upgrade the OpenStack Cisco ACI packages to a version which is equal or lower than the Cisco ACI fabric code you have upgraded to. You should also refer to the OpenStack Cisco ACI plug-in Release Notes on Cisco.com for specific information.

For more information on how to upgrade the OpenStack Cisco ACI plug-in, see Upgrade the Cisco ACI Packages in this guide.

Upgrade the Cisco ACI Packages

The following procedure updates fully deployed Overcloud with the new version of the Cisco Application Centric Infrastructure (ACI) plug-in. The upgrade can be live.


Note
Follow the Red Hat Director documentation to upgrade the plug-in in step 4.

Procedure

Step 1

Copy the updated version of the tripeo-ciscoaci-version RPM and corresponding plug-in tarball (openstack-ciscorpms-repo) from Cisco.com to the OSP Director.

Step 2

Update the tripeo-ciscoaci-version package using yum: yum update tripleo-ciscoaci-

Step 3

Create the Cisco ACI containers by running the command by first logging into registry.connect.redhat.com using sudo podman login registry.connect.redhat.com and then running /opt/ciscoaci-tripleo-heat-templates/tools/build_openstack_aci_containers.py and then pointing it to the downloaded plug-in tarball. For example:

opt/ciscoaci-tripleo-heat-templates/tools/build_openstack_aci_containers.py -p -z/home/stack/openstack-ciscorpms-repo-163.0-848.tar.gz

The command updates the Docker images and updates the /home/stack/templates/cisco_containers.yaml file.

Note

 

To build the containers locally, you can omit the ‘-p’ option. These locally built containers may not be Red Hat certified. Log in to registry.redhat.io before building the containers.

Step 4

Follow the Red Hat upgrade procedure on the Red Hat Customer Portal.

See Chapter 4, "Updating the Overcloud" in the article Keeping Red Hat OpenStack Platform Updated. Go to Products & Services > Product Documentation > Red Hat OpenStack Platform > 16.2.