Re: [openstack-dev] [Neutron]Relationship between physical networks and segment

Bob, Thanks for your detailed response. In it you "strongly recommend that any functionality trying to make decisions based on connectivity do so by calling into the registered mechanism drivers, so they can decide whether whatever they manage has connectivity". After eading this I went through

Re: [openstack-dev] [Neutron]Relationship between physical networks and segment

On 29/03/16 20:42, Miguel Lavalle wrote: > Hi, Hi Miguel, > I am writing a patchset to build a mapping between hosts and network > segments. The goal of this mapping is to be able to say whether a host > has access to a given network segment. I am building this mapping > assuming that if a host

Re: [openstack-dev] [Neutron]Relationship between physical networks and segment

My answers below are from the perspective of normal (non-routed) networks implemented in ML2. The support for routed networks should build on this without breaking it. On 3/29/16 3:38 PM, Miguel Lavalle wrote: Hi, I am writing a patchset to build a mapping between hosts and network

Re: [openstack-dev] [Neutron]Relationship between physical networks and segment

On Tue, Mar 29, 2016 at 1:38 PM, Miguel Lavalle wrote: > I am writing a patchset to build a mapping between hosts and network > segments. The goal of this mapping is to be able to say whether a host has > access to a given network segment. I am building this mapping assuming

[openstack-dev] [Neutron]Relationship between physical networks and segment

Hi, I am writing a patchset to build a mapping between hosts and network segments. The goal of this mapping is to be able to say whether a host has access to a given network segment. I am building this mapping assuming that if a host A has a bridges mapping containing 'physnet 1' and a segment