OpenStack Installation Deployment Tutorial

OpenStack Installation Deployment Tutorial

OpenStack is a free software and open source project, developed and launched by NASA and Rackspace, in collaboration with the Apache license. At the same time, OpenStack is an open-source cloud computing management platform that supports almost all types of cloud environments with the goal of delivering simple, scalable, rich, standard, unified cloud management platforms. OpenStack is designed to provide software for the construction and management of public and private clouds, helping service providers and businesses to implement cloud infrastructure services similar to Amazon EC2 and S3 (infrastructure as Aservice, IaaS). However, because the OpenStack installation process is cumbersome, the purpose of this article is to introduce the Mirantis service integrators developed a set of OpenStack installation tool fuel to complete the OpenStack installation deployment.

A OpenStack Technical Data

OpenStack version (Icehouse)

OpenStack Object Storage (Swift)

OpenStack Computing Services (Nova)

OpenStack Mirroring Service (glance)

OpenStack Operating Interface (Horizon)

OpenStack Identity Certification (Keystone)

OpenStack Network Service (neutron)

OpenStack Block Storage (Cinder), providing block data access

OpenStack Telemetry (ceilometer), providing metering and monitoring functions

OpenStack Orchestration (Heat), provides automatic extension of virtual machine function

OpenStack database Service (TROVE), which provides data management capabilities

Two Installation tools Fuel

Mirantis, a top 5 OpenStack service Integrator in the OpenStack community, has been dedicated to providing small and large enterprises with open source projects to develop and manage the platform needed for cloud infrastructure services since its inception in January 2011. As one of the founding companies of the OpenStack project, Mirantis has developed more than 30 OpenStack deployment projects.

Fuel is a OpenStack automated deployment tool that includes PXE installation of operating systems, DHCP services, business health checks, and log viewing, as well as using puppet to install each node, as shown in Figure 1.

Figure 1:fuel Frame composition

Three Basic Environment

(1) We built the OpenStack environment as an example, a total of 5 machines, one as fuel Master, one as controller node, the other three as compute node. One of the basic requirements for hardware is to have three physical network ports (except fuel Master), the other is not very large requirements, the theory is certainly higher, the speed of the operation will be faster, before the installation of a note is to the BIOS virtualization support to open. The physical configuration of the 5 machines is shown in table 1.

(2) Fuel master image. To the official website download ISO image, which contains OpenStack installation package, CentOS installation package, we use here is the MirantisOpenStack-6.0 version of the mirror, and then burn it in the U disk inside, installed fuel master time will be used. Add: Fuel is the OpenStack Automated deployment tool for the target is the production environment OpenStack deployment, it is based on the Web interface, free and open source, the function is quite rich.

(3) In this OpenStack environment, we have created 3 virtual machines for MONGODB deployments. The three virtual machines are master,secondary and MONGOs respectively. The two virtual machines, master and secondary, serve as MongoDB data nodes, MONGOs as the MongoDB front-end route, where the client is connected, and the three virtual machines as MongoDB Config Server store the entire Cluster Metadata, which includes chunk information.

Node

Ip

Hard disk size (T)

Memory (G)

CPU Kernel Count

Number of network ports

Fuel Master

10.20.0.2

0.4

4

2

1

Controller

10.20.0.3 192.168.1.2

192.168.2.2

192.168.3.2

0.4

4

2

3

Compute1

10.20.0.3.4

192.168.1.3

192.168.2.3

192.168.3.3

0.5

26

4

3

Compute2

10.20.0.5 192.168.1.4

192.168.2.4

192.168.3.4

0.5

32

4

3

Compute3

10.20.0.6 192.168.1.5

192.168.2.5

192.168.3.5

0.5

8

4

3

Table 1: Machine configuration tables

The configuration of 3 virtual machines is shown in table 2.

Node

Ip

Hard disk size (T)

Memory (G)

CPU Kernel Count

Master

10.0.0.2

192.168.3.128

0.1

16

2

Secondary

10.0.0.4 192.168.3.191

0.1

16

2

MONGOs

10.0.0.6

192.168.3.192

0.05

4

2

Table 2: Virtual machine configuration table

The network topology structure of this OpenStack environment is shown in Figure 2.

Figure 2: Network topology structure diagram

Four Installing the deployment process

(1) Install fuel Master

Install fuel Master is to use our previously carved USB disk to install, the installation process does not have much to interfere with the place, that is, the normal installation of the system steps, after loading as shown in Figure 3.

Figure 3:fuelmaster Installation Successful

There will be a fuel UI address, which is actually the admin interface when we deploy OpenStack other nodes, and the interface after login is shown in Figure 4.

Figure 4: Login Fuel UI

Next through this web interface, we can create a new OpenStack environment, named "Demo", this environment can create multiple, visible fuel can manage multiple openstack environments 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.

First select the CentOS system, as shown in Figure 5.

Figure 5: Selecting the operating system

Second, select deployment mode, multiple nodes can be used for testing/development, HA can be used directly in the production environment, because we are also in the testing phase, so select the deployment of OpenStack multi-node non-ha mode, as shown in Figure 6.

Figure 6: Choosing a Deployment Mode

Since we are loading OpenStack on the physical machine, here Select the hypervisor type "KVM" as shown in Figure 7.

Figure 7: Selecting the hypervisor type

Then the network mode selection, we choose the simplest way is currently the most mature way nova-network implementation, as shown in Figure 8.

Figure 8: Select network mode

The remaining configurations follow the default selection, creating a good openstack environment as shown in Figure 9.

Figure 9:openstack Environment

What we can see is that in this environment, there are no physical nodes added, and then we start deploying other nodes.

(2) Deployment of OpenStack nodes (1 controller,3 computer)

We use a router to connect fuel master with the other four machines, note that the router's DHCP disabled, and the router with a static IP, can be equipped with 10.20 0.1, to facilitate the other computers connected to the fuel UI, for management. The four machines are then booted from the network, as shown in Figure 10.

Figure 10: Node Network startup

In this step, the machines load a small kernel from fuel master, which collects some of the machine's parameters to fuel master for management. When the bootstrap login appears on the machine, the fuel Web page can see the node being fuel discovered.

We return to the fuel web interface and we can see that 4 new nodes are found in the upper-right corner. Then we start adding nodes and the operation interface is shown in Figure 11.

Figure 11: Adding Physical nodes

We take one node as the controller node, the other three nodes as compute nodes, and the type selection of the nodes as shown in Figure 12.

Figure 12: Node type selection

Next we want to verify the entire OpenStack environment, at this time we first use a switch to connect 4 nodes intranet, then use a router to connect the extranet network card, and disable the router's DHCP service, and configure the WAN. After this network is connected, we modify the network configuration of each machine as shown in Figure 13.

Figure 13: Node Network configuration modifications

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, while private, management and storage shared eth2 But the network IP is different, need to realize two layer network isolation through VLAN tag way.

When the above network is well matched, we will also have to correspond the above network one by one in the networks, as shown in Figure 14.

Figure 14:openstack Network Configuration

After the last network verification is passed, the deployment can begin, and the process of deployment is to upload the CentOS and OpenStack on 4 nodes. (This process does not require too much interference, but to pay attention to the process of loading the system, the machine will restart, to ensure that the restart when the network to start)

Note: 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 Private,management and storage share the same network card and the IP block is different to achieve two layer isolation needs to play on the VLAN tag. Once the network configuration is complete and installed, this address is permanent can not be changed, so the production environment must first plan well before deployment. When Figure 15 o'clock shows that the deployment has been successful, this time you can go to dashboard and the login interface is shown in Figure 16.

Figure 16: Deployment Success Map

Figure 16:dashboard Login Interface

(3) Deployment Results validation

After entering the dashboard, you start creating the instance, after you create the instance, you need to install the operating system for the instance, and note that OpenStack virtual machine mirroring needs to be made by itself. In the construction process, is downloaded from the Internet has been made a good centos6.5 mirror, installed four virtual machines, after which the three virtual machines inside the installation of MongoDB. More work on dashboard also requires in-depth study.

Dashboard's operating interface is shown in Figure 17.

Figure 17:dashboard Operation interface

This is the end of the fuel web OpenStack installation, and if you want to install more nodes, repeat the above procedure.