Openstack-ansible--3 Target hosts

Installing the operating system

Install the Ubuntu Server 14.04 (trusty Tahr) LTS 64-bit operating system

At least one network interface can access the extranet

Locale to en_US. UTF-8

Configuring the operating system

Deployment host to taget host no password login:

Copy Deployment hos Public key to Taget/root/.ssh/authorized_keysssh-copy-id-i ~/.ssh/id_rsa.pub [email protected]

kernel版本为3.13.0-34-genericor later

$ uname-alinux rpc-3 3.13.0-46-generic #79-ubuntu SMP Tue Mar 20:06:50 UTC x86_64 x86_64 x86_64 gnu/linux

# apt-get Install bridge-utils debootstrap ifenslave ifenslave-2.6   lsof lvm2 ntp ntpdate openssh-server sudo tcpdump v Lan

Add kernel module to/etc/modules to enable VLAN and interface bond

# echo ' bonding ' >>/etc/modules# echo ' 8021q ' >>/etc/modules

Configure NTP

Reboot the host to activate the changes

Configuring LVM

The openstack-ansible automatically configures the LVM, which is configured manually as follows:

2048 physical_volume_device_path# vgcreate Cinder-volumes Physical_volume_device_path

Designing the Network

The following table describes how the container network connects to the host bridge and the physical network interface:

The Target hosts contain the following network bridges:

• LXC Internal lxcbr0:
• Required, auto-generated, containers extranet connection, not connected to any physical/logical interface on host, connected by iptable, it connects to eth0 inside container.
  Configure the openstack_user_config.yml in theprovider_networks dictionary.
• Container Management BR-MGMT:
• necessary.
• Provides management of and communication among infrastructure and OpenStack services.
• Manually created, connected to the physical/logical interface (typically a VLAN subinterface on the bond0), connecting the eth1 of the container.
• Container network interface configured in OPENSTACK_USER_CONFIG.YML
• Storage Br-storage:
• Optional. But recommended
• Provides segregated access to block storage devices between Compute and block storage hosts.
• Manually created, connected to the physical/logical interface (typically a VLAN subinterface on the bond0), connecting the eth2 of the container.
• OpenStack Networking tunnel/overlay Br-vxlan:
• Mandatory.
• Provides infrastructure for VXLAN tunnel/overlay networks.
• Manually created, connected to the physical/logical interface (typically a VLAN subinterface on the bond1), connecting the eth10 of the container.
• OpenStack Networking provider Br-vlan:
• Mandatory.
• Provides infrastructure for VLAN and flat networks.
• Manually create a connection to the physical/logical interface (typically a VLAN subinterface on the bond1), connecting the eth11 of the container. Does not contain a IP address because it only handles Layer 2 connectivity.

The compute service is deployed directly on a physical machine rather than a container.

How to use the Bridges for network connectivity

Among them, compute nodes have Br-vxlan and Br-vlan to do Vxlan and VLAN respectively, Br-vxlan connected to a sub-node of the physical VLAN, Br-vlan do not need.

The following are the network nodes, the DHCP agent, the L3 agent, and the Linux Bridge agent are deployed in networking-agents container

Here's how VMS connect on COMPUTE nodes:

Reference Architecture Best on With

Bridge name	configured	a static IP
Br-mgmt	On every node	Always
Br-storage	On every storage node	When component are deployed on metal
	On every compute node	Always
Br-vxlan	On every network node	When component are deployed on metal
	On every compute node	Always
Br-vlan	On every network node	Never
	On every compute node	Never

Network configuration file for host management node:

Physical interfaces:

1 Auto eth0iface eth0 inet manual    bond-master bond0    Bond-2Auto Eth1iface eth1 inet Manual    bond-master bond1    Bond-3Auto Eth2iface eth2 inet Manual    Bond-4auto eth3iface eth3 inet manual    Bond -master Bond1

Bonding interfaces:

# Bond Interface0(Physical interfaces1and3) Auto Bond0iface bond0 inet static Bond-slaves eth0 eth2 bond-mode active-Backup Bond-miimon -Bond-downdelay $Bond-updelay $address host_ip_address netmask host_netmask Gateway Host_gateway DNS-nameservers host_dns_servers# Bond interface1(Physical interfaces2and4) Auto Bond1iface bond1 inet manual Bond-Slaves eth1 eth3 bond-mode active-Backup Bond-miimon -Bond-downdelay -Bond-updelay -

Logical (VLAN) interfaces:

# Container Management VLAN interfaceiface bond0. container_mgmt_vlan_id inet manual    VLAN-raw-device bond0# OpenStack Networking VXLAN (tunnel/  Overlay) VLAN Interfaceiface bond1. tunnel_vlan_id inet manual    vlan-raw-device bond1# Storage network VLAN interface (optional) iface bond0. storage_vlan_id inet manual    VLAN-raw-device bond0

Bridge Devices:

# Container Management bridgeauto BR-mgmtiface BR-Mgmt inet Static BRIDGE_STP off Bridge_waitport0BRIDGE_FD0# Bridge Port References tagged interface bridge_ports bond0. container_mgmt_vlan_id address container_mgmt_bridge_ip_address netmask container_mgmt_bridge_netmask DNS-nameservers container_mgmt_bridge_dns_servers# OpenStack Networking VXLAN (tunnel/overlay) Bridgeauto BR-vxlaniface BR-Vxlan inet static BRIDGE_STP off Bridge_waitport0BRIDGE_FD0# Bridge Port References tagged interface bridge_ports bond1. tunnel_vlan_id address tunnel_bridge_ip_address netmask tunnel_bridge_netmask# OpenStack Networking VLAN Bridgeauto BR-vlaniface BR-VLAN inet manual bridge_stp off Bridge_waitport0BRIDGE_FD0# Bridge Port References untagged interface bridge_ports bond1# Storage Bridge (optional) auto BR-storageiface BR-storage inet static BRIDGE_STP off Bridge_waitport0BRIDGE_FD0# Bridge Port Reference tagged interface bridge_ports bond0. storage_vlan_id address storage_bridge_ip_address netmask storage_bridge_netmask

Example for 3 controller nodes and 2 compute nodes

• VLANs:
  • Host management:untagged/native
  • Container management:10
  • Tunnels:30
  • Storage:20
• Networks:
  • Host MANAGEMENT:10.240.0.0/22
  • Container MANAGEMENT:172.29.236.0/22
  • Tunnel:172.29.240.0/22
  • Storage:172.29.244.0/22
• Addresses for the controller nodes:
  • Host management:10.240.0.11-10.240.0.13
  • Host Management gateway:10.240.0.1
  • DNS servers:69.20.0.164 69.20.0.196
  • Container management:172.29.236.11-172.29.236.13
  • Tunnel:no IP (because IP exist in the containers if the components aren ' t deployed directly on metal)
  • Storage:no IP (because IP exist in the containers if the components aren ' t deployed directly on metal)
• Addresses for the COMPUTE nodes:
  • Host management:10.240.0.21-10.240.0.22
  • Host Management gateway:10.240.0.1
  • DNS servers:69.20.0.164 69.20.0.196
  • Container management:172.29.236.21-172.29.236.22
  • tunnel:172.29.240.21-172.29.240.22
  • storage:172.29.244.21-172.29.244.22

Simple ARCHITECTURE:A single target host

Openstack-ansible--3 Target hosts