Neutron Network Config for Controller and Compute Nodes on Different Networks

asked 2018-05-31 09:18:05 -0600

Code Manure gravatar image

I'm fairly new to Openstack and have very limited insight into Advanced networking concepts. I'm trying to setup a simple Openstack Mitaka setup for work, following the official installation guides. I thought I was making pretty good progress till I reached the networking bit.

I have the following configuration:

  1. Single controller node on a VMWare virtual machine on 10.110.166.XXX subnet - 2 NICs present
  2. Single compute node on Bare Metal server on 10.110.167.XXX subnet - 2 NICs present

I've deployed Keystone, Nova, Glance and Neutron components on the controller. Nova-compute service and linuxbridge-agent on the compute node. Trying to get the network setup working with the ML2 plugin which was recommended in the installation guide.

After following all the instructions listed, I can't seem to ping any of the VM instances that are launched from my neither my compute nor my controller node. This could also be the reason I'm not able to get a VNC console connection to the instances. I can clearly see that my networking setup is wrong since my Ubuntu instance gets stuck at boot waiting for the network interfaces to come up.

I have recreated the network setup within Openstack multiple times but haven't been successful, Right now, I've cleared everything out and have no provider or any other networks defined within Neutron. I'd really appreciate it if somebody could guide me through this process.

I have doubts about whether it is possible to have controller and compute nodes on different LAN segments. Haven't been able to find solutions for this.

The setup seems to be good so far judging by this output:

neutron agent-list
| id                                   | agent_type         | host       | availability_zone | alive | admin_state_up | binary                    |
| 11ff8610-8eb2-45d5-91e8-d7905beb668c | Linux bridge agent | controller |                   | :-)   | True           | neutron-linuxbridge-agent |
| 370794ac-0091-4908-8293-00d007f7f8be | Linux bridge agent | compute1   |                   | :-)   | True           | neutron-linuxbridge-agent |
| 444eca8d-3a34-4018-97ab-f23925e65713 | DHCP agent         | controller | nova              | :-)   | True           | neutron-dhcp-agent        |
| 90f70ca7-afd2-4127-97f1-f623fac26e29 | Metadata agent     | controller |                   | :-)   | True           | neutron-metadata-agent    |
| ad2a6012-a348-47c7-8ee9-f41401fb048f | L3 agent           | controller | nova              | :-)   | True           | neutron-l3-agent          |

I've added configs below that might help with this problem.

Controller Node:


# The loopback network interface
auto lo
iface lo inet loopback

# The provider network interface
auto ens192
iface ens192 inet manual
up ip link set dev $IFACE up
down ip link set dev $IFACE down

# primary network interface
auto ens160
iface ens160 inet dhcp

Output of ifconfig:

ens160    Link encap:Ethernet  HWaddr 00:50:56:99:c5:74
          inet addr:  Bcast:  Mask:
          inet6 addr: fe80::250:56ff:fe99:c574/64 Scope:Link
          RX packets:995476 errors:0 dropped:0 overruns:0 frame:0
          TX packets:639007 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:578268831 (578.2 MB)  TX bytes:522577815 (522.5 MB)

ens192    Link encap:Ethernet  HWaddr 00:50:56:99:14:d4
          inet6 addr: fe80::250:56ff:fe99:14d4/64 Scope:Link
          RX packets ...
edit retag flag offensive close merge delete