Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Upgrade Contrail Service Orchestration from Release 6.1.0 to Release 6.3.0

Contrail Analytics Nodes (CAN) for CSO Release 6.3.0 run on CentOS version 7.7.1908.

Note:

Before you upgrade an on-premise deployment to CSO Release 6.3.0, ensure that

  • All sites are running version 6.1.0 and the supported Junos OS release.

  • All VMs have Internet connectivity. Internet connectivity is needed to verify the ESM license.

Upgrade Contrail Service Orchestration for KVM and ESXi Hypervisors

Prerequisites

  • For ESXi hypervisors, create three new VMs for the streaming feature. See Provision VMs on Contrail Service Orchestration Servers.

  • You must have at least 40 GB in the / partition in the startupserver1 VM to run the upgrade script.

  • You must not delete previously installed CSO 6.1.0 folder from the startupserver VM.

If you opted for the streaming feature, then complete the following steps:

  • Configure the three physical servers for HA setup (if streaming is opted). Ensure that all the prerequisites are met. For details, see Provision VMs on Contrail Service Orchestration Servers. Ensure that these three physical servers can connect to the existing CSO servers.

  • Create a bridge interface for KVM hypervisors. For details, see Create a Bridge Interface for KVM Hypervisors. You must assign new IP addresses.

  • Modify the main Apt sources configuration file on the new physical servers to connect the Debian sources.list to the Internet.

    root@host:~/# cp /etc/apt/orig-sources.list /etc/apt/sources.list

    You do not need to modify the file if Debian sources.list is connected to the Ubuntu repository.

  • Run the setup_bms.sh script on all the three new physical servers.

  • Run the following commands from the CSO folder:

    root@host:~/Contrail_Service_Orchestration_6.3.0# cd ci_cd

    root@host:~/Contrail_Service_Orchestration_6.3.0# ./setup_bms.sh

    Note:

    If you run the setup_bms.sh script after creating the bridge interface, you might see the error meesage device br0 already exists; can't create bridge with the same name. You can ignore the error message.

Follow this procedure to upgrade from CSO Release 6.1.0 to CSO Release 6.3.0.

  1. Download the CSO Release 6.3.0 installer package from the CSO Downloads page to the startupserver1 VM.
  2. Log in to the startupserver1 VM as root.
  3. On the startupserver1 VM, extract the installer package.

    For example, if the name of the installer package is Contrail_Service_Orchestration_6.3.0.tar.gz,

    The contents of the installer package are extracted in a directory with the same name as the installer package.

  4. Navigate to the Contrail_Service_Orchestration_6.3.0 directory and remove the csp-routing-manager option from the ms_execution_sequence file.

    Verify that the csp-routing-manager option is removed from the ms_execution_sequence file.

  5. Back up the Elasticsearch data.

    The upgrade script retains all microservice data, and a day's data of junoslogs and joblogs. You must back up and restore other data (older joblogs and junoslogs). To back up the data, you need the esm and es_migration files. These files are available in the Contrail_Service_Orchestration_6.3.0 directory.

    1. Copy the esm and es_migration files to /usr/local/bin.

    2. Navigate to the /usr/local/bin folder and extract the esm file.

    3. Change the permission for both the files to 755.

    4. Back up junoslogs and joblogs data older than one day.

  6. Navigate to the CSO Release 6.3.0 directory in the startupserver1 VM.
  7. You can view the list of files in the Contrail_Service_Orchestration_6.3.0.

    The Contrail_Service_Orchestration_6.3.0.tar.tz file includes the upgrade.sh script.

  8. Run the upgrade.sh script.
    Warning:

    Before you upgrade ensure that all ongoing jobs in the Administration Portal and Customer Portal are stopped; otherwise, the upgrade process will fail.

    Confirm if you have the Ubuntu ESM license. This license is required to obtain the security updates. If you do not have the license, contact Juniper support.

    Enter the IP addresses and password for the three new physical servers when prompted. This prompt appears only if you opted for the streaming services feature.

    For ESXi hypervisors, enter the IP addresses of the VMs.

    For KVM hypervisors, enter the host IP addresses.

    Depending on your deployment, it may take 60 minutes to 120 minutes to complete this task.

    You can view the upgrade.log file which is available at root/Contrail_Service_Orchestration_6.3.0/logs folder.

    If an error occurs, you must fix the error and re-run the upgrade.sh script. When you re-run the upgrade.sh script, the script continues to execute from the previously failed step.

    If it fails after 2 attempts, contact Juniper Networks support for further assistance.

    You can run ./python.sh deploy_manager/utils/decrypt_password.py command to decrypt the passwords for each infrastructure component.

  9. Restore the Elasticsearch logs that you backed up in Step 5.

After a successful upgrade, CSO is functional and you can log in to the Administrator Portal and the Customer Portal.