For OpenStack beginners, installation is often a big headache for getting started. Before the E version, to build a basic can use OpenStack environment that is quite troublesome, their own to install, their own source, according to the document to knock orders, and no reliable documents, the official document still have a lot of holes, and language problems are often used for a few days can not be loaded up, Slowly lost the confidence to learn OpenStack!
But then things changed a lot, starting with the E version, the installation process is much simplified and the quality of the documentation has improved a lot. Although this is still more complicated for beginners, in fact many times, many people just want to experience OpenStack, completely do not care about installing this kind of thing. Fortunately, the OpenStack community is active enough, and soon there are companies that have made relatively friendly installation tools, such as fuel, a tool that we would like to introduce to you today, but it can also be called Mirantis OpenStack, developed by Mirantis company.
About Mirantis
Mirantis, a very cool OpenStack service integrator, is the only company in the top 5 community contributors to a meal by software and services (others are red Hat, HP, IBM, Rackspace). In contrast to several other community distributions, the fuel version is fast paced, providing a relatively stable community version on average every two months.
What is Fuel?
Fuel is a tool designed for OpenStack end-to-end "one-click Deployment" with features such as an automated PXE-enabled operating system installation, DHCP services, orchestration Services, and puppet configuration management related services, in addition to OpenStack Very useful services such as critical business health checks and log real-time viewing.
Fuel 3.2 is based on the Grizzly version, and the latest release of the 4.0 version is based on the Havana version of the technical preview, not used as a production environment, and the 4.0 version still does not contain heat and ceilometer components.
Advantages of Fuel
To summarize, Fuel has several advantages:
- Automatic discovery and pre-calibration of nodes
- Simple and fast configuration
- Supports multiple operating systems and distributions, supports HA deployment x external API to manage and configure the environment, such as dynamic add compute/Storage node x comes with Health Check tool x support neutron, such as GRE and namespace are all in, subnets can be configured specifically to use which physical network card, etc.
What is the architecture of Fuel?
Fuel Master node: Used to provide PXE mode operating system installation Services are provided by Open source software cobbler, in addition to orchestration Services and configuration management services provided by Mcollective and puppet respectively. Fuel ISO package has been packaged together with the Centos6.4 and Ubuntu 12.04 installation package, if you need to use Red Hat Enterprise Edition RHEL6.4 need to manually upload.
The installation of OpenStack SA or ha can now be supported. Now that we have a general idea of fuel, let's look at how convenient it is to install OpenStack with her!
Fuel OpenStack Installation
The first thing to note is that the fuel target is the production environment OpenStack deployment, here to explain the installation process on the virtual machine to demonstrate the description. My environment is the HP Notebook folio 9470, in fact, is a common office notebook, the reader can modify the virtual machine configuration according to the actual machine situation, I gave my configuration for reference only.
Installation Instructions
Hardware requirements
- Enable virtualization support: Turn on Virtualization technology support options in the BIOS settings, which will greatly affect your virtual machine performance.
- Minimum hardware configuration: CPU: Dual core 2.6ghz+; memory: 4g+; Disk: 80g+
- Virtualization tools: Oracle Virtualbox 4.2.18
installation package Preparation
- Download VirtualBox Package https://www.virtualbox.org/wiki/Downloads/
- Download Fuel iOS package, first to register a Mirantis user account, currently the latest version is 3.2.1 This version, Mirantisopenstack-3.2.1.iso (1.8G) http://www.openstack.cn/p383.html
Installation steps
- Virtual Environment settings
- Installing the Fuel Master node
- Deploying OpenStack Nodes
- Deployment results Check
- Virtual Environment settings
Network topology
First, customize the following 3 networks in VirtualBox:
›Net1:
–Network name: VirtualBox host-only Ethernet Adapter#2
–Purpose: Fuel administrator network
–IP block: 10.20.0.0/24
–Linux device: eth0
›Net2:
–Network name: VirtualBox host-only Ethernet Adapter#3
–Purpose: public/ floating network
–IP block: 172.16.0.0/24
–Linux device: eth1
›Net3
–Network name: VirtualBox host-only Ethernet Adapter#4
–Purpose: Storage/ management/ internal network
–IP block: 192.168.4.0/24
–Linux device: eth2
Virtual Machine creation
›VM1
–Name: Fuel_3.2.1
–vCPU:1
–Memory :1G
–Disk:30G
–Networks: net1
›VM2
–Name : Fuel_3.2.1_controller
–vCPU:1
–Memory :1G
–Disk:30G
–Network:net1,net2,net3
›VM3
–Name: Fuel_3.2.1_compute1
–vCPU:2
–Memory :2G
–Disk:30G
–Networks:net1,net2,net3
Network topology
Create a network Net1, and be careful not to enable DHCP, which interferes with fuel's own DHCP service.
Create a network Net2
Create a network Net3
Installing the Fuel Master node
Create the fuel Master node virtual machine with the virtual machine name "fuel_3.2.1". Note that the network adapter chooses Net1, namely VirtualBox "VirtualBox host-only Ethernet adapter#2".
After setting up the virtual machine, display boot menu, if you need to modify the IP address can be modified by itself, the default is no need to modify.
Start installing the operating system
When this screen appears, press any key to change the configuration of the fuel master node, you can not modify the default value, and then install the package after a few seconds.
Puppet install fuel related software, such as cobbler.
Fuel Master node installation is complete.
To see if the fuel installation is complete, login http://10.20.0.2:8000/to display the following page.
Possible problems
- If the Web page does not access properly, it is possible that your local firewall has rejected the network, please disable the firewall and try again.
- If you are using a browser HTTP proxy, turn off direct proxy access.
The next step is to install the OpenStack environment.
Installing the OpenStack Environment
First create an OpenStack environment on the fuel web with the name "demo", which can be created in multiple, visible fuel can manage multiple openstack environments at the same time. There are three types of OS selected here, the default choice of CentOS, of course, you can choose Ubuntu and Rhle, but Rhle need to manually upload the image or provide Red Hat official website username and password, fuel for you to download automatically, but the time is longer, not recommended.
Here you choose to deploy OpenStack Multi-node non-ha mode.
Since we are running the virtual machine in the virtual machine, the hypervisor type of "Qemu" is chosen here.
Here we choose OpenStack Network deployment Mode, we choose the simplest way is also the most mature way nova-network implementation.
The last way is to use the default configuration without making changes to complete the environment creation.
Create an OpenStack node virtual machine VM2 and VM3, named Fuel_3.2.1_controller and Fuel_3.2.1_compute1, respectively, noting that compute nodes are more than allocating write CPU core, at least 2, memory 2G, Of course, if the machine is not configured enough it can be a core 1G memory, at least the instance behind creating OpenStack is slower.
Setup system starts from network
Configure network card 1, Access Net1, be sure to select the network card type: Pcnet-pci II, and turn on promiscuous mode: Allow All.node_vms_set_promiscuous.jpg
Configure network card 2, Access Net2.
Configure NIC 3, Access Net3
Let's start VM2 and VM3, respectively.
After the screen appears bootstrap login, fuel Web page can see the node is fuel discovered.
Back to fuel web to see two nodes found
The next step is to configure the OpenStack environment for the two discovered node vm2,vm3.
You first need to configure the roles of VM2 and VM3 in OpenStack. Click "Add Nodes" to add VM2 as the control node for OpenStack.
In the click "Add Nodes" add VM3 as the compute node for OpenStack.
Modify the mapping of the two-node physical network card and the OpenStack logical network, just drag-and-drop to get it done. The admin network has been set to eth0 can no longer be modified 10.20.0.0/24,public and instance floating network share eth1 and share the same address block 172.16.0.0/24, while private, management and storage common eth2 but the network IP is different, need to realize two layer network isolation through VLAN tag way.
Modify the partition of the two-node disk, where the default value is used, note that the storage partition cannot be less than 10g, otherwise it cannot be verified.
Again to configure OpenStack's most complex piece of network, in fact, according to my network topology to use the default value can be installed, is not very convenient? But it's still a bit verbose:
The public IP is used for physical machines and external communications, and floating IP is used to dynamically assign to OpenStack instance implementations and external communications. Note that address blocks cannot overlap here. Since private,management and storage share the same NIC and the IP block is different, to achieve two layer isolation requires the VLAN tag, if it is connected to the real switch, trunk mode must be enabled. Once the network configuration is complete and installed, this address is permanent can not change, so the production environment must first plan to deploy. After the configuration is complete, click on the "Networking Verification" button to check if the network settings are correct.
Verify that the deployment node is started by maintaining the settings after passing.
At this point, you can see that two VMS start to automatically restart to install the OS.
This is odd, the installation progress to 33% need to wait a long time to go down. This time the two-node OS has been installed.
Is there any way to see the installed log? Of course, you can go to log tag view to view the installation log, choose "Other Server", select the corresponding node puppet log to see the log bounce.
Finally, if everything goes well, the installation will be completed in about 20 minutes, but depending on the performance of the machine, click http://172.16.0.2 or http://10.20.0.4 to access OpenStack dashboard. The difference is 172.16.0.2 so-called public IP address, this post dashboard can use VNC access instance directly, and 10.20.0.4 not.
Click on the link to enter the OpenStack login page and enter admin/admin
At this point, the environment deployment of OpenStack is complete, where a compute node, a control node, is deployed. No cinder deployed, no multiple compute nodes deployed. If you need to deploy, repeat these steps.
Finally, verify that the OpenStack environment is properly deployed. In fact, fuel has a very good and a feature that can quickly detect the "health" situation of the OpenStack environment. Enter the Healthcheck label, can be a key security detection, note will not all pass, should be cinder not installed, so create volume related services will fail.
Finally, we're going to create a instance to prove it?
Installing OpenStack Environment Validation
After logging in, enter the OpenStack Manager interface, create a instance, and go to project view–> Open Instances tab and click the Luanch button at the top right. Instance name is Test0
After the instance is created successfully, click the "More" button on the right side of the instance test0 and select "Allocation floating IP" to assign a floating IP address.
Directly in the Web page Access instance: Click on the right end of the "more" and "Console" button to enter the page, which is a web socket technology implementation of the VNC client, with it can do some simple instance management, insufficient to paste the copy is more troublesome.
Finally open a "cmd" terminal on the notebook to see if the floating IP is unobstructed.
At this point, the fuel web OpenStack installation is complete, and if you want to install more nodes, repeat the above steps.
Other tools
Of course, the OpenStack installation tool is not just fuel, but the packstack of the Red Hat is also good, and supports the latest version of OpenStack installation. Here is an article on the two to make a more comprehensive introduction of http://www.openstack.cn/p383.html.
Reference documents
http://openstack-huawei.github.io/mirantis-openstack/
http://software.mirantis.com/quick-start/
Http://www.openstack.cn/p383.html
Transfer from http://yongluo2013.github.io/quick-setup-openstack-with-fuel-in-30-minutes/
Fuel 30-minute quick-install OpenStack