Skip to main content

vCloud Director 9.x upgrade

 

vCloud Director upgrade from 9.7.0.4 to 9.7.0.5

It’s a Multi-cell environment (2 cell) hence I am following Orchestrated method for ease of upgrade which is really easy instead of manual upgrade. 

The current version noted before upgrade is 9.7.0.4 

            

Prerequisites

  • Take Backup of vCD cells and its database
  •   Set up ssh private key login from the primary cell to all other cells in the vCloud Director instance for user vcloud

1.  On the primary cell generate private/public key (with no passphrase):

                 ssh-keygen -t rsa -f $VCLOUD_HOME/etc/id_rsa

 

              chown vcloud:vcloud $VCLOUD_HOME/etc/id_rsa 

              chmod 600 /opt/vmware/vcloud-director/etc/id_rsa 

            

2.  Copy public key to each additional cell in the instance to authorized_keys file. This can be done with one line command ran from the primary cell  

    cat $VCLOUD_HOME/etc/id_rsa.pub | ssh root@<cell-IP> "mkdir -p ~/.ssh && cat ~/.ssh/authorized_keys"

                 

3.  Verify that login with private key works for each secondary cell in the environment

               sudo -u vcloud ssh -i $VCLOUD_HOME/etc/id_rsa root@<cell IP/FQDN>     

       

 

Orchestrated Upgrade 

Upload vCloud Director binary to the primary cell and make it executable

chmod u+x vmware-vcloud-director-distribution-8.20.0-5070903.bin

Execute the file with  --private-key-path option pointing to the private key.

./vmware-vcloud-director-distribution-8.20.0-5070903.bin --private-key-path $VCLOUD_HOME/etc/id_rsa

Workflow

This is the workflow that is automatically executed:

  1. Quiesce, shutdown and upgrade of the primary cell. Does not start the cell.
  2. If maintenance cell was specified, it is put into maintenance mode.
  3. Quiescing and shut down of all the other cells.
  4. Upgrade of the vCloud Database (a prompt for backup)
  5. Upgrade and start of all other cells (except the maintenance cell)
  6. If maintenance cell was specified, it is upgraded and started.
  7. Start of the primary cell

         

         

         

 The vCD is upgraded to 9.7.0.5 and is verified from vCD portal.

      

 



 

 

 

Labels:

Comments

Post a Comment

Popular posts from this blog

Deleting stale kubernetes clusters in vCD

Unlike the previous version the CSE 4.x is a stateless appliance and its data is stored in VMware Cloud Director Database.  The cluster creation and deletion compared with CSE 3.x version has improved. Besides, there are some scenarios where the cluster deletion is failing even when the "Force Delete" option is chosen. We can use vCD API explorer to delete it, the following are the API queries you can execute  Under definedEntity POST /1.0.0/entities/{id}/resolve DELETE /1.0.0/entities/{id}
Post a Comment
Read more

Manage RabbitMQ using VCP LCM

I have been working in vCD for quite some time, and most of the implementation engineers or consultants faced issues during the deployment or upgrade of RabbitMQ for the vCD message queuing service. From vCD 10.2.2, we can use the built-in MQTT client instead of RabbitMQ however, for VCD multisite configuration or some 3rd party applications need RabbitMQ, such as Veeam or VMware HCX. Using the VCP LCM, we can create a new RabbitMQ environment or manage an existing environment. The reason for this blog is that none of the VMware documentation has the information that registering an existing RMQ instance is only going to work if the RMQ instance was previously deployed by the VCP LCM (or at least, if it is a similar setup based on a Bitnami RMQ VM). Other RMQ instances (e.g., running in CentOS) are not supported and cannot be imported into the VCP LCM 1.5. I hope this information will be useful for someone who is performing green field deployment or upgrading an existing setup. ...
Post a Comment
Read more