[designate] Architecture help for designate on multi-region/multi-AZ deployments
openstack at a.spamming.party
Wed Mar 9 08:24:18 UTC 2022
I currently have designate installed in a single region in a cloud.
Now we are thinking about the next steps: A multi-region designate for a simple use case: Bring your own domain, have A/AAAA records for your instances regardless of the region.
Side note: That requirement can be modified if what I am asking is impossible.
I didn't find anything in the ML, nor in the bug tracker  outside a neutron bug  (am I blind?).
I had a look at the designate documentation, but there are no best practices for multi-region (or am I blind again?)
The only relevant part for integration with neutron is in , which is not region related.
I am looking for advice from designate experts here, to see what we can do.
Right now, we are thinking about two ways to deal with this:
A) Install a separate openstack with designate, and make all the regions's neutrons configuration point to a single designate. Neutron would work, designate would be simple to manage (as we have a single designate).
The downside here is the clear-cut separation of regions: I am afraid of how records are stored in the central designate, and if there won't be multi-tenancy issues (uuid could technically overlap, as different regions means different keystones here).
B) Install a designate in each region, with DNS servers in each region. We have strict region separation this way.
The downside is the user friendliness: A customer _can_ decide which region in which the domain will be hosted. That means that we now need to worry about synchronizing region's state (if you have created a domain in that region, you can't do it elsewhere).
Am I misunderstanding/not seeing something obvious here?
Thank you in advance.
Jean-Philippe Evrard (evrardjp)
More information about the openstack-discuss