Tuesday, January 27, 2015

OpenStack (Juno) - How to install Mirantis Fuel 6.0 with default configurations using Virtual Box on Windows 7



I have put together the steps that I took to set up the environment on my laptop (8GB RAM, i7 Dual-Core, Hyper-thread enabled, 500GB Hard Disk, 64-bits Windows 7) with reference to http://docs.mirantis.com/openstack/fuel/fuel-5.1/user-guide.html

I managed to get the test Cirros VM up and running with the default configurations (no changes made).

Hopefully these steps are useful for those who wants to try out OpenStack (Juno) deployment on your local machine with Mirantis Fuel 6.0

Cheers!


Steps:

1) Download Mirantis Fuel 6.0 from Mirantis website:


2) Download and install the latest version of Virtual Box on your laptop


3) Open Virtual Box and click on File -> Preferences -> Network -> Host-only Networks



4) Add 2 more Host-only Networks by clicking on



5) Configure each network by clicking

Note that I have made use of the default configurations: 

VirtualBox Host-Only Ethernet Adapter



VirtualBox Host-Only Ethernet Adapter #2



VirtualBox Host-Only Ethernet Adapter #3



I did not set up any DHCP Server for the networks:



6) Create the Fuel VM using VirtualBox.  I used the following specifications (you can adjust based on your needs but I feel that this is the minimal requirements for it to work with acceptable performance):

Operating System     : 64-bits Red Hat
RAM                         : 1536  RAM
Hard Drive                : 50 GB (VDI, Dynamic Allocation) 
Number of Processor : 1


7) Configure the Network settings for Fuel:

Adapter 1


Adapter 2


Adapter 3



8) Boot the Fuel VM with the MirantisOpenStack-6.0.iso image and use the default settings (let the installer run, i.e. there is no need for manual intervention)

9) As it will take some time to install Fuel, we can set up another 2 VMs while waiting for it to be ready (I am only setting up 1 Controller and 1 Compute node as I have limited resources on my laptop).  

Create 1st VM (Controller, Cinder, Ceilometer) with the following specifications (you can change the settings based on your needs but it is better to have at least 50GB of HDD and 1536 MB RAM for the VM):

Operating System     : 64-bits Ubuntu
RAM                         : 2048  RAM
Hard Drive                : 150 GB (VDI, Dynamic Allocation) 
Number of Processor : 1


Create 2nd VM (Compute) with the following specifications (you can again change the settings based on your needs):

Operating System     : 64-bits Ubuntu
RAM                         : 2048  RAM
Hard Drive                : 250 GB (VDI, Dynamic Allocation) 
Number of Processor : 2


Configure the Network settings for both VMs (they will have the same configuration).  Adapter 1 and 2 will have the same settings as Fuel while Adapter 3 will have the following settings (check that MAC addresses are unique for each adaptor):



Configure the System settings of both VMs for PXE boot, i.e. Network should be on the top list for Boot Order.



10) Wait for Fuel to be installed and we should see the following login prompt:



Key in http://10.20.0.2:8000 on your browser (I used Google Chrome) and it should bring you to the Fuel login screen.  Use the default credentials admin/admin to log in for the first time (note that the web page can fail to load if port 8000 is blocked by Firewall):



11) After logging in, start up the other 2 VMs (click "Cancel" when prompted to provide start-up disk).  The VM should go into PXE boot and we will eventually arrive at the bootstrap login prompt:




12) Go back to Fuel GUI and click on the following icon to create a new OpenStack Environment:



I pretty much used the default settings for non-HA deployment (it is not necessarily to select Ceilometer, I select it as I want to track resource usage in my openstack environment):

OpenStack Release : Juno on Ubuntu 12.04.4 (2014.2-6.0) (default)
Deployment Mode  : Multi-node
Compute                 : QEMU
Network Setup        : Neutron with VLAN segmentation (default)
Storage Backends   : Cinder, Glance Default
Additional Services : Ceilometer


13) Next, click on the "Add Nodes" button to assign roles to the VMs:

We will see 2 unallocated nodes with MAC addresses as their names.  We can differentiate the compute and controller node by looking at the HDD size.  In this case, we know that the following node is the Compute node since it has 250 GB stated as its HDD size.  We will rename it and assign the "Compute" role to it: 


Assign Controller, Storage (Cinder) and Telemetry to the remaining node:


14) We will keep the default settings in the Networks and Settings Tab.  To check that there are no network issues, click on the "Verify Networks" button (it can be found at the bottom of the Network Tab).  It should return all green status since we are using the default settings.



15) Next, click on the following button to deploy the OpenStack environment:

16) It will take quite a while to deploy the environment.  At the end of the deployment, we should see the IP address of the Horizon dashboard:



17) Run basic sanity tests (under the Health Check tab) to make sure that things are good



18) Check that you can access the Horizon dashboard (the default login is admin/admin)



19) Go to the Project tab, followed by Compute -> Instance and click on the "Launch Instance"  button on the right-hand side of the screen


20) Create a Cirros TestVM with Horizon and use the default net04 network that was created during the OpenStack deployment (click on the Launch button after filling in the field):




21) Check that the Cirros VM is in "Active" state





You have successfully installed Mirantis OpenStack and created a test VM =)


Other Related Post:

Click here if you want to set up OpenStack (Juno) + OpenContrail (SDN) using Mirantis Fuel 6.1 on KVM Host





12 comments:

Sharath said...

A very useful article.. Was looking for something like this

Unknown said...

In step-11 ,the bootstrap menu is not coming.IT starts something... and later on says
"FATAL:COULD NOT REED FROM BOOT MEDIUM"

Till step-10 everything is correct.
I can even open the browser to fuel dashboard

By the way, my fuel vm is still running.

Juncheng Anthony Lin said...

Hi Himanshu,

Did you select "Boot from Network" for your VMs? Network should be on the top list for Boot Order.

/Anthony

M.P.B.N.Kumar Acharya said...

Hi followed the above procedure till fuel deployment and nodes comming to bootstrap prompt.
Now the issue comes is when I login to Fule I dont see nodes there.
How can I solve this

Juncheng Anthony Lin said...

Hi Kumar,

If the nodes reached the bootstrap prompt, it means that it PXE booted successfully. You should see the nodes in "Discovered" State from the Fuel GUI.

Can you log into the CLI of Fuel and issue the "fuel nodes" command? What is the output of that command?


/Anthony

Uli!i!i!i!.. said...

Hi Anthony

I repeated whole steps 3-4 times. Everything went ok until Verify Networks step. Network verification is failing with following message:

============================================
Verification failed.
These nodes: "1", "2" failed to connect to some of these repositories: "http://archive.ubuntu.com/ubuntu/", "http://mirror.fuel-infra.org/mos/ubuntu/" Repo availability verification using public network failed on following nodes Node 2. Following repos are not available - http://archive.ubuntu.com/ubuntu/, http://mirror.fuel-infra.org/mos/ubuntu/ . Check your public network settings and availability of the repositories from public network. Please examine nailgun and astute logs for additional details.
===========================================

Can you please help?

Regards,
U

Uli!i!i!i!.. said...

More info to my previous comment: this error is happening when I install Mirantis 6.1
I just tried with v6.0 and it is installed. Only Node 2 VM crashed during installation, I restarted it and installation went ok. Now I try to create instance it is created but failing to launch. Failed to launch instance. Error: No valid host was found.

Juncheng Anthony Lin said...

Hi,

I do not think there is any difference in network checks between Mirantis Fuel 6.0 and 6.1. You need to recheck your network settings to make sure that things are properly set up...

As for "No valid host was found" error message, it might be related to the flavor of the VM that you are trying to create. If you are trying to create a VM that takes up more resources, i.e. CPU, memory than what you have in the compute node, you will see similar error message and VM creation will fail.

There can, of course be other reasons, like network-related problems or incorrect configuration, but that will require further debugging.

/Anthony

hemanth uppuluru said...

Hello Anthony,

Nice and Useful Article!!!

At the Verify networks step I am getting the below error.

Verification failed.
Repo availability verification using public network failed on following nodes Untitled (15:b5). Following repos are not available - http://archive.ubuntu.com/ubuntu/, http://mirror.fuel-infra.org/mos-repos/ubuntu/7.0/ . Check your public network settings and availability of the repositories from public network. Please examine nailgun and astute logs for additional details.

Can you please help!!

Thanks in Advance..

Hemanth Uppuluru

Juncheng Anthony Lin said...

Hi Hemanth,

Are you able to ping archive.ubuntu.com and mirror.fuel-infra.org from Fuel? And how are the networks setup on the other nodes? They need to be able to reach the internet to pull the packages.

Thanks.

/Anthony

Willbail said...

Question During Fuel ISO install in VirtualBox. I am presented with the ability to configure the network interfaces created in the beginning of your How to. My question is should these network setting in the Fuel install mirror those that were configured in the VirtualBox Network interface configuration?

Alexis Pachas said...

Hi Anthony,

I have the same problem of Hemanth and I already have checked that my Master Fuel is able to ping archive.ubuntu.com and mirror.fuel-infra.org. Tha same situation for the Slave Nodes, they have a success message after ping.

Thanks.

Alexis