1. Home
  2. MCP Operations Guide
  3. Upgrade and update an MCP cluster
  4. Update an MCP cluster
  5. Update the OpenContrail 4.x nodes
  6. Update the OpenContrail nodes

Update the OpenContrail nodes

Update the OpenContrail nodesΒΆ

After you prepare the cluster model of your MCP cluster, proceed to updating the OpenContrail controller nodes and the OpenContrail vRouter packages on the compute nodes.

Warning

During the update process, the following resources are affected:

  • The instance(s) running on the compute nodes can be unavailable for up to 30 seconds.
  • The creation of new instances is not possible during the same time interval.

Therefore, you must plan a maintenance window as well as test the update on a staging environment before applying it to production.

To update the OpenContrail nodes:

  1. Log in to the Jenkins web UI.

  2. Verify that you do not have any unapproved scripts in Jenkins:

    1. Navigate to Manage Jenkins > In-process script approval.
    2. Approve pending scripts if any.

  3. Open the Deploy - update Opencontrail 4X pipeline.

  4. Specify the following parameters:

    Parameter Description and values
    SALT_MASTER_CREDENTIALS The Salt Master credentials to use for connection, defaults to salt.
    SALT_MASTER_URL The Salt Master node host URL with the salt-api port, defaults to the jenkins_salt_api_url parameter. For example, http://172.18.170.27:6969.
    STAGE_CONTROLLERS_UPDATE Select to update the OpenContrail controller nodes.

  5. Click Deploy.

To update the OpenContrail vRouter packages on the compute nodes:

  1. Log in to the Jenkins web UI.

  2. Open the Deploy - update Opencontrail 4X pipeline.

  3. Specify the following parameters:

    Parameter Description and values
    COMPUTE_TARGET_SERVERS Add I@opencontrail:compute or target the global name of your compute nodes, for example cmp001*.
    COMPUTE_TARGET_SUBSET_LIVE Add 1 to run the update first on only one of the nodes defined in the COMPUTE_TARGET_SERVERS field. After this stage is done, in the pipeline job console, you will be asked to continue the update the remaining nodes defined in the COMPUTE_TARGET_SERVERS field.
    SALT_MASTER_CREDENTIALS The Salt Master credentials to use for connection, defaults to salt.
    SALT_MASTER_URL The Salt Master node host URL with the salt-api port, defaults to the jenkins_salt_api_url parameter. For example, http://172.18.170.27:6969.
    STAGE_COMPUTES_UPDATE Select to update the compute nodes.

  4. Click Deploy. For details how to monitor the deployment process, see: MCP Deployment Guide: View the deployment details.

  5. Log in to the Salt Master node.

  6. Restart the vrouter-agent and vrouter-nodemgr services on the OpenContrail compute nodes:

    salt -C 'I@opencontrail:compute' service.restart contrail-vrouter-agent
salt -C 'I@opencontrail:compute' service.restart contrail-vrouter-nodemgr

The Deploy - update Opencontrail 4X pipeline workflow:

  1. If STAGE_COMPUTES_UPDATE is selected, update the OpenContrail packages on the compute nodes in two iterations:
    1. Update the sample nodes defined by COMPUTE_TARGET_SUBSET_LIVE.
    2. After a manual confirmation, update all compute nodes targeted in COMPUTE_TARGET_SERVERS.
  2. If STAGE_CONTROLLERS_UPDATE is selected, download a new version of controller, analytics, and analytics db containers.
  3. Stop the running analytics and analytics db containers on nal nodes and start the updated containers.
  4. Stop the running controller containers on ntw nodes and start the updated containers.

See also

MCP 2019.2.3 Maintenance Update: Known issues

updated: 2024-09-16 10:21