|
|
| (5 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| − | __NOTOC__
| + | |
| | DNSaaS is a working name for the next generation DNS support in openstack. | | DNSaaS is a working name for the next generation DNS support in openstack. |
| | | | |
| − | == Documents ==
| + | 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. |
| | | | |
| − | [https://docs.google.com/document/d/1UFoAc7E17XivlV7h2PD4SCMeEhLecvPw0GAaoq_JKCk/edit Comparison of nova-dns and moniker]
| + | = Moniker Links = |
| | | | |
| − | [[attachment:openstack-dns.pptx | Grizzly summit presentation]] | + | [[Moniker| Wiki]] |
| | | | |
| − | [https://etherpad.openstack.org/openstack-dns Grizzly design etherpad ]
| + | https://github.com/managedit/moniker |
| | | | |
| − | == Discussion topics ==
| + | https://launchpad.net/moniker |
| | | | |
| − | '''Scope'''
| + | = Initial Summit Documents = |
| − | * Internal use case : A and PTR records for Fixed IPs and Floating IPs.
| |
| − | * per instance CNAME ?
| |
| | | | |
| − | '''Notifications'''
| + | [https://docs.google.com/document/d/1UFoAc7E17XivlV7h2PD4SCMeEhLecvPw0GAaoq_JKCk/edit Comparison of nova-dns and moniker] |
| | | | |
| − | 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)
| + | [[attachment:openstack-dns.pptx | Grizzly summit presentation]] |
| − | Which notification (instance creation start / instance creation end) ?
| |
| | | | |
| − | '''Zones'''
| + | [https://etherpad.openstack.org/openstack-dns Grizzly design etherpad ] |
| − | | |
| − | 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'''
| |
| − | | |
| − | 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 ?
| |
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
