Upgrade CCO

 

One Time Prerequisite

As a one-time task for all OS configurations, you must tighten the security configuration for the Load balancer VMs to ensure security compliance. See the Security Hardening Requirements section in the Upgrade Overview section for additional context.

CCO Non-HA

Upgrade CCO

To upgrade CCO, follow this procedure.

  1. SSH into the CCO instance.

  2. Download the following files in /tmp folder of CCO.

    • core_upgrade.bin

    • cco-installer.jar

    • cco-response.xml

  3. Run the core upgrade to upgrade CCO system components using the following commands (effective CloudCenter 4.10.0.6).

    sudo -i
    cd /tmp
    chmod 755 core_upgrade.bin
     
    ./core_upgrader.bin <OS> <Cloud> os_upgrade
  4. Upgrade MongoDB – Updating MongoDB is a two-step process (effective CloudCenter 4.10.0.6):

    1. Upgrading MongoDB from 3.4 to 3.6

      1. Perform the following steps to upgrade the MongoDB:

      2. Drop into the MongoDB shell. This will lead your primary prompt for the primary node of your cluster as shown below:

        setname:PRIMARY>
      3. For the remaining nodes, the drop will lead to a secondary prompt as shown below:

        setname:SECONDARY> 
      4. Run the following command on all nodes:

        db.adminCommand( { getParameter: 1, featureCompatibilityVersion: 1 } )
      5. Ensure that the output is as shown below:

        { "featureCompatibilityVersion" : "3.4", "ok" : 1 }
      6. On each secondary node, run the following command to upgrade the mongo binaries to 3.6:

        core_upgrader.bin centos7 vmware mongo
        This upgrades the secondary nodes to 3.6. 
      7. On the primary node, drop into the MongoDB shell and enter the following command:

        setname:PRIMARY>rs.stepDown()
      8. Exit the shell and run the following command to upgrade the MongoDB binaries on the primary node:

        core_upgrader.bin centos7 vmware mongo
      9. Find the newly selected primary shell. The prompt on entering "mongo" displays the following for the newly selected primary node:

        setname:PRIMARY>
      10. Drop into the shell of this primary node and run the following command:

        setname:PRIMARY> db.adminCommand( { setFeatureCompatibilityVersion: "3.6" } ) 

        At this point, your MongoDB is upgraded to 3.6.

    2. Upgrading MongoDB from 3.6 to 4.0 – Perform the following steps to upgrade the MongoDB:

      1. Drop into the MongoDB shell to indicate if the node is primary or secondary.

      2. Drop into the MongoDB shell on each node and run the following command:

        db.adminCommand( { getParameter: 1, featureCompatibilityVersion: 1 } )
      3. Ensure that the output is as shown below. The version must be 3.6.

        { "featureCompatibilityVersion" : "3.6", "ok" : 1 }
      4. On the primary node, drop into the mongo shell and run the following commands:

        setname:PRIMARY>cfg=rs.conf();
        setname:PRIMARY> cfg.protocolVersion=1;
        setname:PRIMARY>rs.reconfig(cfg);
      5. Upgrade the MongoDB binaries on each secondary node using the following command:

        core_upgrader.bin centos7 vmware mongo
      6. On the primary node, drop into the MongoDB shell and enter the following command:

        setname:PRIMARY>rs.stepDown()
      7. Exit the shell and run the following command to upgrade the MongoDB binaries on the primary node:

        core_upgrader.bin centos7 vmware mongo
      8. Find the newly selected primary shell. The prompt on entering "mongo" displays the following for the newly selected primary node:

        setname:PRIMARY>
      9. Drop into the shell of this primary node and run the following command:

        setname:PRIMARY> db.adminCommand( { setFeatureCompatibilityVersion: "4.0" } ) 
      10. All nodes are in version 4.0.17. You can confirm by running following command on the mongo shell on each node:

        db.adminCommand( { getParameter: 1, featureCompatibilityVersion: 1 } )
      11. The output must be as follows:

        { "featureCompatibilityVersion" : "4.0", "ok" : 1 } 
  5. Run the core upgrade to upgrade CCO system components using the following commands.

    sudo -i
    cd /tmp
    chmod 755 core_upgrade.bin
     
    #Set the following only if a local store is setup
    export CUSTOM_REPO=<http://local_package_store IP>
     
    ./core_upgrade.bin <ostype> <cloud> cco
  6. Run the appliance installer to upgrade CCO.

    java -jar cco-installer.jar cco-response.xml
  7. Update the agent bundle URL in the CCO.

    This step is conditional and is required only when the local bundle server or REPO is used in the setup.

    1. SSH into CCO instance.

    2. Run the cco_config_wizard.

      sudo -i
      /usr/local/cliqr/bin/cco_config_wizard.sh
    3. Set the Agent bundle URL.

      After an upgrade the agent bundle URL value reverts to the default URL, cdn.cliqr.com, and your previously-configured value is not retained.

      If you upload new files to the repo, you must manually update the agent bundle URL in the CCM wizard to reflect the customized repo URL.

      #Agent bundle URL -- Only use HTTP protocol 
      http://your_HTTP_server/release-<version>/bundle/
    4. Exit the CCO wizard

You have now completed the CCO upgrade.

CCO HA

You must stop the gateway service on all three CCOs before upgrading to any CloudCenter version.

Run the core_upgrade and appliance files one after the other – do not run them in parallel!

Upgrading in HA Mode

When upgrading CCOs in HA mode, you MUST stop all the CCOs.

Upgrade CCO_PRIMARY

To upgrade CCO_PRIMARY, follow this procedure.

  1. SSH into the CCO_PRIMARY instance.

  2. Download the following files in /tmp folder of CCO.

    • core_upgrade.bin

    • cco-installer.jar

    • cco-response.xml

  3. Run the core upgrade to upgrade CCO system components using the following commands (effective CloudCenter 4.10.0.6).

    sudo -i
    cd /tmp
    chmod 755 core_upgrade.bin
     
    ./core_upgrader.bin <OS> <Cloud> os_upgrade
  4. Upgrade MongoDB – Updating MongoDB is a two-step process (effective CloudCenter 4.10.0.6):

    1. Upgrading MongoDB from 3.4 to 3.6

      1. Perform the following steps to upgrade the MongoDB:

      2. Drop into the MongoDB shell. This will lead your primary prompt for the primary node of your cluster as shown below:

        setname:PRIMARY>
      3. For the remaining nodes, the drop will lead to a secondary prompt as shown below:

        setname:SECONDARY> 
      4. Run the following command on all nodes:

        db.adminCommand( { getParameter: 1, featureCompatibilityVersion: 1 } )
      5. Ensure that the output is as shown below:

        { "featureCompatibilityVersion" : "3.4", "ok" : 1 }
      6. On each secondary node, run the following command to upgrade the mongo binaries to 3.6:

        core_upgrader.bin centos7 vmware mongo
        This upgrades the secondary nodes to 3.6. 
      7. On the primary node, drop into the MongoDB shell and enter the following command:

        setname:PRIMARY>rs.stepDown()
      8. Exit the shell and run the following command to upgrade the MongoDB binaries on the primary node:

        core_upgrader.bin centos7 vmware mongo
      9. Find the newly selected primary shell. The prompt on entering "mongo" displays the following for the newly selected primary node:

        setname:PRIMARY>
      10. Drop into the shell of this primary node and run the following command:

        setname:PRIMARY> db.adminCommand( { setFeatureCompatibilityVersion: "3.6" } ) 

        At this point, your MongoDB is upgraded to 3.6.

    2. Upgrading MongoDB from 3.6 to 4.0 – Perform the following steps to upgrade the MongoDB:

      1. Drop into the MongoDB shell to indicate if the node is primary or secondary.

      2. Drop into the MongoDB shell on each node and run the following command:

        db.adminCommand( { getParameter: 1, featureCompatibilityVersion: 1 } )
      3. Ensure that the output is as shown below. The version must be 3.6.

        { "featureCompatibilityVersion" : "3.6", "ok" : 1 }
      4. On the primary node, drop into the mongo shell and run the following commands:

        setname:PRIMARY>cfg=rs.conf();
        setname:PRIMARY> cfg.protocolVersion=1;
        setname:PRIMARY>rs.reconfig(cfg);
      5. Upgrade the MongoDB binaries on each secondary node using the following command:

        core_upgrader.bin centos7 vmware mongo
      6. On the primary node, drop into the MongoDB shell and enter the following command:

        setname:PRIMARY>rs.stepDown()
      7. Exit the shell and run the following command to upgrade the MongoDB binaries on the primary node:

        core_upgrader.bin centos7 vmware mongo
      8. Find the newly selected primary shell. The prompt on entering "mongo" displays the following for the newly selected primary node:

        setname:PRIMARY>
      9. Drop into the shell of this primary node and run the following command:

        setname:PRIMARY> db.adminCommand( { setFeatureCompatibilityVersion: "4.0" } ) 
      10. All nodes are in version 4.0.17. You can confirm by running following command on the mongo shell on each node:

        db.adminCommand( { getParameter: 1, featureCompatibilityVersion: 1 } )
      11. The output must be as follows:

        { "featureCompatibilityVersion" : "4.0", "ok" : 1 } 
  5. Run the core upgrade to upgrade CCO_PRIMARY system components using the following commands.

    sudo -i
    cd /tmp
    chmod 755 core_upgrade.bin
     
    #Set the following only if a local store is setup
    export CUSTOM_REPO=<http://local_package_store IP>
     
    ./core_upgrade.bin <ostype> <cloud> cco
  6. Run the appliance installer to upgrade CCO_PRIMARY.

    java -jar cco-installer.jar cco-response.xml
  7. Update the agent bundle URL in the CCO.

    This step is conditional and is required only when the local bundle server or REPO is used in the setup.


    1. SSH into CCO instance.

    2. Run the cco_config_wizard.

      sudo -i
      /usr/local/cliqr/bin/cco_config_wizard.sh
    3. Set the Agent bundle URL.

      After an upgrade the agent bundle URL value reverts to the default URL, cdn.cliqr.com, and your previously-configured value is not retained.

      If you upload new files to the repo, you must manually update the agent bundle URL in the CCM wizard to reflect the customized repo URL.

      #Agent bundle URL
      http://your_HTTP_server/release-<version>/bundle/
    4. Exit the CCO wizard

You have now completed the CCO_PRIMARY upgrade.

Upgrade CCO_SECONDARY

To upgrade CCO_SECONDARY, follow this procedure.

follow this procedure.

  1. SSH into the CCO_SECONDARY instance.

  2. Download the following files in /tmp folder of CCO.

    • core_upgrade.bin

    • cco-installer.jar

    • cco-response.xml
  3. Run the core upgrade to upgrade CCO_SECONDARY system components using the following commands.

    sudo -i
    cd /tmp
    chmod 755 core_upgrade.bin
     
    #Set the following only if a local store is setup
    export CUSTOM_REPO=<http://local_package_store IP>
     
    ./core_upgrade.bin <ostype> <cloud> cco
  4. Run the appliance installer to upgrade CCO_SECONDARY.

    java -jar cco-installer.jar cco-response.xml
  5. Update the agent bundle URL in the CCO.

    This step is conditional and is required only when the local bundle server or REPO is used in the setup.

    1. SSH into CCO instance.

    2. Run the cco_config_wizard.

      sudo -i
      /usr/local/cliqr/bin/cco_config_wizard.sh
    3. Set the Agent bundle URL.

      After an upgrade the agent bundle URL value reverts to the default URL, cdn.cliqr.com, and your previously-configured value is not retained.

      If you upload new files to the repo, you must manually update the agent bundle URL in the CCM wizard to reflect the customized repo URL.

      #Agent bundle URL
      http://your_HTTP_server/release-<version>/bundle/
    4. Exit the CCO wizard

You have now completed the CCO_SECONDARY upgrade.

Upgrade CCO_TERTIARY

To upgrade CCO_TERTIARY, follow this procedure.

  1. SSH into the CCO_TERTIARY instance.

  2. Download the following files in /tmp folder of CCO.

    • core_upgrade.bin

    • cco-installer.jar

    • cco-response.xml
  3. Run the core upgrade to upgrade CCO_TERTIARY system components using the following commands.

    sudo -i
    cd /tmp
    chmod 755 core_upgrade.bin
     
    #Set the following only if a local store is setup
    export CUSTOM_REPO=<http://local_package_store IP>
     
    ./core_upgrade.bin <ostype> <cloud> cco
  4. Run the appliance installer to upgrade CCO_TERTIARY.

    java -jar cco-installer.jar cco-response.xml
  5. Update the agent bundle URL in the CCO.

    This step is conditional and is required only when the local bundle server  or REPO is used in the setup.

    1. SSH into CCO instance.

    2. Run the cco_config_wizard.

      sudo -i
      /usr/local/cliqr/bin/cco_config_wizard.sh
    3. Set the Agent bundle URL.

      After an upgrade the agent bundle URL value reverts to the default URL, cdn.cliqr.com, and your previously-configured value is not retained.

      If you upload new files to the repo, you must manually update the agent bundle URL in the CCM wizard to reflect the customized repo URL.

      #Agent bundle URL
      http://your_HTTP_server/release-<version>/bundle/
    4. Exit the CCO wizard

You have now completed the CCO_TERTIARY upgrade.

Check the MongoDB Status after Upgrade

Run the following command on the CCO_PRIMARY, CCO_SECONDARY, and CCO_TERTIARY to verify the MongoDB status. All nodes should display the Mongo replica set.

Connect to Mongo shell on each of the three CCO instances and run the following command.

mongo
> rs.status()

The following is a sample output for this command.

rs.status()
{
         "set" : "setname",
         "date" : ISODate("2018-7-16T19:28:33Z"),
         "myState" : 1,
         "members" : [
                   {
                            "_id" : 1,
                            "name" : “12.3.6.1:27017",
                            "health" : 1,
                            "state" : 1,
                            "stateStr" : "PRIMARY",
                            "uptime" : 33876,
                            "optime" : Timestamp(1513446629, 8),
                            "optimeDate" : ISODate("2018-7-16T17:50:29Z"),
                            "electionTime" : Timestamp(1513418644, 1),
                            "electionDate" : ISODate("2018-7-16T10:04:04Z"),
                            "self" : true
                   },
                   {
                            "_id" : 2,
                            "name" : "12.4.6.2:27017",
                            "health" : 1,
                            "state" : 2,
                            "stateStr" : "SECONDARY",
                            "uptime" : 33876,
                            "optime" : Timestamp(1513446629, 8),
                            "optimeDate" : ISODate("2018-7-16T17:50:29Z"),
                            "lastHeartbeat" : ISODate("2018-7-16T19:28:32Z"),
                            "lastHeartbeatRecv" : ISODate("2018-7-16T19:28:32Z"),
                            "pingMs" : 0,
                            "syncingTo" : "12.3.6.1:27017"
                   },
{
                            "_id" : 3,
                            "name" : "12.4.6.3:27017",
                            "health" : 1,
                            "state" : 2,
                            "stateStr" : "SECONDARY",
                            "uptime" : 33876,
                            "optime" : Timestamp(1513446629, 8),
                            "optimeDate" : ISODate("2018-7-16T17:50:29Z"),
                            "lastHeartbeat" : ISODate("2018-7-16T19:28:32Z"),
                            "lastHeartbeatRecv" : ISODate("2018-7-16T19:28:33Z"),
                            "pingMs" : 0,
                            "syncingTo" : "12.3.6.1:27017"
                   }
         ],
         "ok" : 1
}
  • No labels
Terms & Conditions Privacy Statement Cookies Trademarks