eucalyptus

How to Build a Private Cloud

Ubuntu Enterprise Cloud (UEC) is a private cloud that embeds Eucalyptus cloud on Ubuntu server. The current release of UEC runs on Ubuntu 9.04 Server running Eucalyptus 1.5. There is a latter version of Eucalyptus (i.e., 1.5.2); however, I didn’t try that for this blog post. In this blog example I installed all of the UEC cloud components on a single system. Typically you would not want to do this; however, this works well as a demo system.

Quick UEC Overview

UEC is made up of three components: Cloud Controller (eucalyptus-cloud), Cluster Controller (eucalyptus-cc), and one or more Node Controllers (eucalyptus-nc). The Cloud Controller is the Web-services interface and the WEBUI server. The Cloud Controller also provides resource scheduling and S3 and EBS computable storage interfaces. A cluster in UEC is synonymous with an availability zone in AWS. In this release of UEC the Cluster Controller has to run on the same machine as the Cloud Controller. The Cluster Controller provides network control for the defined cluster and manages resources within the cluster (i.e., resources on the node). The Cloud Controller and the Cluster Controller are sometimes referred to as the Front End. Typically the Node Controller runs on a separate box from the Front End box. In a production environment there will be multiple Node Controllers making up a larger cluster (i.e., your cloud). Each Node Controller runs as a KVM hypervisor and all the Node Controllers in the cluster make up the cloud environment. In the current release, running multiple clusters is really not supported. In future releases of UEC, you will be able to run multiple clusters in one environment. Each cluster acts like an availability zone in the UEC environment. As I noted earlier, in this blog example, I am putting everything on the same box (my laptop). I will point out areas where the configuration would be different in a normal installation of UEC.

Building a Private Cloud in One Hour

Rich Wolski on the difference between data centers and clouds

I’m working up an article about EUCALYPTUS and Eucalyptus Systems, cf. my earlier post on’t.

Leaving aside the giggles over nomenclature, I had quite a nice talk with Dr. Rich Wolski, the lead scientist on the original open source project (also with CEO Woody Rollins and the VP of marketing).

Anyway, Wolski had an interesting and quite succinct definition of the differences between a data center employing virtualization in its currently accepted form and a cloud infrastructure, because, on paper, the two share enough common elements that lots of people (and marketers) are happy to fuzz the two together.

I didn’t think that was quite right, and neither does the Good Doctor, (ha! like I’m the expert over here). Otherwise, why get excited over cloud? If that were true, then it’s just re-packaged old news, and nobody needs to do anything but change the badges and maybe dice up the trim package, if I may borrow from the big book of automobile industry metaphors. But cloud is fundamentally something different, and new, and it’s worth knowing why.

He says it’s down to access and the control structure. The major difference between a data center and a cloud is access- a cloud is set up so anyone can drop a penny in the slot and start up a server or six- in a data center, you ask, and someone does it for you, then hands over the steering wheel.

He said something like, pardon the paraphrasing, “in a data center, virtualization is the grease that lubricates resource management” for the admins; it allows the guy in charge to move his resources around- “it’s a reconfiguration mechanism,” but “in a cloud, [virtualization] is a fence.” it separates and protects resources and lets everyone have their own private playground without knocking over the other kids’ toys.

A subtle difference? Wolski says it’s down to a bedrock set of premises and assumptions that drove the development of the cloud model.

“We tried to look at the cloud paradigm from an analytical perspective,” he explains, and “cloud is an ecommerce model-it’s a transactional model [in a] distributed system”.

Did that sink in? At its most basic, cloud is not about computers. It’s about sales. Start with the premise that you have a product (server instances/CPU time/bit buckets), you want to sell them to any and all comers over the internet (ecommerce) and you want to do a lot of it. What you get is “cloud computing”, and logically, it’s no surprise that Amazon pioneered it commercially. They didn’t assume they needed a resource farm and a way to sell access to it- they assumed they had servers and needed to sell those instead.

So that’s interesting to me. Cloud is not a utopian access opium dream- it’s a logical outgrowth of commodity commerce.

UPDATE:Story’s done, look for it soon. One more little nugget from Wolski on defining cloud computing: When he and his crew started thinking about the project in 2007, they found it was “utterly impossible to get a consensus” on what cloud was, so they “decided to sidestep the debate by picking the thing that was demonstrably was a cloud — the one thing no one could say was NOT a cloud.” Their answer? Amazon Web Services.

So there you have it - not sure what an elephant is? Look around; you can’t miss one if it’s in the room with you.

EUCALYPTUS sprouts business shoots

In what is surely a contender for the most-complicated backronym of the ages, the Elastic Utility Computing Architecture for Linking Your Programs to Useful Systems, first developed at Middleware and Applications Yielding Heterogenous Environments for Metacomputing, UC- Santa Barbara (MAYHEM in case you weren’t seeing the silly nomenclature trend) has jumped the public lagoon for the open waters of commerce:

Eucalyptus Systems, formed out of the team that developed EUCALYPTUS has gone commercial to sell help with their open-source software to cloud-minded types.

EUCALYPTUS (fingers…getting…so… tired) is a set of open-source software tools that allow users to interact with and deploy AWS-type clouds. You can use the software to administer your EC2 images or create your own private data cloud along the same model. Pretty neat, and free, but what happens when AWS decides to re-tool their APIs? Questions soon to be answered.

read the press release here.

watch this page for updates.