Difference between revisions of "DNSaaS"
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
| − | |||
| − | == | + | DNSaaS is a working name for the next generation DNS support in openstack. |
| − | [https://docs.google.com/document/d/1UFoAc7E17XivlV7h2PD4SCMeEhLecvPw0GAaoq_JKCk/edit | + | |
| + | == 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 ] | ||
== Discussion topics == | == Discussion topics == | ||
| − | + | ""Scope"" | |
* Internal use case : A and PTR records for Fixed IPs and Floating IPs. | * Internal use case : A and PTR records for Fixed IPs and Floating IPs. | ||
* per instance CNAME ? | * per instance CNAME ? | ||
| − | + | ""Notifications"" | |
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) | 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"" | |
nova-dns is creating one zone per tenant, using the tenant id as the name. What zone for floating IP ? | 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. | 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. | 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 ? | What is the right model ? | ||
* A for uuid and instance name | * A for uuid and instance name | ||
* A for uuid, CNAME for instance name (can be changed later by user) | * A for uuid, CNAME for instance name (can be changed later by user) | ||
| − | |||
What about PTR ? | What about PTR ? | ||
Revision as of 23:40, 29 October 2012
DNSaaS is a working name for the next generation DNS support in openstack.
Documents
Comparison of nova-dns and moniker Grizzly summit presentation Grizzly design etherpad
Discussion topics
""Scope""
- Internal use case : A and PTR records for Fixed IPs and Floating IPs.
- per instance CNAME ?
""Notifications"" 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"" 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 ?
