Openstack deployment Summary: Install the Icehouse (ml2 + GRE) with rdo on centos 6.5)

This article mainly introduces how to install a dual-computing node icehouse environment through rdo on centos6.5. Because of the many software involved in the installation process, the network mode adopts ml2 + GRE, and the dependency is complex. We recommend that you use a new operating system for installation.

 

Hardware environment

Two Dell r720 server machines, each with four NICs, only Em1 and EM2, and both NICs are connected with a network cable. Em1 is used for public networks and management networks, and EM2 is used for Virtual Machine networks.

In terms of vswitches, only one vswitch is used for the reason of the condition. However, in theory, the efficiency of separating Em1 and EM2 is higher.

Server	Public Network/Management Network	VM net	Role
Server 1	Em1: 192.168.100.242	EM2: 10.1.1.2	Control nodes, network nodes, storage nodes, and computing nodes
Server 2	EM2: 192.168.100.244	EM2: 10.1.1.3	Computing node

An obvious difference from VLAN configuration is that eth1 requires a private IP address, which must be configured.

Because the GRE mode is used, you do not need to bother configuring the trunk

 

A simple logic diagram is taken from the diagram of Mr Chen's blog (ignore IP addresses and device names)

Communication between virtual machines is through eth1 (corresponding to my environment is EM2). virtual machines access external networks through the l3agent on Server 1, br-ex to eth0 (corresponding to my environment is Em1) to access the external network

 

The installation procedure is as follows.

When partitioning, You need to divide a logical zone and create a group named cinder-volumes. This logical volume group will be used by cinder.

The created results are similar:

For the creation process see: http://www.centos.org/docs/5/html/Deployment_Guide-en-US/s1-lvm-diskdruid-manual.html

You can also create an ECS instance by running commands after installing the operating system.

Modify fstab

Modify/etc/fstab to remove the boot mount of cinder-volume, otherwise you will not be able to restart

Sed-I '/cinder-volume/S/^/#/'/etc/fstab

Configure the network

The two servers have the same configuration, but the IP address is different from hwaddr/UUID. Configure VI/etc/sysconfig/network-scripts/ifcfg-em1 as follows:

 

DEVICE=em1HWADDR=C8:1F:66:E5:29:0DTYPE=EthernetUUID=63d91b69-5c37-437e-898b-65403cef29a0ONBOOT=yesBOOTPROTO=staticIPADDR=192.168.100.242GATEWAY=192.168.100.1NETMASK=255.255.255.0DNS1=8.8.8.8 

Configure VI/etc/sysconfig/network-scripts/ifcfg-em2 and edit as follows

DEVICE=em2HWADDR=C8:1F:66:E5:29:0ETYPE=EthernetUUID=b2cdb6e2-37d9-4fd0-b3d6-01f107ed80e0ONBOOT=yesBOOTPROTO=staticIPADDR=10.1.1.2NETMASK=255.255.255.0DNS1=8.8.8.8

After the above configuration, confirm that the network can be connected.

The NetworkManager service can be stopped when the instance is running, so that useless services of this service will occupy a large amount of memory.

chkconfig NetworkManager off  

Install related Yum sources

Whether the yum source is correctly installed directly affects the correctness of the installation. Many problems encountered during the installation are related to the source.

The installation process involves three sources:

Install the 163 Source

1, backup/etc/yum. Repos. d/CentOS-Base.repo

1. MV/etc/yum. Repos. d/CentOS-Base.repo/etc/yum. Repos. d/CentOS-Base.repo.backup

2. Download the repo file of the corresponding version and put it in/etc/yum. Repos. d/(back up the file before the operation)

• Centos5

• Centos6

Install icehouse Source

Run the following command:

1. Yum install-y http://rdo.fedorapeople.org/openstack-icehouse/rdo-release-icehouse.rpm

Install epel Source

Select a 64-bit system and run the following command:

1. Rpm-IVH http://download.fedora.redhat.com/pub/epel/6/x86_64/epel-release-6-5.noarch.rpm

The foreman. Repo source is generated when the above source is installed. This source can be deleted directly.

 

Set Yum Cache

Due to network problems, the installation process may often fail, so you can set Yum cache to improve the efficiency of re-installation after failure.

Packstack

Install openstack-packstack

Run the following command:

yum install -y openstack-packstack  

Some programs may always fail to be installed on the computing node. you can install the program on the computing node and execute the program again on the control node.

 

Configure packstack

To facilitate the subsequent execution of the same packstack configuration multiple times, you can first export an original configuration and make some modifications to this file. Then you can specify a configuration file to install openstack.

Generate your own configuration file

packstack --gen-answer-file=myanswer.txt   

Modify configuration file

# To use heatconfig_heat_install = yconfig_ntp_servers = 0.uk.pool.ntp.org in the environment # configure two computing nodes: config_compute_hosts = 192.168.100.242, 192.168.100.244 # password used to log on to the console: config_keystone_admin_pw = admin # token = N # The configuration used by the network has been created. Token = token = em2config_lbaas_install = Signature = y # related to the GRE mode. configure config_neutron_ml2_type_drivers = greconfig_neutron_ml2_tenant_network_types = greconfig_neutron_ml2_tunnel_id_ranges = 100: environment = environment = 100:1000 # Use EM2 as the channel config_neutron_ovs_tunnel_if = EM2 # do not install demo user config_provision_demo = nconfig_heat_cloudwatch_install = yconfig_heat_cfn_install = y

Modify hosts

Add the IP address and name of the other node to the/etc/hosts file. To increase the download speed from the source, you can also configure the source information in the hosts file, for example, the hots file on 192.168.100.242 is as follows:

::1         localhost localhost.localdomainlocalhost6 localhost6.localdomain6127.0.0.1   develop5192.168.100.244   develop6::1         localhost localhost.localdomainlocalhost6 localhost6.localdomain6192.118.12.243          mirrors.skyshe.cn208.113.241.137         ceph.com152.19.134.191          repos.fedorapeople.org123.58.173.106          mirrors.163.com152.19.134.191          repos.fedorapeople.org69.56.251.103           openvswitch.org66.109.26.212           mirror.centos.org23.253.148.10           yum.theforeman.org 

Execute the configuration file

Packstack --answer-file=myanswer.txt

This process may be long and may be interrupted several times in the middle. Please continue after the interruption

Configure Br-ex

After the installation is complete, no Br-ex is created due to the current rdo problem. You only need to configure it on 192.168.100.242. For details, it should be performed on the network node.

Modify ifcfg-em1 files

DEVICE=em1HWADDR=C8:1F:66:E5:29:0DONBOOT=yesDEVICETYPE=ovsTYPE=OVSPortOVS_BRIDGE=br-ex

Create an ifcfg-Br-Ex File

DEVICE=br-exDEVICETYPE=ovsTYPE=OVSBridgeONBOOT=yesOVSBOOTPROTO=noneIPADDR=192.168.100.242NETMASK=255.255.255.0DEFROUTE=yesPREFIX=24GATEWAY=192.168.100.1DNS1=202.103.24.68

Configure ovs

ovs-vsctladd-br br-exovs-vsctladd-port br-ex em1; service network restart

 

After ovs is successfully configured and the virtual machine is added, the configuration is as follows:

Control + network + computing

Ovs Configuration

[[email protected]~(keystone_admin)]# ovs-vsctl showd3ac11c9-8d88-4abc-8ca0-19788ab1491b    Bridge br-ex        Port "em1"            Interface "em1"        Port "qg-158cc8c6-4f"            Interface"qg-158cc8c6-4f"                type: internal        Port br-ex            Interface br-ex                type: internal    Bridge br-int        fail_mode: secure        Port "tapa104132f-bd"            tag: 1            Interface"tapa104132f-bd"                type: internal        Port "qvo0715cfb5-b4"            tag: 1            Interface"qvo0715cfb5-b4"        Port "tape8875e25-22"            tag: 2            Interface"tape8875e25-22"                type: internal        Port br-int            Interface br-int                type: internal        Port "qvoeb74bfb0-1b"            tag: 1            Interface"qvoeb74bfb0-1b"        Port "qvod119e70f-3f"            tag: 1            Interface"qvod119e70f-3f"        Port patch-tun            Interface patch-tun                type: patch                options: {peer=patch-int}        Port "qvo948222df-c9"            tag: 1            Interface"qvo948222df-c9"        Port "qr-da6f872b-7c"            tag: 1            Interface"qr-da6f872b-7c"                type: internal    Bridge br-tun        Port "gre-0a010103"            Interface "gre-0a010103"                type: gre                options: {in_key=flow,local_ip="10.1.1.2", out_key=flow, remote_ip="10.1.1.3"}        Port patch-int            Interface patch-int                type: patch                options: {peer=patch-tun}        Port br-tun            Interface br-tun                type: internal    ovs_version: "1.11.0"

Linux bridge configuration

Computing node:

Ovs Configuration

[[email protected]~]# ovs-vsctl show17cbd24e-df55-4f3d-b6a4-446b88b47ac4    Bridge br-int        fail_mode: secure        Port "qvo28484b00-f0"            tag: 1            Interface"qvo28484b00-f0"        Port "qvo61070289-31"            tag: 1            Interface"qvo61070289-31"        Port "qvo3207417a-bd"            tag: 1            Interface"qvo3207417a-bd"        Port patch-tun            Interface patch-tun                type: patch                options: {peer=patch-int}        Port br-int            Interface br-int                type: internal    Bridge br-tun        Port patch-int            Interface patch-int                type: patch                options: {peer=patch-tun}        Port br-tun            Interface br-tun                type: internal        Port "gre-0a010102"            Interface "gre-0a010102"                type: gre                options: {in_key=flow,local_ip="10.1.1.3", out_key=flow, remote_ip="10.1.1.2"}    ovs_version: "1.11.0"

Linux bridge configuration

Installation Verification

1. You can open the logon page and log on with the configured password.
2. You can create networks and instances.
3. The configured instance can communicate with the external network.
   

 

Openstack deployment Summary: Install the Icehouse (ml2 + GRE) with rdo on centos 6.5)