- play_arrow Installing and Upgrading Contrail
- play_arrow Understanding Contrail
- play_arrow Supported Platforms and Server Requirements
- play_arrow Contrail Command
- How to Install Contrail Command and Provision Your Contrail Cluster
- How to Login to Contrail Command
- Navigating the Contrail Command UI
- Installing a Contrail Cluster using Contrail Command and instances.yml
- Importing Contrail Cluster Data using Contrail Command
- Adding a New Compute Node to Existing Contrail Cluster Using Contrail Command
- How to Deploy Contrail Command and Import a Cluster Using Juju
- Importing a Canonical Openstack Deployment Into Contrail Command
- play_arrow Upgrading Contrail Software
- Upgrading Contrail Networking using Contrail Command
- Upgrading Contrail Command using Backup Restore Procedure
- How to Perform a Zero Impact Contrail Networking Upgrade using the Ansible Deployer
- Updating Contrail Networking using the Zero Impact Upgrade Process in an Environment using Red Hat Openstack 16.1
- Updating Contrail Networking using the Zero Impact Upgrade Process in an Environment using Red Hat Openstack 13
- Updating Contrail Networking using the Zero Impact Upgrade Procedure in a Canonical Openstack Deployment with Juju Charms
- Upgrading Contrail Networking using the Ansible Deployer In-Service Software Upgrade Procedure in OpenStack Environments
- Upgrading Contrail Networking using contrail-ansible Deployer
- Upgrading Contrail Networking using In-Place Upgrade Procedure
- Upgrading Contrail Networking Release 19xx with RHOSP13 to Contrail Networking Release 2011 with RHOSP16.1
- play_arrow Backup and Restore Contrail Software
- play_arrow Using Contrail Networking with VMware vCenter
- play_arrow VMware vCenter with Containerized Contrail Networking
-
- play_arrow Using Contrail Networking with OpenStack
- play_arrow Setting Up Contrail with Red Hat OpenStack 16.1
- play_arrow Setting Up Contrail with Red Hat OpenStack 13
- play_arrow Configuring Virtual Networks
- play_arrow Using Contrail Resources in Heat Templates
- play_arrow QoS Support in Contrail Networking
- play_arrow Load Balancers
- play_arrow Optimizing Contrail Networking
- play_arrow Contrail Networking OpenStack Analytics
- play_arrow Contrail OpenStack APIs
-
- play_arrow Using Contrail with Juju Charms
- Installing Contrail with OpenStack by Using Juju Charms
- Installing Contrail with Kubernetes by Using Juju Charms
- Installing Contrail with Kubernetes in Nested Mode by Using Juju Charms
- Installing OpenStack Octavia LBaaS with Juju Charms in Contrail Networking
- Using Netronome SmartNIC vRouter with Contrail Networking and Juju Charms
- play_arrow Using Contrail and Contrail Insights with Kolla/Ocata OpenStack
- Contrail, Contrail Insights, and OpenStack Kolla/Ocata Deployment Requirements
- Preparing for the Installation
- Run the Playbooks
- Accessing Contrail in Contrail Insights Management Infrastructure in UI
- Notes and Caveats
- Example Instances.yml for Contrail and Contrail Insights OpenStack Deployment
- Contrail Insights Installation and Configuration for OpenStack
- Contrail Insights Installation for OpenStack in HA
- play_arrow Post Installation Tasks
- Configuring Role and Resource-Based Access Control
- Configuring Role-Based Access Control for Analytics
- Configuring the Control Node with BGP
- Configuring MD5 Authentication for BGP Sessions
- Configuring Transport Layer Security-Based XMPP in Contrail
- Configuring Graceful Restart and Long-lived Graceful Restart
- Scaling Up Contrail Networking Configuration API Server Instances
- Scaling Up Contrail Networking Configuration API
-
Upgrading Contrail Networking Release 19xx with RHOSP13 to Contrail Networking Release 2011 with RHOSP16.1
The goal of this topic is to provide a combined procedure to upgrade Red Hat OpenStack Platform (RHOSP) from RHOSP 13 to RHOSP 16.1 by leveraging Red Hat Fast Forward Upgrade (FFU) procedure while simultaneously upgrading Contrail Networking from Release 19xx to Release 2011. The procedure leverages the Zero Impact Upgrade (ZIU) procedure from Contrail to minimize the downtime.
The downtime will be reduced by not requiring extra server reboots in addition to the ones that the RHOSP FFU procedure already requires for Kernel/RHEL upgrades.
Refer to Red Hat OpenStack Framework for Upgrades (13 to16.1) documentation for details on RHOSP 13 to RHOSP 16.1 Fast Forward Upgrade (FFU) procedure of OpenStack Platform environment from one long life version to the next long life version.
Access ContrailImageTag located at README Access to Contrail Registry 20XX.
- Follow chapter 2—Planning and preparation for an in-place upgrade through chapter 8.3— Copying the Leapp data to the overcloud nodes of Red Hat OpenStack Framework for Upgrades (13 to16.1) procedure.
- Use predictable NIC names for overcloud nodes
- Log in to the undercloud as the stack user.
- Run the playbook-nics.yaml playbook on all overcloud nodes.
$ ansible-playbook -i ~/inventory.yaml playbook-nics.yamlThe playbook sets the new NIC prefix to
em. To set a different NIC prefix, set the prefix variable when running the playbook:$ ansible-playbook -i ~/inventory.yaml -e prefix="mynic" playbook-nics.yaml - Run the playbook-nics-vhost0.yaml playbook on all overcloud compute nodes.
$ ansible-playbook -i ~/inventory.yaml -l overcloud_Compute $my_dir/playbook-nics-vhost0.yamlFor details, see https://github.com/tungstenfabric/tf-deployment-test/blob/master/rhosp/ffu_ziu_13_16/tf_specific/playbook-nics-vhost0.yaml.
- Reboot overcloud nodes using the standard reboot procedures. For more information, see Red Hat rebooting nodes documentation.
- Follow chapter 8.3—Copying the Leapp data to the overcloud nodes through chapter 19.2—Upgrading Controller nodes with external Ceph deployments of Red Hat OpenStack Framework for Upgrades (13 to16.1) procedure.
- Upgrade compute nodes to OpenStack Platform 16.1.Note:
If you are not using the default stack name (overcloud), set your stack name with the --stack STACK NAME option replacing STACK NAME with the name of your stack.
- Source the stackrc file.
$ source ~/stackrc - Migrate your instances. For details, see RedHat Migrating virtual machine instances between Compute nodes documentation.
- Run the upgrade command with the
system_upgrade_prepareandsystem_upgrade_runtags.$ openstack overcloud upgrade run --stack STACK NAME --tags system_upgrade_prepare --limit overcloud-compute-0$ openstack overcloud upgrade run --stack STACK NAME --tags system_upgrade_run --limit overcloud-compute-0To upgrade multiple Compute nodes in parallel, set the
--limitoption to a comma-separated list of nodes that you want to upgrade. - Run the upgrade command with no tags to perform Red Hat
OpenStack Platform upgrade.
$ openstack overcloud upgrade run --stack STACK NAME --limit overcloud-compute-0
- Source the stackrc file.
- Follow chapter 19.4—Synchronizing the
overcloud stack through chapter 21.4—Synchronizing
the overcloud stack of Red Hat OpenStack Framework for Upgrades (13 to16.1) procedure
to complete the upgrade.Note:
To speed up the overcloud upgrade process, you can upgrade 1/3 of the control plane at a time, starting with the bootstrap nodes. For details, see Speeding Up An Overcloud Upgrade.