Fuel Quick Mount OpenStack

1 Introduction 1.1 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 1.2 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 1.3 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 the 1.4 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!

2 Fuel OpenStack Installation 2.1 Installation Preparation

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 5

installation package Preparation:

Download fuel ISO Package, currently the latest version is 8.0 this version, download link: https://software.mirantis.com/releases/#supported; This practice uses a more stable version of 5.1.1.

2.2 Network topology

This installation uses the simplest method, does not involve ha, only for multi-node deployment. Fuel_master node as a PXE server and management, Fuel_controller is the OpenStack control node, Fuel_compute is the compute node, the real resources to use.

Figure 1 Deployment topology

Here is the network planning:

Figure 2 Network configuration

2.3 Virtual machine settings

The three nodes are configured as follows to properly increase the resource settings:

2.4 Installation Steps

Create Fuel_master,3~4:

Figure 3

Figure 4

Create three virtual network card, corresponding to Net1~3, the original network card does not move, pay attention to turn off the DHCP service; settings See Figure 5~7:

Figure 5

Figure 6

Figure 7

Set Fuel_master Network, a total of three network cards, NIC 1 note control chip options, allow promiscuous mode, 8

Figure 8

Nic 2, 3 default, 9, 10:

Figure 9

Figure 10

Load the ISO file as follows:

Figure 11

Note: If you encounter the hint in Figure 12, increase disk space

Figure 12

Fuel_master installed successfully will be shown in 13:

Figure 13

In this case, you need to access the 10.20.0.2:8000 Web page, but the port may not be open and can be accessed through the Xshell tunnel settings, 14/15:

Figure 14

Figure 15

Can log in, 16:

Figure 16

Go to homepage, 17:

Figure 17

Start OpenStack Configuration, new environment, named demo, version here to choose CentOS, see 18:

Figure 18

Select multiple nodes here, Figure 19:

Figure 19

Since the environment is virtual machine, choose Qemu as shown in Figure 20:

Figure 20

Network Environment 21, which uses the GRE base network, can be selected according to the actual environment:

Figure 21

Back-End storage default, Ceph not used:

Figure 22

Additional services are not selected, see Figure 23:

Figure 23

Complete Setup

Figure 24

When you are finished, you need the node in the demo to start the new node

Figure 25

To create a new Fuel_controller node, set the reference fuel_master,26~28:

Figure 26

Figure 27

Figure 28

Need to set up network boot, 29:

Figure 29

Notice the initialization of the mac,30:

Figure 30

To create a new Fuel_compute node, see figure 31~32:

Figure 31

Figure 32

To prepare for adding nodes:

Figure 33

Create a new compute node and select the corresponding resource, such as:

Figure 34

You need to set up the network, here is the simplified setting, you can set Figure 37:

Figure 35

Figure 36

Figure 37

What needs to change here is the DNS server settings, 38:

Figure 38

Finally verify the network, the success can continue:

Figure 39

After the application is complete, the node starts to deploy and the progress display in Figure 40 appears:

Figure 40

When done, 41 is shown, and the login URL is prompted

Figure 41

Login URL, the OpenStack login interface appears, such as:

Figure 42

To this, the OpenStack management interface has been entered and the environment deployment is formally completed.

Figure 43

Fuel Quick Mount OpenStack