Difference between revisions of "Designate/Talks"
Tim Simmons (talk | contribs) (→Talks) |
(Added proposed abstract for workshop) |
||
| Line 25: | Line 25: | ||
* How easy it is to get involved, get started | * How easy it is to get involved, get started | ||
* How to migrate your current DNS solution to Designate | * How to migrate your current DNS solution to Designate | ||
| + | |||
| + | ===Proposed Abstract for the workshop === | ||
| + | Designate provides DNSaaS services for OpenStack: | ||
| + | |||
| + | REST API for domain & record management | ||
| + | * Multi-tenant | ||
| + | * Integrated with Keystone for authentication | ||
| + | * Framework in place to integrate with Nova and Neutron notifications (for auto-generated records) | ||
| + | * Support for PowerDNS and Bind9 out of the box | ||
| + | The workshop shows how Designate can be installed with PowerDNS as the backend. For the purposes of the workshop the various designate components would be installed on a single node. Once installed it shows some of the v1 and v2 apis for domain and record management. The workshop would conclude by using a tool like dig to retrieve the added records from the PowerDNS backend. | ||
| + | |||
| + | The workshop would also talk about the steps for contributing to the development of Designate. | ||
| + | |||
| + | ===Additional Notes on the workshop === | ||
| + | I chose PowerDNS as the backend rather than BIND as it is more well tested as of now. I put in a single node – so that it is easier to control and easier for newbies to install. Also we talked about the workshop showing migration to Designate. However I think it is early at this point for us to talk about migration as we have not yet done a migrate with Designate. | ||
Revision as of 16:40, 5 February 2014
Contents
Talks
Submit abstracts here.
1 - Tim - WIP Outline/Abstract
- Talk about what's new since the last talk (v2 API, Mini-DNS, Server Pools etc)
- Advertize any new advanced features that are completed by the summit
- How easy it is to get involved, get started
- API design
2 - Graham
- How does Designate integrate with OpenStack - How does Designate Sink work (multiple tenants, floating and fixed IPs, etc.)
- Why is designate a better solution than current DNS providers in an Openstack Ecosystem ( allow reverse DNS on cloud owned IPs, sink service etc)
- Lets itemize what backends are supported and how easy it would be to integrate other new backends that are spec-compliant
3 - Kiall
- Whats up with Global Load Balancing?
- The mini-DNS solution - why/if we did it (challenge of integrating with multiple vendors)
- NSUpdate and supporting multiple pre-existing clients
Workshop
Workshop - Joe
- Designate Deploy/Use Workshop Install fest!
- How easy it is to get involved, get started
- How to migrate your current DNS solution to Designate
Proposed Abstract for the workshop
Designate provides DNSaaS services for OpenStack:
REST API for domain & record management
- Multi-tenant
- Integrated with Keystone for authentication
- Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)
- Support for PowerDNS and Bind9 out of the box
The workshop shows how Designate can be installed with PowerDNS as the backend. For the purposes of the workshop the various designate components would be installed on a single node. Once installed it shows some of the v1 and v2 apis for domain and record management. The workshop would conclude by using a tool like dig to retrieve the added records from the PowerDNS backend.
The workshop would also talk about the steps for contributing to the development of Designate.
Additional Notes on the workshop
I chose PowerDNS as the backend rather than BIND as it is more well tested as of now. I put in a single node – so that it is easier to control and easier for newbies to install. Also we talked about the workshop showing migration to Designate. However I think it is early at this point for us to talk about migration as we have not yet done a migrate with Designate.
