Fuel Quick Install OpenStack graphics and text tutorial _openstack

1 Introduction

1.1 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's 1.2Fuel?

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 1.3Fuel

To sum up, Fuel has the following advantages:

Node automatic discovery and pre-verification configuration simple, fast support for a variety of operating systems and distributions, support HA deployment x external API for the environment management and configuration, such as dynamic add compute/Storage node x Self Health Check tool x support neutron, for example, GRE and namespace are all in it, Subnet can configure the specific use of the physical network card, etc.

What is the 1.4Fuel architecture?

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!

2 Fuel OpenStack Installation

2.1 Installation Preparation

Hardware requirements:

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 5

installation package Preparation:

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

2.2 Network topology

This installation uses the simplest way, 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 computing node, the real resources to use.

Figure 1 Deployment topology

The following are network planning:

Figure 2 Network configuration

2.3 Virtual Machine Setting

Three node configuration is as follows, can be appropriately increased resource settings:

2.4 Installation Steps

Create Fuel_master, as shown in Figure 3~4:

Figure 3

Figure 4

Create three virtual network cards, respectively corresponding to Net1~3, the original NIC does not move, pay attention to shut down the DHCP service; setup See figure 5~7:

Figure 5

Figure 6

Figure 7

Set Fuel_master Network, a total of three network cards, network card 1 attention to control chip options, allow promiscuous mode, as shown in Figure 8

Figure 8

Network card 2, 3 by default, as shown in Figure 9, 10:

Figure 9

Figure 10

Load the ISO file as follows:

Figure 11

Note: If you encounter Figure 12 prompts, please increase disk space

Figure 12

The Fuel_master installation is successful as shown in Figure 13:

Figure 13

You need to access the 10.20.0.2:8000 page in the previous illustration, but the port may not be open and can be accessed through the Xshell tunnel settings, as shown in Figure 14/15:

Figure 14

Figure 15

You can log in, as shown in Figure 16:

Figure 16

Enter the home page, as shown in Figure 17:

Figure 17

Start OpenStack Configuration, new environment, named demo, version here select CentOS, see Figure 18 below:

Figure 18

Select multiple nodes here, Figure 19:

Figure 19

Because the environment is a virtual machine, select Qemu, as shown in Figure 20:

Figure 20

The network environment, as shown in Figure 21, uses the GRE basic network, which can be selected according to the actual environment:

Figure 21

Back-End storage default, Ceph not used:

Figure 22

Additional services not selected, see Figure 23:

Figure 23

Complete Setup

Figure 24

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

Figure 25

Create a new Fuel_controller node and set the reference Fuel_master, as shown in Figure 26~28:

Figure 26

Figure 27

Figure 28

You need to set up a network boot, as shown in Figure 29:

Figure 29

Note Initialize the Mac, as shown in Figure 30:

Figure 30

New Fuel_compute node, set see Figure 31~32:

Figure 31

Figure 32

Prepare to add nodes:

Figure 33

Create a new compute node and select the corresponding resource, as shown in the following figure:

Figure 34

You need to set up the network, here for simplified settings, you can set Figure 37:

Figure 35

Figure 36

Figure 37

What needs to be changed here is the DNS server settings, as shown in Figure 38:

Figure 38

Finally verify the network and succeed to continue:

Figure 39

When the application is complete, the node starts to deploy, showing the progress shown in Figure 40:

Figure 40

Upon completion, as shown in Figure 41, and prompted to login to the URL

Figure 41

Login URL, that appears OpenStack login interface, the following figure:

Figure 42

To this, has entered the OpenStack management interface, the environment deployment formally completes.

Figure 43

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.