DevStack Homelab Network Configuration

asked 2019-09-28 02:45:14 -0500

qubitrenegade gravatar image

updated 2019-09-28 14:24:54 -0500


I have a single host that I'd like to run DevStack on.

OS: 18.04.3 LTS (Bionic Beaver)
Kernel: Linux OpenStack 5.0.0-29-generic #31~18.04.1-Ubuntu SMP Thu Sep 12 18:29:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
CPU: AMD Ryzen 7 1800X Eight-Core Processor
Disk:  /dev/mapper/ubuntu--vg-ubuntu--lv  916G   19G  860G   3% /
NIC: enp35s0, Intel Corporation I211 Gigabit Network Connection (rev 03) (I followed this doc). The installer runs, and I'm able to spin up VMs! This seems to create two networks "Public" and "Shared" (I do not seem to be able to assign a floating IP when a VM is attached to the shared network, that seems intentional?).

However, these are not reachable from outside of the host machine.

I set the following in my local.conf before running


After creating DevStack, I created a few networks, subnets, and routers. Then for troubleshooting purposes I created an "allow all" to allow all TCP, UDP, and ICMP traffic. (Terraform that I used to do so can be found here). (I created a gist) of the out put from network, router, and port opentstack commands.

I'm doing this on my home network I created a (rough drawing) to illustrate what I have going on.

Home Subnet:
DHCP Range:
DHCP/DNS Server:

Host1: DevStack

VM1: Guest on DevStack
Network: prod01-network
Floating IP:

VM2: Guest on another host, all results are replicable from laptop and workstation (which is the host of VM2)

I am able to ping/ssh to the VM1 guest from Host1. I cannot ping/ssh from VM2 (external to DevStack) to VM1 (DevStack guest). I _can_ ping/ssh from VM1 (DevStack Guest) to VM2 (external to DevStack)

I performed the following connectivity tests:

Host1 -> VM1 Floating IP -, yes
Host1 -> Floating IP G/W -, yes
Host1 -> VM1 IP -, negative
Host1 -> VM1 Gateway -, negative

VM2 -> ping VM1 Floating IP -, negative
VM2 -> ssh VM1 FLoating IP -, negative
VM2 -> ping Floating IP G/W -, yes
VM2 -> VM1 IP -, negative
VM2 -> VM1 Gateway -, negative
VM2 -> curl -L, yes
VM2 -> Host1 -, yes

VM1 -> ping VM2 -, yes
VM1 -> ssh VM2, yes
VM1 -> ping -> yes
VM1 -> ping, negative "name ...
edit retag flag offensive close merge delete


Hmm... These docs: (

Have different attributes:


Though, I'm not sure that would really have any affect...

But, the FLOATING_RANGEdifferent subnet than host

qubitrenegade gravatar imagequbitrenegade ( 2019-09-28 12:39:26 -0500 )edit

1 answer

Sort by ยป oldest newest most voted

answered 2019-09-29 16:06:47 -0500

qubitrenegade gravatar image

Ok, the solution was to add a static route in the router to point to the floating subnet.

What I ended up doing was setting FLOATING_RANGE= then adding a static route in the modem pointing at as the G/W.

This is a screenshot of my ZyXEL C2100Z router configuration page:

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2019-09-28 02:45:14 -0500

Seen: 135 times

Last updated: Sep 29 '19