Sunday, October 16, 2016

VMware on AWS tech preview

GREAT NEWS!! The power of virtualization meets the most powerful cloud.

    The news is not that quite new but knowing the same technically is quite interesting.

The deployment of VMware vsphere on aws is quite easy and provides great flexibility and power of scalability.

  Since i am going to show few preview steps, i am not going to go deep in bla bla bla!!

  Start the deployment of VMware on AWS with AWS web portal, (spoiler alert!!) i think the same may be available in vCenter web console in next version.

   Login to the console and select the region closest to your on-prem VMware (if you do not have on-prem VMware then you can select any)

Initially the VMware is available in 3 T-shirt size. 4 Hosts, 32 hosts and 64 hosts. The CPU, Memory and Disk is fixed with the size. Customization is available but still explored in demo.
Choose the pricing model, Good old Hourly price (not sure how feasible it is), 1 Year reserved and 3 year reserved. I hope partial and no upfront options available here. Payment option can be through Credit card, VMware account or through MSP like CrimsonCloud.

Wallah!! All the settings done. The setup will deploy VMware vSphere, vSAN and NSX for network virtualization. If you are using NSX on-prem then you can leverage Long distance vMotion features described below.
The AWS Cloud console for VMware is quite similar to previous web console. It shows all the different regions where VMware is deployed. The same console shows on-prem VMware VDC as well.

"The true form of Hybrid cloud is where we can migrate VM from on prem to cloud without shutting down" Now the same is possible with this partnership. With few clicks we can migrate storage (VMDK) and memory and other metadata information to AWS Cloud.

The steps are quite simple for migration, Click on on-prem VM->action and select Migrate

  Choose both Memory and storage (because you can not migrate just compute to AWS and storage to on-prem). select compute resource first if workload is compute intensive and storage if its IO intensive.

Select the target virtual datacenter where we just deployed our new VMware cluster

High priority vMotion will initiate live migration immediately and gives priority over any running scheduled VM migration. The max concurrent VM vMotion is still the same limit with current vSphere version. 

Recommended way of migrating the same over the direct connect because of high network requirement (if migration time is the concern).

For directconnect, private VIF is required for migration or public VIF with VPN. 

   The live migration also enables VMware DRS feature for VM migration to distribute the load. Since its working without single cluster its now called EDRS (Elastic distributed resource scheduling)

 One of the other main advantage is patch update of vmware infrastructure. deployed vSphere on AWS is managed by AWS so patch update and security is also AWS responsibility.

Still the DC level (AZ level) HA is not visible but if the vSAN cluster do not span across multiple AZ then VM level backup can be taken to AWS S3 using CrimsonVault.

  Since vSphere on AWS will be integrated with other AWS services like redshift, S3 and other non VPC service it will be easier to leverage true hybrid cloud functionality. I hope VPC based services like EC2 and RDS will be also available for integration with VMs running in AWS vSphere.

Still the on-prem VMware editions requirements are not published for hybrid cloud. Hope the same is available with the lowest VMware edition.