- 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 Command using Backup Restore Procedure
You cannot use the SQL data with the new version of Contrail Command container if the database schema changes while upgrading the Contrail Command container.
You can resolve the issue by:
- Back up SQL database in yaml format db
dump.
Run the following docker exec contrail_command command on the Contrail Command node to backup the DB.
Contrail Networking Release 2005 or later:
docker exec contrail_command commandutil convert --intype rdbms --outtype yaml --out /etc/contrail/db.yml -c /etc/contrail/command-app-server.yml; mkdir ~/backups; mv /etc/contrail/db.yml ~/backups/
Contrail Networking Release 2003 or earlier:
docker exec contrail_command contrailutil convert --intype rdbms --outtype yaml --out /etc/contrail/db.yml -c /etc/contrail/contrail.yml; mkdir ~/backups; mv /etc/contrail/db.yml ~/backups/
- Upgrade the Contrail Command container.
Specify the desired version of Contrail Command container (container_tag) in the deployer input file (command_servers.yml) and deploy playbook.
You must use PostgreSQL in the command_servers.yml file.
The step depends on how you have deployed the Contrail Command.
Contrail Command is deployed using docker installation:
docker run -td --net host -v <ABSOLUTE_PATH_OF_COMMAND_SERVERS_FILE>:/command_servers.yml --privileged --name contrail_command_deployer_<contrail_container_tag> hub.juniper.net/contrail/contrail-command-deployer:<<contrail_container_tag>
Contrail Command is deployed through juju-charms:
juju config contrail-command image-tag=<contrail_container_tag>
After entering this command, enter the juju config contrail-command image-tag command to ensure the Contrail Command container is associated with the new image tag.
If the command output displays the old image tag, wait several minutes then retry the juju config contrail-command image-tag command.
If the command output displays the new image tag, proceed to the next step. If the command output continues to display the old image tag, re-enter the juju config contrail-command image-tag=contrail_container_tag to upgrade the container.
The contrail_container_tag for any Contrail Release 20 software can be obtained from README Access to Contrail Networking Registry 20xx.
- This
step depends on your Contrail Networking release.
Contrail Networking Release 2005 or later:
Migrate the yaml formatted db dump to the new database schema:
content_copy zoom_out_mapdocker exec contrail_command mkdir /root/backups docker cp /root/backups/db.yml contrail_command:/root/backups/ docker exec contrail_command commandutil migrate --in /root/backups/db.yml --out /root/backups/db_migrated.yml
Contrail Networking Release 2003 or earlier:
Modify the yaml-formatted db dump by adding or removing the fields per the new database schema.
- Restore
the modified yaml formatted db dump to the SQL database.
Contrail Networking Release 2005 or later:
content_copy zoom_out_mapdocker exec contrail_command commandutil convert --intype yaml --in /root/backups/db_migrated.yml --outtype rdbms -c /etc/contrail/command-app-server.yml
Contrail Networking Release 2003 or earlier:
content_copy zoom_out_mapdocker exec contrail_command mkdir /root/backups docker cp /root/backups/db.yml contrail_command:/root/backups/ docker exec contrail_command contrailutil convert --intype yaml --in ~/backups/db.yml --outtype rdbms -c /etc/contrail/contrail.yml