OpenStack Private Cloud on Your Laptop with DevStack Guide is a complete Guide with needed video for setup of private Cloud using your laptop as Bare Metal. We told you to get your Ubuntu to ready for Private Cloud ! There is not to much to say about this guide on OpenStack Private Cloud on your Laptop with Dev tack Guide, the word ‘laptop’ in title we hope will make people more interested. Total cost is zero up to the point we have shown you. OpenStack Private Cloud is deployed with DevStack using your computer / laptop as bare metal like a data center.
OpenStack Private Cloud on Your Laptop with DevStack Guide : Requirements
The requirement is thin. An Ubuntu back version (11.x) is suggested, we took the risk with Ubuntu 12.04 LTS (we basically modified few files that made Ubuntu crazy a bit, seriously do not use 12.04 for Dev Stack) on a Laptop with 2 GB RAM. It was a good laptop once. Officially you can check Github for more info on DevStack before seriously starting the project OpenStack Private Cloud on Your Laptop with DevStack :
|
1 |
https://github.com/cloudbuilders/devstack |
OpenStack Private Cloud on Your Laptop with DevStack : Requirements
First the Ubuntu must be of minimal setup. Second is, the Internet connection, Router etc. should be clean and have a Static IP, proper DNS etc. Third is, install the needed components to make it a LAMP server, if you are hesitating with commands, you can read this guide. We will take that you already know the Debian specific UNIX commands. The reason to use DevStack instead of OpenStack are various. OpenStack can be deployed with low (relatively) RAM too, but networking mode is important. Basically we have installed server components on Ubuntu, so it has become Server with GUI.
---
In your BIOS settings, you need eth0 and eth1 . In the video you will see, we have first installed :
|
1 |
sudo apt-get install bridge-utils # install birdge |
Here is the reference for the command :
|
1 |
https://help.ubuntu.com/community/NetworkConnectionBridge |
Then we opened the Interfaces config file and there are onscreen instructions to find the data easily, we used :
|
1 |
vi /etc/network/interfaces |
We used gksudo gedit command to open it in Gedit as read and write enabled file. Classically it should look like this after Editing (except the IPs) :
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 |
<span style="color: #0000ff;"># The loopback network interface</span> auto lo iface lo inet loopback <span style="color: #0000ff;"># The primary network interface</span> auto eth0 iface eth0 inet static address 10.11.12.13 netmask 255.255.255.255 network 10.11.12.13 broadcast 10.11.13.12 gateway 10.12.13.11 auto br100 iface br100 inet static bridge_ports eth2 bridge_stp off bridge_maxwait 0 bridge_fd 0 address 200.200.200.1 netmask 255.255.255.255 |
200.200.200.1 is your Private IP. Then we installed git :
|
1 |
sudo apt-get install git |
Cloned the DevStack repo :
|
1 |
git clone git://github.com/cloudbuilders/devstack |
Went to devstack folder (cd devstack) and opened the localrc file :
|
1 |
vi localrc |
Unofficially this should be added :
|
1 2 3 4 5 6 7 8 9 |
PUBLIC_INTERFACE=eth0 FIXED_RANGE=200.200.200.0/24 FIXED_NETWORK_SIZE=256 FLOATING_RANGE=10.11.13.12/24 NET_MAN=FlatDHCPManager FLAT_NETWORK_BRIDGE=br100 VIRT_DRIVER=libvirt <span style="color: #0000ff;">LIBVIRT_TYPE=kvm</span> SCHEDULER=nova.scheduler.simple.SimpleScheduler |
Deploying is by using ./stack command. As like many Rackspace Beta Products (if you are an user like us), do not use symbols but numbers, letters etc. up to 8. Go to your IP on browser (delete any Apace2 html file like things from www folder) :
You will get the OpenStack panel. It reminds me of old Rackspace mail server GUI. The options are also quite familiar. Instances and services are two important things which you must understand clearly for OpenStack Private Cloud setup.
With direct OpenStack Private Cloud Software, there is no pain of so much CLI commands. As you actually need no big config Cloud Server to add, you can do a practice with this kind of setup. Otherwise this way to setup is actually not for real usage in deployment field. It is actually not enough stable.
Thanks for the update. I really appreciate the efforts you have made for this blog