Hi folks, 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? Thanks a lot!! Daniel _______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
