Hi Kiall, Thanks for getting back. Yes, I understand that Designate is providing the API interface to push data into a DNS namespace, so not really related to the region concept in the same way as nova or most other OpenStack services. I think the problem I am highlighting here is that of making updates for zone data to an authoritative DNS server from distributed sources. Take the example of a company which has deployed their resources across multiple OpenStack regions. Now they just want to have a flat DNS namespace (say example.com). They will need to enter host - IP mapping data to some authoritative back end DNS server for this purpose. The records for this zone are being created from multiple regions either through static data entry through designate or via notification handlers from OpenStack events like FIP creation. So my question is can we view designate simply as an data entry vehicle with an API front end where a single (centralized) backend DNS server can be fed data from multiple designate instances ? That way different designate instances in different regions can generate their local RRs for a zone (example.com) and point to the same backend DNS for populating the zone file. Once data goes into the centralized backend DNS, it will be the responsibility of the DNS infrastructure to serve the DNS data in a distributed scale out manner globally for lookups. The problem that will still need to be solved is how do you create major DNS entries, like creating a new zone, with this approach ? I will try to describe a solution for that in a follow up email but wanted to get your opinion first on what I am describing here so far. Regards, Anik
---------------------------------------------------------------------- Message: 1 Date: Tue, 07 Apr 2015 13:00:33 +0100 From: Kiall Mac Innes <ki...@macinnes.ie> To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] Multi Region Designate Message-ID: <5523c6e1.9090...@macinnes.ie> Content-Type: text/plain; charset=windows-1252 Hey Anik, So, unlike Nova or other services which really are "region" aware, Designate, being designed to push data into the global DNS namespace, doesn't have the same concept of regions. Typically, you will either have regions which are "close enough" to run a Galera/Percona cluster across them without adding too much latency, or you will run asynchronous replication from one region to another using an Active/Standby failover for the core DB. The DNS team @ HP has discussed possible improvements to this many times over the last year or so, but haven't come up with any great solutions to providing what amounts to a global service is a per-region way. We're certainly open to suggestions! :) Thanks, Kiall On 23/03/15 04:41, Anik wrote: > Hi, > > Are there any plans to have multi region DNS service through designate ? > > For example If a tenant has projects in multiple regions and wants to > use a single (flat) external domain name space for floating IPs, what is > the proposed solution for such a use case using Designate ? > > Regards, > Anik > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
