Difference between revisions of "DNSaaS"
| Line 4: | Line 4: | ||
== Comparison of nova-dns and moniker == | == Comparison of nova-dns and moniker == | ||
[https://docs.google.com/document/d/1UFoAc7E17XivlV7h2PD4SCMeEhLecvPw0GAaoq_JKCk/edit Google Doc document] | [https://docs.google.com/document/d/1UFoAc7E17XivlV7h2PD4SCMeEhLecvPw0GAaoq_JKCk/edit Google Doc document] | ||
| + | |||
| + | == Discussion topics == | ||
| + | |||
| + | === 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) | ||
Revision as of 18:16, 24 October 2012
Dumping ground for content around OpenStack and DNS-as-a-Service
Comparison of nova-dns and moniker
Discussion topics
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)
