The “big three” public cloud providers are turning their sights to legacy workloads. It will be interesting to see how customers adopt and deploy VMware on AWS, Azure Stack and, now, Google Nested Virtualization.
One knock on public clouds from Google, Amazon, and even Microsoft is that they are terrific for brand-new software built to take advantage of their resources, but not so great for existing, older business software developed and deployed before the cloud era kicked off 10 years ago.
The cloud players are working to address that issue. Many companies don’t necessarily want to rebuild applications that run just fine so they can move to someone else’s cloud data centers.
In the quest for moving workloads to the cloud, many enterprises stall at the first hurdle: How best to migrate workloads to a public cloud where not only the hypervisor technology in use is completely different but so are the network principles? This is especially true for sophisticated and/or distributed workloads that have been around for years and are still running on old infrastructure.
Typically, the process is quite arduous e.g. Discovery, Re-Platform/Conversion, Network Changes etc., while making sure the application still behaves identically and with no performance degradation. Multiply this by the number of applications and you can see why it causes such a headache for enterprises.
Ravello makes it all easy by enabling migration of VMware-based workloads “as is” and even without any changes to networking. This is made possible due to Ravello’s HVX Hypervisor technology which abstracts the hardware, storage, and networking, thereby enabling any VMware workload to seamlessly move to the destination public cloud.