All along, for OpenStack beginners, installation is often the first big problem of getting started. Before the E version, to build a basic OpenStack environment that is quite troublesome, they have to install, their own source, according to the document to knock orders, and there is no reliable documents, the official documents still have a lot of pits, and language problems often with a few days of time can not be installed, Slowly lost the confidence to learn OpenStack!
However, the situation has changed a lot, starting from the E version, the installation process after a lot of simplification, the quality of the document improved a lot. Although this is still more complex for beginners, in fact many times, many people just want to experience the OpenStack, completely do not pay attention to the installation of this thing. Fortunately OpenStack community is active enough, soon have the company made a relatively friendly installation tools, such as today to introduce the fuel this tool, in fact, here can also call her Mirantis OpenStack, by the Mirantis company development.
About Mirantis
Mirantis, a great OpenStack service integrator, is the only one of the top 5 community contributors to eat on software and services (others are red Hat, HP, IBM, Rackspace). Compared to several other community distributions, the fuel version is fast-paced and provides a relatively stable community version every two months.
What is Fuel?
Fuel is a tool designed for OpenStack End-to-end "one-click Deployment" that features an automatic PXE-enabled operating system installation, DHCP service, orchestration Services, and puppet configuration management-related services, in addition to OpenStack Critical business Health Check and log real-time view and other very useful services.
Fuel 3.2 is based on the Grizzly version, and the latest release of 4.0 is based on the Havana version of the technology Preview, not used in the production environment, and the 4.0 version still does not contain heat and ceilometer components.
Advantages of Fuel
To sum up, Fuel has the following advantages:
- Automatic discovery and pre-verification of nodes
- Simple and fast configuration
- Support for HA deployments with multiple operating systems and distributions
- Externally provided APIs to manage and configure the environment, such as dynamically adding compute/storage nodes
- Self-carrying Health check tool
- Support for neutron, such as GRE and namespace are all done, subnet can configure the specific use of the physical network card, etc.
What is the structure of the Fuel?
Fuel Master: A PXE-mode operating system installation service is provided by the open source software cobbler, and orchestration Services and configuration management services are provided by Mcollective and puppet respectively. Fuel ISO packaging has been packaged together with the Centos6.4 and Ubuntu 12.04 installation package, if you need to use the Red Hat Enterprise version RHEL6.4 need to manually upload.
The installation of OpenStack SA or ha can now be supported. Now we have a general understanding of fuel, now to see 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 demo. My environment is HP Notebook Folio 9470, in fact, is the ordinary 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
Enable virtualization Technical Support: Open the Virtualization Technology support options in the BIOS setup, which will largely affect your virtual machine performance.
Minimum hardware configuration: CPU: Dual-core 2.6ghz+; RAM: 4g+; Disk: 80g+
Virtualization tools: Oracle Virtualbox 4.2.18
Download VirtualBox Package
Https://www.virtualbox.org/wiki/Downloads
Download Fuel iOS package, first to register a Mirantis user account, the latest version is 3.2.1 This version, Mirantisopenstack-3.2.1.iso (1.8G)
Http://www.openstack.cn/p383.html
- Virtual Environment settings
- Installing the Fuel Master node
- Deploying OpenStack Nodes
- Deployment results Check
Virtual Environment settings
First, the following 3 networks are customized in VirtualBox
–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
›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
The network topology is as follows
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 virtual machine, the virtual machine name is "fuel_3.2.1". Note that the network card chooses Net1, namely VirtualBox "VirtualBox host-only Ethernet adapter#2".
After setting up the virtual machine, show boot menu, if you need to modify the IP address can be modified, the default is no need to modify.
Start installing the operating system
When the screen appears, press any key to enter the modified fuel primary node configuration, you can use the default value without modification, a few seconds after the package installation.
Puppet install fuel related software, such as cobbler.
Fuel the master node is installed.
To see if the fuel installation is complete, log on http://10.20.0.2:8000/display the following page.
Possible problems:
- If the Web page is not normal access, it may be your native firewall to the local network refused, please disable the firewall and try again.
- If you are using a browser HTTP proxy, turn off proxy direct access.
Then you start to install the OpenStack environment.
Install OpenStack Environment
First of all, create a openstack environment on the fuel web, named "Demo", this environment can create multiple, visible fuel can manage multiple OpenStack environment at the same time. There are three of the OS selected here, the default selection CentOS, of course, you can also choose Ubuntu and Rhle, but Rhle need to upload a mirror manually or provide Red Hat official website username and password, fuel for you automatically download, but the time is longer, not recommended.
Here you choose to deploy the OpenStack multi node non-ha mode.
Since we are running the virtual machine again in the virtual machine, choose hypervisor type "QEMU" here.
Here choose OpenStack Network Deployment Mode, we choose the simplest way is also the most mature way nova-network implementation.
Last use default configuration, do not make changes to complete the environment creation.
Create OpenStack node virtual machines VM2 and VM3, respectively named Fuel_3.2.1_controller and fuel_3.2.1_compute1, note that compute nodes are allocated to write CPU core, at least 2, memory 2G, Of course, if the machine configuration is not enough can also be a core 1G memory, at least behind the creation of OpenStack instance relatively slow.
Configure network card 1, Access Net1, note must choose the type of network card is: Pcnet-pci II, and open promiscuous mode: Allow all.
Configure network card 3, Access Net3
The screen appears bootstrap login, fuel Web page can see the node was fuel found.
Back to fuel web can see two nodes being found
The next step is to configure the OpenStack environment for the two discovered nodes vm2,vm3.
First you need to configure the roles of VM2 and VM3 in OpenStack. Click "Add Nodes" to add VM2 as OpenStack control node.
Click "Add Nodes" to add VM3 as the OpenStack compute node.
Modify the mapping relationship between the two-node physical network card and the OpenStack logical networks, just drag and drop. 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 share eth2 but network IP is different, need to use VLAN tag way to achieve two layer network isolation.
Modify the partition of the two-node disk, using the default value, note that the storage partition cannot be less than 10g, otherwise it cannot be validated.
And then configure the OpenStack the most complex piece of network, in fact, according to the network topology I gave the default value can be installed, is not very convenient? But still to be long-winded:
- Public IP is used for physical machine and external communication, floating IP is used to dynamically assign to OpenStack instance implementation and external communication. Note that the address block cannot overlap.
- Because of private, management and storage share the same network card and IP block to achieve two layer isolation need to play on the VLAN tag, if it is connected to the real switch, you must enable the trunk mode.
- Once the network configuration is complete and installed, this address is permanent can not be changed, so the production environment must first plan good deployment.
When the configuration is complete, click the "Networking Verification" button to check that the network settings are correct.
After the validation passes, the settings are persisted and the node is deployed.
At this point, two VMs can be found to start automatic reboot and start installing the OS.
It's odd, and it will take a long time to get down when the installation progresses to 33%. At this time two nodes of the OS have been installed complete.
Is there any way to see the installed log? Of course, at this time can go to Log tab view to view the installation log, choose "Other Server", the corresponding node in the selection of the puppet log log bounce.
Finally, if all goes well, the installation will be completed in about 20 minutes, but depending on the machine performance, clicking http://172.16.0.2 or http://10.20.0.4 can access the OpenStack dashboard. The difference is 172.16.0.2 so-called public network IP address, this post dashboard can directly use VNC access instance, and 10.20.0.4 can not.
Click on the link to enter the OpenStack login page and enter admin/admin
At this point, the OpenStack environment deployment is complete, where a compute node, a control node, is deployed. Cinder is not deployed and multiple compute nodes are not deployed. If you need to deploy, repeat the steps above.
Finally, verify that the OpenStack environment is properly deployed. In fact, fuel has a very good and a function, can quickly detect OpenStack environment "health" situation. Enter the Healthcheck label, can be a key security detection, attention will not all pass, should be cinder not installed, so create volume related services will fail.
Finally, let's create a instance to prove it.
Installation OpenStack Environment Verification
First login to enter the OpenStack Supervisor interface, create a instance, enter project View–> Open Instances tab-> Click the upper right Luanch button. Instance name is Test0
Instance after the successful creation, click on the corresponding instance test0 the "more" button on the right, select "Allocation floating IP", assign it a floating IP address.
Directly in the Web page Access instance: Click on the right side of the "more"-> "console" button to enter the page, this is the web socket technology to achieve the VNC client, with which it can do some simple instance management, the problem is not able to paste copy more trouble.
Finally in the notebook to open a "cmd" terminal to see if the floating IP unobstructed.
This is the end of the fuel web OpenStack installation, and if you want to install more nodes, repeat the above procedure.
Other tools
Of course, the OpenStack installation tool is not only fuel, but also has a red Hat packstack is also good, and support the latest version of the OpenStack installation.
Original link: http://www.tuicool.com/articles/rYb26j
The above is the entire content of this article, I hope to help you learn, but also hope that we support the cloud habitat community.