We will illustrate using a single Calm blueprint to: one, deploy an application to Nutanix, two, deploy the same application to AWS, and three, deploy part of the application to Nutanix and part to AWS. Looking at the blueprint we see multiple application profiles: one for each cloud configuration that we are deploying to. We currently have the Nutanix cloud deployment profile selected, and we can see that each of the services has the Nutanix X signifying that these services are being deployed to an Nutanix cloud. Looking at the VM settings of the MongoDB service, we see the required attributes to deploy to a Nutanix cluster and in the package we have the Nutanix credential selected, and the script to install and configure our MongoDB. Let’s go ahead and launch this blueprint with the Nutanix cloud deployment profile selected and fast forward to the completion of this deployment. Now that the deployment has completed, we will look at the services tab to find information about the servers that have been deployed, such as the names and IPs of each server. Copying the nginx IP and dropping it here in a new browser window, we can see that my custom application has been deployed and is functional.
We can also see information about the VMs that have been deployed here in the Prism Central explore tab. Now, I will demo the deployment of the same blueprint to AWS. When I select the AWS profile, we see that the icons on each service are now the AWS boxes signifying that these services will be deployed to AWS. Looking at the MongoDB service we see all the required attributes to deploy the same application to AWS. On the package tab, we can see that the credential required to access the deployed server and run the script is set to AWS. Let’s launch the blueprint. We provide a name for the deployment and then all we have to do to send it to AWS is select the appropriate profile, in this case the AWS cloud deployment. Let’s fast forward to the end of this deployment. Now that the AWS deployment has completed, as with the earlier Nutanix deployment where you’re able to view the details of the deployed services, and we can see that the AWS application has been deployed and is functional.
Here within the AWS interface we can see the instances that have been deployed. We are back at our blueprint, this time we are going to select the hybrid cloud deployment which will deploy the MongoDB and node.js services to AWS as we can see by their icons; and the nginx service to the Nutanix cloud. Let’s go ahead and launch this blueprint, this time selecting the hybrid cloud deployment profile. We will also go ahead and fast forward to its completion. As with earlier examples, we can see our functioning application. This time, part is running on Nutanix and part on AWS. Looking at the AWS interface, we can see the newly deployed MongoDB and node.js instances, along with those that were previously deployed. In PC, we can see the new nginx VM that has just been deployed with the other previously deployed VMs. To sum up, we have demonstrated how the same Calm blueprint can be leveraged to easily deploy applications to multiple clouds or hybrid clouds.