OpenStack Networking (neutron)The example architecture with OpenStack Networking (neutron) requires
one controller node, one network node, and at least one compute node.
The controller node contains one network interface on the
management network. The network node contains
one network interface on the management network, one on the
instance tunnels network, and one on the
external network. The compute node contains
one network interface on the management network and one on the
instance tunnels network.Network interface names vary by distribution. Traditionally,
interfaces use "eth" followed by a sequential number. To cover all
variations, this guide simply refers to the first interface as the
interface with the lowest number, the second interface as the
interface with the middle number, and the third interface as the
interface with the highest number.Unless you intend to use the exact configuration provided in this
example architecture, you must modify the networks in this procedure to
match your environment. Also, each node must resolve the other nodes
by name in addition to IP address. For example, the
controller name must resolve to
10.0.0.11, the IP address of the management
interface on the controller node.Reconfiguring network interfaces will interrupt network
connectivity. We recommend using a local terminal session for these
procedures.Controller nodeTo configure networking:Configure the first interface as the management interface:IP address: 10.0.0.11Network mask: 255.255.255.0 (or /24)Default gateway: 10.0.0.1To configure name resolution:Set the hostname of the node to
controller.Edit the /etc/hosts file to contain the
following:# controller
10.0.0.11 controller
# network
10.0.0.21 network
# compute1
10.0.0.31 compute1You must remove or comment the line beginning with
127.0.1.1.Network nodeTo configure networking:Configure the first interface as the management interface:IP address: 10.0.0.21Network mask: 255.255.255.0 (or /24)Default gateway: 10.0.0.1Configure the second interface as the instance tunnels
interface:IP address: 10.0.1.21Network mask: 255.255.255.0 (or /24)The external interface uses a special configuration without an
IP address assigned to it. Configure the third interface as the
external interface:Replace INTERFACE_NAME with the
actual interface name. For example, eth2 or
ens256.Edit the /etc/network/interfaces file
to contain the following:# The external network interface
auto INTERFACE_NAME
iface INTERFACE_NAME inet manual
up ip link set dev $IFACE up
down ip link set dev $IFACE downEdit the
/etc/sysconfig/network-scripts/ifcfg-INTERFACE_NAME
file to contain the following:Do not change the HWADDR and
UUID keys.DEVICE=INTERFACE_NAME
TYPE=Ethernet
ONBOOT="yes"
BOOTPROTO="none"Edit the
/etc/sysconfig/network/ifcfg-INTERFACE_NAME file to
contain the following:STARTMODE='auto'
BOOTPROTO='static'Restart networking:#service networking stop && service networking start#service network restartTo configure name resolution:Set the hostname of the node to network.Edit the /etc/hosts file to contain the
following:# network
10.0.0.21 network
# controller
10.0.0.11 controller
# compute1
10.0.0.31 compute1You must remove or comment the line beginning with
127.0.1.1.Compute nodeTo configure networking:Configure the first interface as the management interface:IP address: 10.0.0.31Network mask: 255.255.255.0 (or /24)Default gateway: 10.0.0.1Additional compute nodes should use 10.0.0.32, 10.0.0.33,
and so on.Configure the second interface as the instance tunnels
interface:IP address: 10.0.1.31Network mask: 255.255.255.0 (or /24)Additional compute nodes should use 10.0.1.32, 10.0.1.33,
and so on.To configure name resolution:Set the hostname of the node to compute1.Edit the /etc/hosts file to contain the
following:# compute1
10.0.0.31 compute1
# controller
10.0.0.11 controller
# network
10.0.0.21 networkYou must remove or comment the line beginning with
127.0.1.1.Verify connectivityWe recommend that you verify network connectivity to the internet
and among the nodes before proceeding further.From the controller node,
ping a site on the internet:#ping -c 4 openstack.orgPING openstack.org (174.143.194.225) 56(84) bytes of data.
64 bytes from 174.143.194.225: icmp_seq=1 ttl=54 time=18.3 ms
64 bytes from 174.143.194.225: icmp_seq=2 ttl=54 time=17.5 ms
64 bytes from 174.143.194.225: icmp_seq=3 ttl=54 time=17.5 ms
64 bytes from 174.143.194.225: icmp_seq=4 ttl=54 time=17.4 ms
--- openstack.org ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3022ms
rtt min/avg/max/mdev = 17.489/17.715/18.346/0.364 msFrom the controller node,
ping the management interface on the
network node:#ping -c 4 networkPING network (10.0.0.21) 56(84) bytes of data.
64 bytes from network (10.0.0.21): icmp_seq=1 ttl=64 time=0.263 ms
64 bytes from network (10.0.0.21): icmp_seq=2 ttl=64 time=0.202 ms
64 bytes from network (10.0.0.21): icmp_seq=3 ttl=64 time=0.203 ms
64 bytes from network (10.0.0.21): icmp_seq=4 ttl=64 time=0.202 ms
--- network ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 0.202/0.217/0.263/0.030 msFrom the controller node,
ping the management interface on the
compute node:#ping -c 4 compute1PING compute1 (10.0.0.31) 56(84) bytes of data.
64 bytes from compute1 (10.0.0.31): icmp_seq=1 ttl=64 time=0.263 ms
64 bytes from compute1 (10.0.0.31): icmp_seq=2 ttl=64 time=0.202 ms
64 bytes from compute1 (10.0.0.31): icmp_seq=3 ttl=64 time=0.203 ms
64 bytes from compute1 (10.0.0.31): icmp_seq=4 ttl=64 time=0.202 ms
--- network ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 0.202/0.217/0.263/0.030 msFrom the network node,
ping a site on the internet:#ping -c 4 openstack.orgPING openstack.org (174.143.194.225) 56(84) bytes of data.
64 bytes from 174.143.194.225: icmp_seq=1 ttl=54 time=18.3 ms
64 bytes from 174.143.194.225: icmp_seq=2 ttl=54 time=17.5 ms
64 bytes from 174.143.194.225: icmp_seq=3 ttl=54 time=17.5 ms
64 bytes from 174.143.194.225: icmp_seq=4 ttl=54 time=17.4 ms
--- openstack.org ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3022ms
rtt min/avg/max/mdev = 17.489/17.715/18.346/0.364 msFrom the network node,
ping the management interface on the
controller node:#ping -c 4 controllerPING controller (10.0.0.11) 56(84) bytes of data.
64 bytes from controller (10.0.0.11): icmp_seq=1 ttl=64 time=0.263 ms
64 bytes from controller (10.0.0.11): icmp_seq=2 ttl=64 time=0.202 ms
64 bytes from controller (10.0.0.11): icmp_seq=3 ttl=64 time=0.203 ms
64 bytes from controller (10.0.0.11): icmp_seq=4 ttl=64 time=0.202 ms
--- controller ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 0.202/0.217/0.263/0.030 msFrom the network node,
ping the instance tunnels interface on the
compute node:#ping -c 4 10.0.1.31PING 10.0.1.31 (10.0.1.31) 56(84) bytes of data.
64 bytes from 10.0.1.31 (10.0.1.31): icmp_seq=1 ttl=64 time=0.263 ms
64 bytes from 10.0.1.31 (10.0.1.31): icmp_seq=2 ttl=64 time=0.202 ms
64 bytes from 10.0.1.31 (10.0.1.31): icmp_seq=3 ttl=64 time=0.203 ms
64 bytes from 10.0.1.31 (10.0.1.31): icmp_seq=4 ttl=64 time=0.202 ms
--- 10.0.1.31 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 0.202/0.217/0.263/0.030 msFrom the compute node,
ping a site on the internet:#ping -c 4 openstack.orgPING openstack.org (174.143.194.225) 56(84) bytes of data.
64 bytes from 174.143.194.225: icmp_seq=1 ttl=54 time=18.3 ms
64 bytes from 174.143.194.225: icmp_seq=2 ttl=54 time=17.5 ms
64 bytes from 174.143.194.225: icmp_seq=3 ttl=54 time=17.5 ms
64 bytes from 174.143.194.225: icmp_seq=4 ttl=54 time=17.4 ms
--- openstack.org ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3022ms
rtt min/avg/max/mdev = 17.489/17.715/18.346/0.364 msFrom the compute node,
ping the management interface on the
controller node:#ping -c 4 controllerPING controller (10.0.0.11) 56(84) bytes of data.
64 bytes from controller (10.0.0.11): icmp_seq=1 ttl=64 time=0.263 ms
64 bytes from controller (10.0.0.11): icmp_seq=2 ttl=64 time=0.202 ms
64 bytes from controller (10.0.0.11): icmp_seq=3 ttl=64 time=0.203 ms
64 bytes from controller (10.0.0.11): icmp_seq=4 ttl=64 time=0.202 ms
--- controller ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 0.202/0.217/0.263/0.030 msFrom the compute node,
ping the instance tunnels interface on the
network node:#ping -c 4 10.0.1.21PING 10.0.1.21 (10.0.1.21) 56(84) bytes of data.
64 bytes from 10.0.1.21 (10.0.1.21): icmp_seq=1 ttl=64 time=0.263 ms
64 bytes from 10.0.1.21 (10.0.1.21): icmp_seq=2 ttl=64 time=0.202 ms
64 bytes from 10.0.1.21 (10.0.1.21): icmp_seq=3 ttl=64 time=0.203 ms
64 bytes from 10.0.1.21 (10.0.1.21): icmp_seq=4 ttl=64 time=0.202 ms
--- 10.0.1.21 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 0.202/0.217/0.263/0.030 ms