Quickly deploy an openstack cluster with Fuel

1 Deployment planning

Fuel node: It is only used when deploying OpenStack to other nodes, so prepare 1 node as the Fuel
Controller node: the management node of openstack, the
Compute node to be used for HA in production: the computing node of openstack, in production If there are multiple computing nodes, create a virtual machine instance
Storage node on it: the storage node of openstack. In production, a storage cluster should be formed, and the object storage and block storage should be separated into different clusters.

Node Name
Configuration
Network
Ip Address
Fule
2G, 50G disk
PXE network
192.168.10.5
Collector
1G, 50G disk
4 NIC
Fule allocation
Computer
4G, 50G disk
4 NIC
Fule allocation
Storage
1G, 50G disk
4 NIC
Fule allocation

Network device
Network type
Network segment Belonging
node
Vmnet1
PXE network
192.168. 10.0
All
Vmnet2
public network network
192.168.20.0
All
Vmnet3
management network
192.168.30.0
All
Vmnet4
storage network
192.168.40.0
All


VMware configuration


We only use VMnet1, VMnet2, VMnet3, VMnet4 these 4 network devices

2 Install Fuel

2.1 VMware creates Fuel nodes

on windows Create a Fuel virtual machine on VMware workstations
Key points :
         1) Custom configuration
         2) Linux system
         3) Install the operating system later
         4) HostOnly network (others are also OK)
         5) The memory is first given 8G (after installing the fuel, adjust it down), The installation speed is fast
         6) The disk is 40G, which may only occupy about 20G. After the
creation is completed, add the ISO image file of Fuel to it.

2.2 Start the Fuel node

Note : After starting the Fuel node and entering the welcome interface, press the Tab key.

You can see that the ip is assigned to it below. address, gateway, hostname, etc, and it's also installed via the ks.cfg file
The following network settings for the Fuel node are as follows:
Ip address: 192.168.10.5
Gateway address: 192.168.10.2
Subnet mask: 255.255.255.0
DNS: 8.8.8.8
Hostname: fuel.gyq.com


After configuration, press Enter Start installing Fuel

In fact, Fuel is a Centoslinux system with openstack software installed. In the future, Fuel will use Docker to deploy the OpenStack application on it to the nodes that communicate with it. Wait for a while to complete the installation

2.3 Log in to Fuel

2.3.1 Log in to the Fuel node

After the Fuel installation is complete, you can see the prompt information: UI address, root password, UI user name and password

Prompt root user password: r00tme, Fuel UI's Username and password: admin
Use the root user to log in to the Fuel node. If you

log in successfully, you can see the hostname of the Fuel node, which is exactly what we configured.
View the network
#ip addr ,

you can see so many network device information
2.3.2 Log in to the Fuel monitoring page After


installing Fuel , you can see the address that prompts the Fuel UI: http://192.168.10.5:8000, the username and password are both admin
, access on the browser : http://192.168.10.5:8000

Ok, you can successfully access the Fuel UI
Enter username and password: admin

After logging in, you will see the prompt message, cancel the Send usage statisitcs, click Start Using Fuel


2.4 to create a new OpenStack environment,

click the

OpenStack version of the new OpenStack environment, select CentOS6.5, and move forward.

We only plan one openstack management node Controller, so we do not choose HA. node.

Choose to use KVM, go forward

Select Neutron GRE,

use the default storage, go forward

Do not install these additional services for now, go forward

Ok, click New to complete the creation

Now , Fuel is waiting for other nodes to connect to it
Prepare each node of Openstack
3 Start each node of openstack

3.1 Prepare each node of openstack Create three virtual machines, Controller, Computer and Storage respectively

in VMware
Note:
         1) Add 4 network cards to all three nodes, use vmnet1, vmet2, vmnet3, vmnet4 respectively, they are all in Host Only mode
         2) Computing The node Computer will create a virtual machine instance in the future, so its CPU must be enabled to support hardware-assisted virtualization.
         3) All three nodes choose to install the operating system later, and do not add an ISO image file to it. The Fuel node will install the most Jane OS
         4) It must be ensured that the 4 network cards are all self-starting at boot
Controller node:
allocate 1G memory, 50G disk, 4 network cards, no system mirroring

Computer node:
allocate 6G memory, 50G disk, 4 network cards, do not add system mirroring, and enable CPU support for hardware-assisted virtualization

Storage node:
allocate 1G Memory, 50G

disk, 4 network cards, no system image added After the Fuel node is started, the PXE server is started. The ip address of Fuel is 192.168.10.5, and the three nodes of openstack have an ip address of 10 network segments, so after these three nodes are started, they will communicate with Fuel. The PXE service of the nodes communicates with each other, and then Fuel will assign them an ip address according to the simplest operation system respectively. After ensuring that the Fuel nodes are started, start them. 3.2.1 Start the Controller node After starting the Controller node, it defaults to Send broadcast information to the Fuel node through network boot, and the fuel node uses PXE to install the operating system for it. The Collector node is started up. It is found that there is an error reported by the Controller node. This is that the time cannot be synchronized. We are not connected to the network, so we can't synchronize. Don't care about it. You can see that the Fuel node has installed an operating system on the Controller node. Check the UI interface of Fuel, you can see Fuel found 1 node

















This node is the Controller node that we started. Next, we will start the Computer node.

3.2.2 Start the Computer node . The


Computer node is started, and the time cannot be synchronized. It doesn't matter.
Looking at the UI of Fuel,

you can see that Fuel has detected the second node, which is what we started. Computer node
3.2.3 Start the Storage node


Ok, the Storage node is also started successfully, check the Fuel UI interface

Fuel all detected 3 nodes

4 Fuel add node

4.1 Add node

4.1.1

Add The address suffix determines which node is the node

according to the last two digits of the mac address of the network card to determine which node we plan, and then assigns the corresponding role, such as f7:f1 is the mac address of the controller node eth1 network card The last 2 are, So assign the Controller role to it.


Click "Apply Changes"

to see that the node is assigned the Controller role.
4.1.2 Adding Storage Nodes


After checking, we know that 3b:c8 is the Storage node, and we assign it the Storage role

. Click "Apply Changes" "

You can see that this node is assigned the role of Storage-Cinder .

4.1.3 Add a Computer node.


The remaining 6G memory node is the Computer node we planned.


Assign the Compute role, and click "Apply Changes" to see that the node

is assigned the Compute role.

4.2 Assign network Perform network settings for each network card

of each node ” Drag the network card type to click Apply 4.2.2 4.2.3 The same reflection 4.3 Network settings 4.3.1 Public network According to our network planning, the public network is the Vmnet2 device address: 192.168.20.0 The IP range of the public network is to give The public network address CIDR assigned by other service nodes of openstack is the network segment and subnet mask of the public network network. When creating a new Openstack environment, the network selected is Nutron GRE, which only supports tags, but does not support Vlan, so do not check the gateway address is Vmnet2 ip address 4.3.2 Management and storage network The management network uses the Vmnet3 network device, the address is: 192.168.30.0 The storage network uses the VMnet4 storage network, the address is: 192.168.40.0 4.3.3 The intranet and Floating IP intranet address is to The network floating IP range allocated to the virtual machine instance is to implement DNAT for the virtual machine created by openstack through Neutron, and to give the floating IP address of the internal virtual machine



































4.3.4 Verify the network


Click "Verify the network"

Ok, the verification is successful, click "Save Settings"
4.2.5 Deploy Change



Click Deploy Change

Click Deploy,

you can see that 4% has been installed

and slowly wait for the Fuel node to deploy openstack to these three On the node...
5 openstack operations

5.1 Log in to openstack to monitor

the Fuel deployment. After the completion of the Fuel deployment, you can see the following prompt


Deployment of environment 'my-openstack' is done. Access the OpenStack dashboard (Horizon) at http://192.168.20.2/ or via internal network athttp://192.168.10.2/
Seeing such a prompt, it means that Fuel has successfully deployed openstack, and the Fuel node can be closed.
According to the prompt: visit http://192.168.20.2, which is the monitoring interface of openstack.

The username and password are both admin, log in to openstack


5.2 Create an instance on openstack

5.2.1 Create an Instance

Click Project -> Compute -> instance

to see that there is no Any instance
1) Click "Launch Instance" to create an instance


Availability Zone: is the available resource zone, the default resource zone is nova
Flavor: equivalent to the computing solution in cloudstack, we choose m1.micro which is the smallest computing solution, you can see that the memory is only 64M
Instance Boot Source: Instance image boot, We choose the image that comes with the storage node, only TestVM.

2) Click the "Access & Security" tab and


select default security group default
3) Click "Networking"


where net04 is the internal network card and net04_ext is the external network card. We only add an internal network to this instance.
4) Click "Post-Creation"


here is the script executed after the instance created by the configuration is started, we will not execute any script for the time being
5) Click the "Advanced Options"


advanced option to configure automatic disk partitioning, this option is optional.
6) Click "Launch" to start the instance.


You can see that the instance spark01 is being created. After the creation is completed, you can see the information

of the instance. The intranet IP address is assigned: 10.0.0.3, and the Power state is Running
. In the Actions option of the virtual machine, click Console

Prompt to connect to it through vnc

5.2.2 Assign an external IP address to the virtual

machine Click "Associate Floating IP" in the Actions option of instance spark01

If there is an already obtained Floating IP in the IP Address drop-down list, you can choose to use it.

If is no ip address in the drop-down list, click "+" on the right to get an IP address from the Floating IP Range
Click "+"

to select Pool, the default There is only this one net04_ext, which is the external network ip pool.
Click "Associate IP",

you can see that an IP address of a public network has been obtained from the net04_ext pool: 192.168.20.102. In fact, it is obtained from the Floating IP Range. Select this IP address to assign to the spark01 instance.
Click "Associate" "Button

Ok, you can see that the public IP address we obtained appears in the IP Address of instance spark01: 192.168.20.102
The principle is to serve the DNAT implemented by the virtual machine instance saprk01 through the network component Neutron of openstack, and forward the Floating ip to spark01. 's intranet address.
5.2.3 Communication between the external network and spark01 After adding the external network IP address

to the instance Spark01, use the cmd command line ping on Windows to

see that the ping is different, because the default security group default was selected when the instance was created.
1) Configuration Security group

Click Project -> Compute -> Access & Security

to see the default security group: default, click "Manage Rules" in its Actions column

You can see the rules that come with these default security groups, click "Add Rule" to add a rule