Latest Cloud Director 10.1 release adds support for VM Encryption using cloud director self service portal, this means it allow users to encrypt/decrypt VMs and disks via Cloud Director, view the encryption status of VMs and disks in the API as well as user interface. Some of the key features are:

• Ability to encrypt VMs at rest through Cloud Director UI and API
• Cloud Providers configure Key Management Service (KMS), and encryption policy in backend vSphere
• Cloud Providers can choose to make VM encryption available for some or all tenant
• Tenant users can choose to apply encryption policy to VMs or individual disks.
• In case of Tenant Managed Dedicated vCenter then Tenant can manages Keys and VM Encryption

I am going to write three part blog posts , which will cover:

• VMware Cloud Director Encryption – PartI
• VMware Cloud Director Encryption – PartII
• VMware Cloud Director Encryption – PartIII

Deploy KMS

With HyTrust KeyControl supports a fully functional KMIP server that can be deployed as a vSphere Key Management Server and once deployment is completed and a trusted connection between KeyControl and vSphere has been established, KeyControl can manage the encryption keys for virtual machines in the cluster that have been encrypted with vCenter Server for vSphere Virtual Machine Encryption or VMware VSAN Encryption.

In this post we will deploy HyTrust KeyControl KMS server and setup KMS Cluster..There are two methods for installation of Key Control… either we can use OVA appliance or another Method to use ISO. in this Post we will use OVA method..

• Open your vSphere Web Client and Click on “Deploy OVF Template”.
  • 
• Choose OVF
  • 
• Provide Name for the HyTrust KeyControl Appliance, select a deployment location, then click Next.
  • 
• Select the vSphere cluster or host Where you would like to install the HyTrust KeyControl appliance on, then click Next.
  • 
• Review the details, then click Next.
  • 
• Select the proper configuration from the drop down menu, then click Next. ( i am using Demo as resources are less in my Lab)
  • 
• Select the preferred storage and disk format for the KeyControl appliance, then click Next.
  • 
• Select the appropriate network, enter appropriate network details then click Next.
  • 
• Review the summary screen, if everything is correct, click Finish.
  • 
  • 

Appliance deployment is successfully completed.. since i am going to setup a cluster , so i would go ahead and deploy another appliance using the same procedure

Configure KMS Cluster

Once Both the appliance has been deployed ,

• Power on the newly created HyTrust KeyControl appliance.then open a console to the KeyControl appliance. Set the system password, then press OK.
  • 
• Since this is the First Node ,Select No, then press enter.
  • 
• Review the Appliance Configuration, then press OK.
  • 
• Now First KeyControl appliance is configured and you can now move to the KeyControl WebGUI. Open a web browser and navigate to the IP or FQDN of the KeyControl appliance. Use the the following credentials to initially log in:
  • Username: secroot
    Password: secroot
  • 
• After login , read and accept the EULA by clicking on I Agree at the bottom of the agreement.
  • 
• Enter a new password for the secroot account, then click Update Password.
  • 
• Now we successful setup our first Node..
  • 
• Power on the second appliance and follow all the steps as above , except.. Click “YES” Here.
  • 
• This will take us to the process of Cluster creation process..
  • 
• Enter the IP address of First Node.
  • 
• The final piece of information required is the passphrase. We would require a minimum of 16 characters.
  • 
• The node must now be authenticated through the webGUI, as the following message indicates:
  • 
• At this point you need to log on to the webGUI console of First Node with Administration privileges. The new KeyControl node will automatically appear as an unauthenticated node in the KeyControl cluster, as shown below:
  • 
• To authenticate this new node, click the Actions Button and then click Authenticate. This will take you to the authentication screen shown below. You are prompted to enter the Authentication Passphrase.
  • 
• On the new KeyControl’s console, you will see a succession of status messages, as shown below:
  • 
• Once authentication completes, the KeyControl node is listed as Authenticated but Unreachable until cluster synchronisation completes and the cluster is ready for use. This should not take more than a minute or two. Then it will show as Authenticated and Online.Once the KeyControl node is available, the status will automatically move to Online and the cluster status at the top right of the screen will change back to Healthy.
  • 

At this point, the new cluster/node is ready to use.

Enable KMS Service

• Now Click on the KMIP button on the toolbar to configure the KMIP.
  • 
• Enable KMIP by changing the state from disabled to enabled, then click save, then click Apply.
  • NOTE: Take note of the port number 5696 and have it handy. You will specify this port number in the vCenter\VCSA configuration, later on.
    
• Now we have successfully setup KMS Cluster.
  • 

This completes process of KMS server installation , their configuration and KMS cluster creation and configuration. In the next post , we will use this cluster for vSphere to use as KMS server.