Jump to: navigation, search

Difference between revisions of "Designate/Talks"

Line 9: Line 9:
  
  
[[Designate/Atlanta/Presentation_2|Talk 2]] - Graham
+
[https://docs.google.com/document/d/1D6FcXMiWMvFTIggWiRu3VajVTnerCFDErTdafcSyxl0/edit?usp=sharing Talk 2] - Graham
 
* How does Designate integrate with OpenStack - How  does Designate Sink work (multiple tenants, floating and fixed IPs, etc.)
 
* 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)
 
* Why is designate a better solution than current DNS providers in an Openstack Ecosystem ( allow reverse DNS on cloud owned IPs, sink service etc)

Revision as of 17:42, 11 February 2014

Talks

Submit abstracts here.

Talk 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


Talk 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


Talk 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