CloudBolt customers are deriving great benefit from using the product and we want to share some of their stories. We cannot use all of their names publicly due to confidentiality agreements, but hopefully this series of posts will be useful to you. These are their stories…

A Major International Hotel Company

Today’s customer story is about one of the largest hotel companies in the world.  This company has over 5000 hotels under their corporate umbrella of brands and is an avid CloudBolt customer.

Pre-CloudBolt Problem

Because of the size and complexity of their IT infrastructure, the company utilizes four different public clouds.  They want the flexibility of multiple public clouds so they can use the platform that provides the optimal environment for each workload, as well as to protect themselves against price increases and instabilities in any one public cloud.

The challenge this created was that administrators needed to understand and use four different interfaces to locate, manage, and provision compute resources.  

They have used VMware’s vRealize Automation for managing VMware servers, but it did not provide support for the public clouds that they need. Furthermore, they found vRA to be extremely time-consuming to maintain, with upgrades requiring a multi-month processes, and a large professional services cost. Finally, the process of installing multi-server, multi-tier apps on any one of these public clouds was onerous and required the administrator to use multiple different interfaces (the public cloud console, Chef, and the new VM itself).

Our Solution

CloudBolt provided this hotel group a single user interface and API through which they can now deploy complex apps to any of the four public clouds they use, manage these apps and their constituent servers over the course of their lifecycle, and automate their business policies and best practices surrounding server deployment and management.

Their IT group has built blueprints in CloudBolt for deploying 40+ node Apache Hadoop clusters to the public cloud. After being deployed, these services can be scaled up and down from CloudBolt, and eventually decommissioned. Since CloudBolt has native Chef Enterprise integration, they are able to perform these tasks without the end user needing to separately work in the Chef UI. CloudBolt coordinates the bootstrap of the Chef agent on new VMs, associates nodes with the proper roles in Chef, and checks for success or failure of the Chef runs.

The company has found CloudBolt valuable enough that they have built a blueprint for CloudBolt itself, so they can install a development CloudBolt environment from within CloudBolt, then use that development instance of CloudBolt to experiment with a new version or an integration project, then remove the temporary CloudBolt server.

Recommended Reading