With NOS 4.1 GA around the corner I thought I should get started with playing with Cloud Connect with the tech Preview on NOS 4.0.1. Cloud Connect provides an infrastructure free hassle way to backup your virtual environments.
More information can be found on: Nutanix – High Availability and Data Protection
Common Amazon Terms
AWS = Amazon Web Services
EC2 = Elastic Compute Cloud
EBS = Elastic Block Storage
S3 = Simple Storage Service
AMI = Amazon Machine Images
Today Cloud Connect only works with AWS but Azure is also slated. You can deploy to any availability region which is great as Amazon is launching a new data center in Germany. In NOS 4.1 everything will be UI driven but in tech preview you do have to run one command line to setup your Nutanix AMI. Until 4.1 the AMI is private so you have to engage support to give you access to the AMI. You will have to give support your customer ID.
***** Make sure your cluster has the external cluster IP setup **************
On my cluster I ran:
The AWS ID & Key can be found from AWS support portal
Almost everything is automatically selected for the user except the AWS region & subnet (which decides connectivity type – SSH tunnel vs pre-existing VPN tunnel). Current workflow takes AWS API keys as input & expects that AWS API keys can be then used for below AWS operations:-
1. Query regions in EC2
2. Query subnets, VPCs & VPN gateways
3. Query AMIs in EC2
4. Query/create/modify security groups in EC2/VPC
5. Create/run/list AWS instances
6. Create/list/delete snapshots of EBS volumes
7. Create S3 buckets & write data into those buckets
Output from the Command
AWS subnet id not specified, launching instance in EC2
2014-10-23 08:48:14 INFO create_aws_instance:368 Started instance i-83b27e89 is in state pending
2014-10-23 08:48:57 INFO create_aws_instance:420 Waiting for AWS instance to be accessible...
2014-10-23 08:49:42 INFO create_aws_instance:420 Waiting for AWS instance to be accessible...
2014-10-23 08:50:27 INFO create_aws_instance:420 Waiting for AWS instance to be accessible...
2014-10-23 08:51:00 INFO create_aws_instance:638 Change of nutanix password Succeeded.
2014-10-23 08:51:00 INFO create_aws_instance:634 Creating single node cluster for cloud_data_gateway...
2014-10-23 08:52:09 INFO create_aws_instance:638 Creation of cluster (ip : XX.XXXX.XXXX.XXX) on AWS Succeeded.
2014-10-23 08:52:16 INFO create_aws_instance:634 Adding DNS serverv to cluster...
2014-10-23 08:53:19 INFO create_aws_instance:512 Successfully configured passworless ssh access.
2014-10-23 08:53:23 INFO create_aws_instance:638 Configuration of the cloud disk Succeeded.
2014-10-23 08:53:31 INFO create_aws_instance:638 Creation of storage pool backup-sp Succeeded.
2014-10-23 08:53:35 INFO create_aws_instance:638 Creation of container backup-ctr Succeeded.
2014-10-23 08:53:39 INFO create_aws_instance:638 Configuration of remote site 'local' on AWS instance Succeeded.
2014-10-23 08:53:41 INFO create_aws_instance:614 Configuration of remote site 'aws_54-244-175-211' on local cluster Succeeded.
2014-10-23 08:53:41 INFO create_aws_instance:391 AWS instance was successfully configured.
2014-10-23 08:53:41 INFO create_aws_instance:402 Instance i-83b27e89 private_ip XX.XXX.XXX.XXX. public_ip XXX.XXX.XXX.XXX VPC None Name Nutanix_EC2_
The Remote site does get setup in PRISM. The only thing that you might want to check off is to compress the data on the wire. I was using an ssh tunnel but for production you should run a VPC. Using a VPC you can achieve up to 25% better throughput.