If you read Nathan’s “A Cloud to Call Your Own” blog, and you wanted to learn a little more about private clouds in general or SoftLayer Private Clouds specifically, this post is for you. We’re going take a little time to dive deeper into the technology behind SoftLayer Private Clouds, and in the process, I’ll talk a little about why particular platforms/hardware/configurations were chosen.
The Platform: Citrix CloudPlatform
There are several cloud infrastructure frameworks to choose from these days. We have surveyed a number of them and actively work with several of them. We are active members of the happenings around OpenStack and we have working implementations of vSphere, Nimula, Eucalyptus and other stacks in our data centers. So why CloudPlatform by Citrix?
First off, it’s one of the most mature of these options. It’s been around for several years and now has the substantial backing of Citrix. That backing includes investment, support organizations and the multitude of other products managed by Citrix. There are also some futuristic ideas we have regarding how to leverage products like CloudBridge and Netscaler with Private Clouds. Second, CloudPlatform operates in accordance with how we believe a private cloud should work: It’s simple, it doesn’t have a huge management infrastructure and we can charge for it by the CPU per month, just like all of our other products. Finally, CloudPlatform has made good inroads with enterprise customers. We love the idea that an enterprise ops team could leverage CloudPlatform as the management platform for both their on-premise and their off-premise private cloud.
So, we selected CloudPlatform for a multitude of reasons; not just one.
Another huge key was our ability to integrate CloudPlatform into the SoftLayer portals/mobile apps/API. Because many SoftLayer customers manage their environments exclusively through the SoftLayer API, we knew that a seamless integration there was an absolute necessity. With the help of the SoftLayer dev team and the CloudStack folks, we’ve been able to automate private clouds the same way we did for public cloud instances and dedicated servers.
When it came to choosing what hardware the private clouds would use, the decision was pretty simple. Given our need for automation, SoftLayer Private Clouds would need to be indistinguishable from a standard dedicated server or CloudLayer environment. We use the latest and greatest server hardware available on the market, and every month, you can see thousands of new SuperMicro boxes being delivered to our data centers around the world. Because we know we have a reliable, powerful and consistent hardware foundation on which we can build the private clouds product, it makes the integration of the system even easier.
When it comes to the specs of the hardware provided for a private cloud environment, we provide as much transparency and flexibility as we can for a customer to build exactly what he or she needs. Let’s look into what that means…
The Hardware Configurations
A CloudPlatform environment can be broken down into these components:
- A single management server (that can manage multiple zones across layer 2 networks)
- One or more zones
- One or more clusters in a zone
- One or more hosts in a cluster
- Storage shared by a cluster (which can be a single server)
A simple diagram of a two-zone private cloud might look like this:
We’ve set a standard “management server” configuration that we know will be able to accommodate all of your needs when it comes to running CloudPlatform, and how you build and configure the rest of your private cloud infrastructure is up to you. Whether you want simple dual proc, quad core Nehalem box with a lot of local disk space for a dev cloud or an environment made up of quad proc 10-core Westmeres with SSDs, you have the freedom to choose exactly what you want.
Oh, and everything can be online in two to four hours, and it’s offered on a month-to-month contract.
The Network Configuration
When it comes to where the hardware is provisioned, you have the ability to deploy zones in multiple geographies and manage them all through a single CloudPlatform management node. Given the way the SoftLayer three-tier network is built, the management node and host nodes do not even need to be accessible by our public network. You can choose to make accessible only the IPs used by the VMs you create. If your initial private cloud infrastructure is in Dallas and you want a node online in Singapore, you can just click a few buttons, and the new node will be provisioned and configured securely by CloudPlatform in a couple of hours.
Imagine how long it would have taken you to build this kind of infrastructure in the past:
It doesn’t take days or weeks now. It takes hours.
As you can see, when we approached the challenge of bringing private clouds to the SoftLayer platform, we had to innovate. In Texas, that would be roughly translated as “Go big or go home.” Given the response we’ve seen from customers and partners since the announcement of SoftLayer Private Clouds, we know the industry has taken notice.
Will all of our customers need their own private cloud infrastructure? Probably not. But will the customers who’ve been looking for this kind of functionality be ecstatic with the CloudPlatform environment on SoftLayer’s network? Absolutely.