That's just it. The isolation type *is* provided when creating physical network. If I create a physical network with isolation type 'VXLAN', and then add traffic type of 'Public', it doesn't obey it. There's physical_networks and networks, when the zone is created, an entry goes in network that is Public/Vlan, hardcoded. The Public traffic type uses this, regardless of what the physical_network its being added to says. So if we updated the the public network table row with the correct isolation method for that physical network we are adding traffic type to when we add the public traffic type, that would work. It's worth noting that a zone can only have one physical network with traffic type of public.
On Wed, Jan 1, 2014 at 12:37 PM, Daan Hoogland <daan.hoogl...@gmail.com> wrote: >> While I've got your attention, what's the deal with isolation method vs >> broadcast method? These are always set to the same thing as far as I've seen. > > I've been asking this but haven't found the answer yet. There is an > overlap but both have some extra values the other hasn't. > > I don't like either of your solutions but haven't got a good > alternative. Best would be to be able to set the isolation type on > each physical network on creation. The wizard and zone creation api > command would have to be extended and allow for vlan as default. > > regards, > > On Wed, Jan 1, 2014 at 8:53 AM, Marcus Sorensen <shadow...@gmail.com> wrote: >> I suppose the answer might be to update the network with the proper >> isolation method when the traffic type is added. Look up the physical >> network's isolation method, grab network object for the public network, and >> set the right isolation. >> On Jan 1, 2014 12:46 AM, "Marcus Sorensen" <shadow...@gmail.com> wrote: >> >>> I ran into an issue today that I'm still trying to wrap my head >>> around, and I wanted to bounce this off of you guys. I have a physical >>> network whose isolation method is set to 'VXLAN' (v4.3+). I add my >>> Public traffic type to it. I'd assume that nics generated for public >>> traffic would have the standard vxlan:// URI for isolation URI and >>> broadcast URI, but they just have a vlan://. Digging into it, it seems >>> that public traffic is hard-coded to BroadcastDomainType.Vlan. I fixed >>> this fairly easily for my testing, there were only a few places to >>> fix, by pulling the BroadcastDomainType from the network object rather >>> than hardcoding it, but that found another problem. This only works if >>> I change the broadcast type in the 'networks' mysql table by hand, as >>> during zone deployment the public network creation is also hard-coded >>> to vlan. >>> >>> I'm not sure how to go about fixing this, since the Public, Control, >>> Management networks are created upon zone deployment, (see >>> createDefaultSystemNetworks). The immediate thing that jumped out was >>> a config variable for public isolation method, set prior to zone >>> deployment, or perhaps even one that overrides what's in the table. >>> >>> While I've got your attention, what's the deal with isolation method >>> vs broadcast method? These are always set to the same thing as far as >>> I've seen. >>>
