Deploying Multiple Docker Containers in the Cloud with Clocker

A lot has been said about LinuX Container‘s lately. In fact, white-hot Docker, the creator of the Docker open source container project, is nearing a $40M-plus funding round. The reason containers are gaining so much popularity is they make it easier to move software applications from computer to computer and from cloud to cloud. It’s even easier than the Virtual Machine images that are so popular today. You can create, deploy, move, update and resize containers because Docker makes it easy to partition a single host into multiple containers and then makes it easy to resize each container to fit the compute needs of your application. And Docker open sourced their container project making it appealing to a wide range of customers and vendors who want to use containers on-premise and in the public cloud.

As you can imagine, this will have a significant impact on the Virtual Machine image vendors, namely VMware. But it doesn’t stop there. By embracing containers as the new unit of deployment for cloud-based applications, the idea of being locked into a Virtual Machine format like an Amazon Machine Image (AMI) is no longer a problem. Any cloud that embraces Docker-based containers can make a huge catalog of cloud-based applications immediately available to their customers, thus removing one of Amazon EC2’s greatest advantages … locked-in machine images. And Docker can run in the Public Cloud on Amazon EC2, Google and Microsoft Azure as well as native on Linux as well as inside KVM, VMware or Hyper-V hosts. As we speak, 1000’s of Virtual Machines images are converting from VMware or Amazon’s image format to Docker’s light weight container images.

This is well and good if your application can run in multiple containers on a single host. But most web scale and enterprise applications require multiple hosts for resilience, fault tolerance and application scaling … not to mention simplicity. As you can imagine, managing IP Addresses is no simple task either. And this new container complexity is creating great demand for deployment tools that can setup and configure Docker-compatible clouds and applications. One such tool is Clocker, an Apache Brooklyn-based project, created by CloudSoft.

Clocker helps you turn any public or private cloud into a one capable of provisioning applications across multiple Docker server hosts, each with multiple docker containers. Not only does Clocker automate the provisioning, but it places the containers intelligently within the hosts to provide resilience, fault tolerance, easy scaling, maximum resource utilization of hosts and maximum application performance.

docker-in-the-cloud-slidesTo automate the deployment of your application, you need a script, manifest or some description of the application resources to be deployed into the containers. With Clocker, you can use a Dockerfile or an existing Brooklyn/CAMP blueprints. If you use Brooklyn/CAMP blueprints, you can add specific Docker customizations to take advantage of special Clocker features like specifying affinity rules to help place the containers intelligently. 

There is something special about containers that makes it seem natural for the cloud. Docker, the company, has demonstrated how to bring containers into the mainstream in a way that is capturing the imagination of many. I’m sure we will see many other innovative ways to use Docker to improve cloud usage. Right now, the land grab opportunity is to be the first to deploy Docker containers. Apache Brooklyn-based Clocker uses innovation and open source to make the deployment of multi-container applications easy too.

To find out more about Clocker, read CLOCKER – CREATING A DOCKER CLOUD WITH APACHE BROOKLYN or join the CloudSoft crew today online to see how to deploy Applications using Docker containers on OpenStack.  

Helion: HP’s OpenStack Distro – Download Available

Helion is born!

It’s been 2 years since HP announce it would launch a public cloud based on OpenStack ™. Their public cloud (now called HP Helion Public Cloud) went GA in late 2012. Since then, HP has run its public cloud on multiple iterations of OpenStack, gaining a ton of operational know-how. Today HP announced its first OpenStack distro called HP Helion OpenStack Community Edition. The Community Edition is a pure OpenStack distribution that has been been wrapped in an HP installer to make it easy for you to download & install.  This announcement is great news for anyone looking to try the latest version of OpenStack (the current version is based on Icehouse, the 9th OpenStack release). But don’t expect to run an enterprise grade cloud on it. That option will come later when HP releases its commercial edition of Helion.

So what can you do with the Community Edition? The Community Edition is free to download and use. So it’s great for education, proof of concepts, dev and test, and relatively small production workloads. And it is continuously updated and tested by HP on 30 nodes. Anyone using this free distro will get tested updates every six weeks or so. And if you buy support, HP will help you manage those updates. Beyond that, if you need to run a large production cloud, HP recommends you use its enhanced commercial edition which will target global enterprises and service providers when it is released.

Tomorrow at noon (12pm Pacific time), I will be participating in an online chat with Sriram (the Cloud Don) and some folks from HP. Please join us as we discuss Helion, the first OpenStack distribution by HP for its customers and everyone else in the open source community. And if you feel like trying OpenStack, a freshly baked version of Helion is waiting for you to download right here!

 

 

 

Developerweek Hackathon this Saturday

The DeveloperWeek Hackathon is this Friday-Saturday-Sunday. What is it is you ask? it’s a 43-hour app-building contest and the official kick-off of DeveloperWeek 2013. 

The purpose of the hackathon is to give developers, designers, and entrepreneurs the chance to pitch app ideas – form teams – build a prototype of their app – and present to our hackathon judges for a chance to be one of the top 5 hackathon winners who get “incubated” during DeveloperWeek.
 
The judging is from 11:30am – 12:30pm on Sunday. Here’s the rest of the schedule: http://www.developerweek.com/hackathon/index.html#schedule
 
As for the hackathon rules
 
Developers can build any app they want – however they get ‘extra points’ from the judges if their app integrates an external API. That can be anything from google maps or twitter OAuth to one of our sponsor’s API’s!

 
Here are the rest of the hackathon rules:
  1. You can prepare wireframes, outlines, or notes but you cannot start any of your design or development until Friday February 1st at 6 PM! 
  2. Teams must consist of at least 1 person but at max 5 people 
  3. Your team and your app will be judged based on 3 criteria: 
    1) Are you solving a real problem in an interesting way? 
    2) How well did you present? 
    3) How much progress did you make on your app? 
  4. If you build using a sponsor’s technology then you are also eligible for the sponsor prize! The sponsor prizes are listed here: https://www.hackerleague.org/hackathons/developerweek-2013-hackathon/wikipages/50fdb2fec050da2598000005
The event is sold out, but I may be able to get passes for a few deserving developers. Let me know!