On Thu, Feb 28, 2019 at 06:48:03PM +0100, Daniel Alvarez Sanchez wrote: > Just wanted to throw an idea here about introducing availability zones > (AZ) concept in OVN and get implementation ideas. From a CMS > perspective, it makes sense to be able to implement some sort of > logical division of resources into failure domains to maximize their > availability. > > In this sense, establishing a full mesh of Geneve tunnels is not > needed (and possibly undesired when strict firewalls are used between > AZs) as L2 connectivity will be constrained to the AZ boundaries. > > A possibility would be to let the deployer of the CMS set a key on the > OpenvSwitch table of the local OVS instance like > 'external_ids:ovn_az=<int>' and if it's set, ovn-controller will > register itself as a Chassis with the same external ID and establish > tunnels to those Chassis within the same AZ, otherwise it'll keep the > current behavior. > > It'll be responsibility of the CMS to schedule gateway ports in the > right AZ as well to provide L3 AZ awareness. > > Does that make sense? Thoughts?
What's the effective difference between an OVN deployment with 3 zones, and a collection of 3 OVN deployments? Is it simply that the 3-zone deployment shares databases? Is that a significant advantage? _______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
