Many companies are finding workloads that are much more appropriate for the infinite scalability and cost predictability of the public cloud. They are also finding the public cloud to be an excellent disaster recovery and business continuity resource. The challenges come when you consider that the local data center and the public cloud have two completely different sets of management tools, and moving workloads between them is not that easy.
Companies using VMware are certainly very familiar with VMware vCenter, and those familiar with Amazon Web Services (AWS) are used to its management console. Of the two interfaces, vCenter is more advanced and integrates with a greater number of on-premise and third party tools used by production data centers. The AWS management console, on the other hand, is relatively basic when compared to vCenter. Although Amazon is enhancing the functionality of AWS, its management still operates in a standalone environment; taking advantage of some of the new features requires integrating with an API and is not integrated into mainstream data center tools.
Even if the two management interfaces were of equivalent functionality, it is always challenging to learn and manage two different interfaces that accomplish very similar things. It increases the learning curve and can decrease the depth to which an administrator would learn an interface. You can only go so deep if you must learn multiple interfaces. It can also increase the time it takes to accomplish a certain task. That’s because an administrator might have to stop and think how to accomplish a particular task with a given tool. In IT, this traditional challenge is often met by a third-party that writes a single interface that communicates with other products. For example, consider all the third-party storage management tools and backup reporting tools – each of which manage multiple products with a single interface.
HotLink chose to go a different route. Since vCenter is already very mature and broadly deployed into every VMware data center, HotLink has a patented way to use vCenter to natively interoperate with and manage AWS, including Govcloud. Once set up, Amazon resources appear and behave as vCenter resources. This allows VMware enthusiasts to use their existing knowledge and tools to deploy, administer and manage a completely new resource in the same way a VMware vSphere hosts and virtual machines.
HotLink is able to use AWS as a disaster recovery and business continuity option for vSphere workloads, and is able to easily migrate workloads between the two platforms. It is also able to do this without requiring the installation of guest-level agents. Besides allowing customers to leverage their current knowledge of vCenter, it also allows the use of vCenter-compatible tools to manage their AWS environment. HotLink can reuse existing VMware templates, scripts, and workflows, and use PowerCLI for automation and orchestration.
While one can certainly not count out companies like Microsoft and IBM when it comes to the public cloud, it is hard to argue against the ubiquity of Amazon Web Services. One challenge, however, comes in having two very different interfaces to manage two very different infrastructures. HotLink’s offering that allows companies to use their existing vCenter knowledge and tools to manage AWS and migrate workloads between AWS and their local VMware environment offers a lot of possibilities across a wide range of use cases.