Bays spawned from devstack dont have external network access
Bug #1446372 reported by
Andrew Melton
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Magnum |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
When using a devstack build with out plugin, instances spawned for bays don't have external network access. And thus, our example that use public containers won't work. To get external network access, IP masquerading needs to be set up on the external bridge. This can be done manually after setting up devstack by running: "sudo /sbin/iptables -t nat -A POSTROUTING -o br-ex -j MASQUERADE" But, we may want to consider running this command by default in our devstack plugin.
description: | updated |
Changed in magnum: | |
milestone: | none → mitaka-1 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I agree it should be added by default. I expect that most users of the devstack plugin actually intend to use public images, at least to start with, so we should set the environment up to allow that.