Traffic from vm to vm on different hosts should be able to go accross
flat_interface
Okay, that makes sense.
Getting inbound connectivity over fixed_ips can be tricky. It looks
like you want to set up a specific range from vms that is not
snatted. there is a config option for this called
On Aug 2, 2012, at 7:35 AM, Lars Kellogg-Stedman l...@seas.harvard.edu wrote:
With a multi_host, flatDHCP model, is the general idea that fixed_ips
are -- generally -- internal to the compute host, and all external
access is supposed to be via floating ips? That's sort of how it
looks,
On Thu, Aug 02, 2012 at 09:24:56AM -0700, Vishvananda Ishaya wrote:
It isn't explicitly that way, but it is the easiest setup. It is
possible to set up fixed ips that are accessible/routable from
outside but there are a lot of gotchas
Got it.
The snatting rule is created exclusively from
We are trying to use the FlatDHCP network model in multi_host mode.
Getting things to boot and establishing *outbound* connectivity has
been relatively simple. Systems come up, pull an address from the
local dnsmasq process running on the compute host, and all traffic is
routed out
On Aug 1, 2012, at 9:35 AM, Lars Kellogg-Stedman l...@seas.harvard.edu wrote:
For outbound access, it's not clear why the flat_network_bridge needs
to be connected to an actual physical interface...since everything
goes out public_interface, I'm not sure what flat_interface is for.
Traffic
5 matches
Mail list logo
