Jump to: navigation, search

Difference between revisions of "DNSaaS"

(Moniker Links)
 
(7 intermediate revisions by 3 users not shown)
Line 1: Line 1:
__NOTOC__
 
Dumping ground for content around [[OpenStack]] and DNS-as-a-Service
 
  
== Comparison of nova-dns and moniker ==
+
DNSaaS is a working name for the next generation DNS support in openstack.
[https://docs.google.com/document/d/1UFoAc7E17XivlV7h2PD4SCMeEhLecvPw0GAaoq_JKCk/edit  Google Doc document]
 
  
== Discussion topics ==
+
After the initial design summit, and the few first meetings, it has been decided to use the code base from Moniker for the DNS as a Service function of Openstack.
  
=== Scope ===
+
= Moniker Links =
* Internal use case : A and PTR records for Fixed IPs and Floating IPs.
 
* per instance CNAME ?
 
  
=== Notifications ===
+
[[Moniker| Wiki]]
Today the nova-dns implementation is querying the nova database to detect ip allocation. We should not rely of the nova database for this and should instead add notification in nova to notify of fixed_ips allocation (for example in the place where the current dns code resides)
 
  
=== Zones ===
+
https://github.com/managedit/moniker 
nova-dns is creating one zone per tenant, using the tenant id as the name. What zone for floating IP ?
 
Should users be able to specify zone parameters (SOA) ? Suggestion is to use templates and not allow tenant specification.
 
  
=== Records ===
+
https://launchpad.net/moniker
Today, A record is created for both the instance uuid and instance name or, in the case of nova-dns, just for instance name.
 
What is the right model ?
 
* A for uuid and instance name
 
* A for uuid, CNAME for instance name (can be changed later by user)
 
  
What about PTR ?
+
= Initial Summit Documents =
 +
 
 +
[https://docs.google.com/document/d/1UFoAc7E17XivlV7h2PD4SCMeEhLecvPw0GAaoq_JKCk/edit  Comparison of nova-dns and moniker]
 +
 
 +
[[attachment:openstack-dns.pptx | Grizzly summit presentation]]
 +
 
 +
[https://etherpad.openstack.org/openstack-dns  Grizzly design etherpad ]

Latest revision as of 15:22, 25 March 2015

DNSaaS is a working name for the next generation DNS support in openstack.

After the initial design summit, and the few first meetings, it has been decided to use the code base from Moniker for the DNS as a Service function of Openstack.

Moniker Links

Wiki

https://github.com/managedit/moniker

https://launchpad.net/moniker

Initial Summit Documents

Comparison of nova-dns and moniker

Grizzly summit presentation

Grizzly design etherpad