Things change. Technology changes fast. Here is an updated installation guide for Chef version 12. There are two notable differences in this post compared to a previous guide for Chef version 11, Install a Chef (Version 11) Server, Workstation and Client. First, this installation is all done via command line whereas we used the user interface in the previous post. Second, version 12 defaults to using authentication keys to communicate between a Chef Workstation and a Chef Server. There are also a number of other changes, such as the new Chef Development Kit. Note that this guide uses Enterprise Linux 6.5 instead of Ubuntu 12.04. This guide will also provide instructions on how to setup Chef when the environment is behind a http proxy. (more…)
I invested 14 months of my life working at Nebula after having worked 14 years at IBM. What a contrast. Nebula’s leaders and founders changed the IT universe by creating OpenStack Nova. Perhaps there was too much focus on changing the world than on making money, but it was awesome to work with the people who pioneered OpenStack. The mentality was very different than my prior experience, where the clear emphasis was sales. This blog post captures lessons learned from my Nebula experience.
The biggest takeaway might be best summarized by a question posed by one prospect. Do you have an equivalent of a “Hello World” program for cloud? What this prospect needed was something rare in today’s enterprise, applications well-suited for the cloud. Many enterprises and vendors have prioritized building and providing IaaS and PaaS (Platform-as-a-Service). If you read my very first blog post, “How to assess the maturity and growth potential of an enterprise cloud”, you will see that I had focused on IaaS and PaaS too. I have now updated the assessment method to include applications, as described later in this post.
The previous post, “Are meaningful server names just for tradition in a cloud?”, talked about how Enterprises want to use server naming conventions. What happens, however, when a cloud service provider uses its own scheme, typically hard-to-remember unique? This post will talk about one possible solution, creating an alternative DNS-in-a-cloud.
Let us assume that we want a naming convention with hostnames like:
but our cloud provider uses a scheme like this:
In today’s “AWS re:Invent” keynote, Andy Jassy, Senior VP of AWS (Amazon Web Services), said that 90% of their roadmap is driven directly by client feedback. For the other 10%, they listen to what the clients say but have to think about what the client really wants and invent on their behalf to solve the problem. Is server name convention one such scenario where those of us in the cloud space need to innovate?
One of my clients is so invested in their DNS naming convention that their applications and security protocols expect servers to follow a specific convention. They have requested that an IaaS (Infrastructure-as-a-Service) solution needs to conform to their DNS naming standard because it would be so difficult to move away from their convention.
Can we build clouds that scale and meet existing DNS naming conventions? Do we want to? In the long-term, when enterprises have fully embraced cloud, my belief is that we will move away from server naming conventions to server tagging and search. Such a transition will neither be quick nor easy. As Mark Twain wrote in The Adventures of Tom Sawyer, “the less there is to justify a traditional custom, the harder it is to get rid of it”. We will need interim solutions.
Whereas the last post introduced Chef and its key concepts, this post talks about how to install it. Afterall, perhaps the best way to learn a technology is to use it. So let’s take a look at how to install a Chef Server, Workstation and Clients. This guide also includes instructions on how to install the “knife-openstack” plugin. Note, this guide is for Chef version 11. See the post “Install a (Version 12) Chef Server, Workstation and Client” for a guide on installing Chef version 12.
Similar to OpenStack, Chef is a tool that brings technologies used by web-scale companies to the mainstream. OpenStack enables us to dynamically deploy thousands of virtual machine instances. Chef enables the automated configuration of those instances and is inspired by the automation long used at both Amazon and Google. Chef has become one of the more popular configuration management tools and cloud services like Amazon OpsWorks support Chef. Alternatives to Chef are Puppet, Ansible and Salt.
Chef provides a way to code infrastructure in “recipes”. The code, or recipes, can automate the setup, configuration, deployment and management of virtual servers in a cloud. To better understand the value of Chef, consider the operational tasks a system admin would have to do. These tasks become daunting as the number of VMs increases. (more…)
June 17, 2014 – Added instructions to use block storage instead of instance storage
It is one thing to talk about technology. It is another thing to get it to work. Whereas my last blog post talked about the value of running Hadoop on a cloud, this one talks about my experience with implementing it. I used a Nebula appliance to deploy an OpenStack cloud and used Hortonworks Apache Ambari to setup a Hadoop cluster. (more…)
On January 29th, I logged onto the Open Compute Project Summit V live stream just in time to catch two technology titans, Mark Andreessen, a venture capitalist who had co-founded the Mosaic web browser and Netscape, and Andy Bechtolsheim, Chairman of Arista and co-founder of Sun Microsystems. Andy noted that, just ten years ago, hardware was too expensive for a service like Facebook to be feasible. Today, it is possible and Facebook has opened their technology to the world via the Open Compute Project. Together, Andy and Mark talked about the combination of open hardware and open source as a disruptive force that will radically reduce the costs of hardware and enable innovate cloud services.
Later in the summit, a panelist brought up the pairing of Open Compute hardware with OpenStack management software. To express how much of a fit Open Compute and OpenStack were, someone used an analogy that the combination was like peanut butter and jelly. It is an analogy which likely makes more sense those of us who grew up in the USA. Coupling OpenStack and Open Compute sounded compelling so I did a quick search and found a blog post by Rob Ober, “AIS: Open Compute and OpenStack – “peanut butter and jelly”. In that post, Rob talks about his experience moderating a panel discussion about the two open source initiatives. (more…)
While OpenStack is primed to transform enterprise IT, enterprises still have a lot of questions today. One popular topic is how OpenStack compares with VMware. Perhaps the best analogy that I have heard to explain OpenStack to vSphere skilled staff is that of cattle and pets. vSphere servers are likened to pets that are given names, uniquely cared for and nursed back to health when sick. OpenStack servers are likened to cattle, which get random identification numbers, cared for as a group and are replaced when ill. Figure 1 below shows an excellent slide from a Gavin McCance presentation. For network technologist, another good analogy that I have seen compares OpenStack to UDP and VMware to TCP.
Is the enterprise ready for OpenStack?
In addition to asking how OpenStack compares to vSphere, many also want to know if OpenStack is ready for the enterprise. Perhaps the better question would be, is the enterprise ready for OpenStack? To get the most benefit out of an OpenStack private cloud, or a public cloud like Amazon Web Services, enterprise applications need to be optimized. Applications would need to have a cloud native architecture. (more…)