Académique Documents
Professionnel Documents
Culture Documents
Training
Events
Video
search linux.com
Home
Home
News
Linux Community
Learn Linux
Learn Linux
Linux Tutorials
Directory
Jobs
168
127
Exclusive
1
Here's a scenario. You've been hearing much about
OpenStack and you're interested in putting it through a test
drive so you can start learning it. Perhaps you want to learn it
to further your career, or perhaps you want to test it out to see if
it's something that would fit into your infrastructure. Either way,
you want to get it up and running, but with one important
requirement: Minimal or zero cost if possible.
Before we begin, let's address that final requirement. There
are many ways you can get up and running at no cost,
provided you already have some hardware. But if you don't
have the hardware, you can still get going at minimal cost
pdfcrowd.com
DETAILS
LFS426 Linux Perform ance Tuning
07 Dec 10 Dec - Virtual
OpenStack is technically just an API specification for managing cloud servers and overall cloud
infrastructures. Different organizations have created software packages that implement OpenStack. To
use OpenStack, you need to acquire such software. Fortunately, there are several free and open source
solutions. (There are also premium models available, as well as free software, that come with premium
support models.)
Since OpenStack is for managing cloud infrastruture, to get a minimal setup, you need two machines:
One will be the infrastructure you're managing, and one will be the manager. But if you're really strapped
for hardware, you can fit both on a single machine. Today's computers allow for virtualization whereby you
can run multiple server instances on a single machine. Of course, the more cores you have, the better; a
DETAILS
LFS416 Linux Security
07 Dec 10 Dec - Virtual
DETAILS
View All Upcom ing Courses
quad-core is probably the minimum. So if you're working on single-core computer, you probably will want
to grab some space on a hosted server. If you have a dual-core computer, you'll still be a bit tight for CPU
space, and I recommend renting a server. But you can do it on your dual core if you have no other choice
and just want to test out the basic functionality.
Latest Tutorials
The management tools are where things become a bit fuzzy between OpenStack being just an API and a
set of software that makes use of the API. Anyone can technically build a set of software that matches the
OpenStack specification. That software can be either on the managed side, or the manager side. The
managed side would implement the API allowing any OpenStack-compliant management tool to manage
it. The manager side would be a tool that can manage any OpenStack-compliant platform. The managed
side is where OpenStack mostly lives with its various APIs. There are several APIs, but here are a couple:
Compute is the main API for allocating and de-allocating servers. The code name for this API is Nova.
(Each portion of OpenStack includes a code name.) OpenStack also allows you to create and manage
images that represent backups of disk drives. This portion of OpenStack is called Glance. These images
are often going to contain operating systems such as Linux. The idea here is that you can choose an
pdfcrowd.com
image that you'll use to create a new server. The image might contain, for example, an Ubuntu 14.04
First Nam e
server that's already configured with the software you need. Then you would use the Compute server to
launch a couple of servers using that image. Because each server starts from the same image, they will
Last Nam e
be identical and already configured with the software you placed on the image.
Em ail
In addition to the APIs living on the managed side, you'll need a tool on the manager side to help you
Country
create servers. (This process is often referred to as provisioning servers.) The OpenStack community has
created a very good application called Horizon, which is a management console. Although I mentioned
that the free software is good for testing and development, the Horizon tool is actually quite mature at this
point and can be used for production. Horizon is simply a management console where you click around
and allocate your servers. In most production situations, you'll want to perform automated tasks. For that
you can use tools such as Puppet or Chef. The key is that any tool you use needs to know how to
communicate with an OpenStack API. (Puppet and Chef both support OpenStack, and we'll be looking at
those in a forthcoming article.)
Latest Software News
Up and Running
Knowing all this, let's give it a shot. The steps here are small, but you'll want to keep in mind how these
steps would scale to larger situations and the decisions you would need to make. One important first
decision is what services you want to use. OpenStack encompasses a whole range of services beyond
Active
the compute and image APIs I mention earlier. Another decision is how many hardware servers i.e. bare
metal servers you want to use, as well as how many virtual machines you want to allow each bare metal
server to run. And finally, you'll want to put together a plan whereby users have limits or quotas on the
amount of virtual machines and drive space (called volumes) they can use.
For this article we're going to keep things simple by running OpenStack on a single machine, as this is an
of Code Changes
easy way to practice. Although you could do this on your own everyday Linux machine, I highly recommend
instead creating a virtual machine so that you aren't modifying your main work machine. For example, you
might install Ubuntu 14.04 in VirtualBox. But to make this practice session as simple as possible, if you
want you can install a desktop version of Ubuntu instead of the server version and then run the Horizon
console right on that same machine. As an alternative, you can instead create a new server on a cloud
hosting service, and install Ubuntu on it.
Next, you'll need to install git. You don't need to know how to actually use git; it's just used here to get the
latest version of the DevStack software. Now create a directory to house your OpenStack files. Switch to
that directory and paste the following command into the console:
git clone https://git.openstack.org/openstack-dev/devstack
This will create a subdirectory called devstack. Switch to the new devstack, and then switch to the
pdfcrowd.com
pdfcrowd.com
pdfcrowd.com
Use the username demo and password nomoresecrete. This will bring up the main dashboard:
pdfcrowd.com
pdfcrowd.com
Leave the other tabs with their defaults. For this test, let's keep it simple by not providing a security key for
logging into the instances. Now click the Launch button and you'll see the progress of the machines
launching:
This might take a while since you're probably getting a little tight for system resources (as I was). But
again, this is just a test, after all.
The Task column will show Spawning as the instances are starting up. Eventually, if all goes well, the
instances will boot up.
That's about all it takes to get up and running with OpenStack. There are some pesky details, but all in all,
it's not that difficult. But remember that you're using just a developer implementation of OpenStack called
DevStack. This is just for testing purposes, and not for production. But it's enough to get you started
playing with OpenStack. Next time we'll explore automation with OpenStack using a couple of popular
tools, Chef and Puppet.
Jeff Cogswell
pdfcrowd.com
Comments
Name :
Email :
Comment :
Post Comment
Subscribe to Comments
WHO WE ARE ?
EXPLORE
STAY CURRENT
ABOUT LINUX.COM
Answ ers
Netbooks
How to Participate
Blogs
Cloud Computing
Contact / About
Forums
Enterprise
Advertise
Directory
pdfcrowd.com
pdfcrowd.com