With vCloud Director 10, cloud providers will be able to receive the additional following benefits:
- HTML 5 UI Enhancements (Provider and Tenant)
- Intelligent Workload Allocation
- VM Sizing Policies
- VM Placement Policies NSX-T Integration
- Central Point of Management
- Object Storage Extension
- Enterprise PKS support for Container Service Extension (CSE)
- Terraform vCloud Director Provider API Enhancements and vRealize Orchestrator Plugin
In vCloud Director 10 the legacy Flash based UI is deprecated and disabled by default. The HTML 5 UI now includes a complete provider UI and improvements to the existing Tenant UI.
Today I’m going to walk you through the processes required to upgrade a single vCloud Director cell which is original running on a Linux based OS.
You can upgrade a single cell by running the vCloud Director installer without command options. Before you restart an upgraded cell, you must upgrade the database schema. You upgrade the database schema after upgrading at least one cell in the server group.
You can use the vCloud Director installer for Linux to upgrade a vCloud Director server group that consists of vCloud Director installations on a supported Linux OS.
Verify that your vCloud Directordatabase, the vSphere components, and the NSX components are compatible with the new version of vCloud Director.
From the following screen, you can see that we first download the installation file to the target server, give the installation file execution permission, run the installation file, enter “y", and press “Enter” to confirm the upgrade. This script will install some upgrades to vClod Director server itself.
When changing the existing global.propertiesfile on the target server, the installer displays a warning of the following form:
warning: /opt/vmware/vcloud-director/etc/global.properties created as /opt/vmware/vcloud-director/etc/global.properties.rpmnew
If you previously updated the existing global.propertiesfile, you can retrieve the changes from global.properties.rpmnew.
You might see a warning if your host’s memory is less than 5 GB, VMware recommends at least 5 GB of memory be available for vCloud Director.
Then run the /opt/vmware/vcloud-director/bin/upgrade script to upgrade the database scheme.
Enter “y” to upgrade the database.
After the DB has been upgraded, restart the services. This completes our vCloud Director upgrade processes, it’s very easy and straightforward !
Now we’d like to login to check the vCloud Director 10 GUI.
I use “Provider” as the organization name to login in order to perform some Cloud Provider system administrator operations, I found this is a new login mechanism in this version which is much easy for our tenants to login.
Enter Cloud Provider’s system administrator login credential information:
Here we can see that we’ve successfully upgraded our vCloud Director to version 10.
The HTML 5 UI now includes a complete provider UI and improvements to the existing Tenant UI.
During VM creation a Tenant then can select one of the allocated policies.
Tenant Login check, enter organization name:
Enter tenant login credential:
Check that the Tenant UI adds support for creating and attaching named disks in vCloud Director 10.
I hope this blog can find you well regarding how easy it is to manually upgrade vCloud Director, thanks for reading, see you next time!