Difference between revisions of "Designate/Old Incubation Application"
m (Kiall moved page Moniker Incubation Application to Designate Incubation Application) |
|||
Line 1: | Line 1: | ||
== Project codename == | == Project codename == | ||
− | + | Designate | |
== Summary == | == Summary == | ||
− | + | Designate DNSaaS Project | |
== Detailed Description == | == Detailed Description == | ||
− | + | Designate is a DNS as-a-service project. It is intended to be used to provide DNS service from the entry point of creating, updating, maintaining and deleting DNS data using the Designate API, to providing DNS resolution for users. It is a very modular project, allowing for the use of whatever DNS server and organization demands, or the database where DNS data is stored. It is also intended to work in conjunction with other components such as Nova. | |
− | The purpose of the project is provide managed DNS for the Openstack Ecosystem using a REST API or | + | The purpose of the project is provide managed DNS for the Openstack Ecosystem using a REST API or Designate Sink which consumes events from Nova or Quantum, or any other service that has events that would necessitate DNS changes. It also will replace Nova DNS bindings and provide much more robust and full-featured DNS functionality. Also, advanced DNS record support will be added such as DNSSEC. |
− | + | Designate is relevant to the mission by adding a missing piece of data-center functionality, namely, one of the most ubiquitous services, DNS. It's relevant to other OpenStack projects by automating the name resolution changes required for the creation and deletion of Nova instances or other components. | |
== Basic roadmap for the project == | == Basic roadmap for the project == | ||
Line 30: | Line 30: | ||
* DNSSEC | * DNSSEC | ||
− | * Development of functionality to utilize | + | * Development of functionality to utilize designate-sink to process events from Nova and Quantum |
* Import/Export of Domains via BIND9 style zone files | * Import/Export of Domains via BIND9 style zone files | ||
* Private/Internal DNS servers | * Private/Internal DNS servers | ||
Line 36: | Line 36: | ||
== Location of project source code == | == Location of project source code == | ||
− | * [https://launchpad.net/moniker | + | * [https://launchpad.net/moniker Designate on Launchpad] |
− | * [https://github.com/stackforge/moniker/ | + | * [https://github.com/stackforge/moniker/ Designate at StackForge] |
− | * [https://github.com/stackforge/python-monikerclient/ python- | + | * [https://github.com/stackforge/python-monikerclient/ python-designateclient at StackForge] |
== Programming language, required technology dependencies == | == Programming language, required technology dependencies == | ||
Line 53: | Line 53: | ||
* Software: Private Beta at HPCS. Implementations at other organizations. | * Software: Private Beta at HPCS. Implementations at other organizations. | ||
− | * Team: Working together for six months | + | * Team: Working together for six months. |
== Proposed project technical lead and qualifications == | == Proposed project technical lead and qualifications == | ||
− | ;Kiall Mac Innes (kiall): Kiall has worked on OpenStack for ~2 years. He has an extensive understanding of DNS and is the lead author of | + | ;Kiall Mac Innes (kiall): Kiall has worked on OpenStack for ~2 years. He has an extensive understanding of DNS and is the lead author of Designate. |
== Other project developers and qualifications == | == Other project developers and qualifications == | ||
Line 67: | Line 67: | ||
;Endre Karlson (zykes-): DNS, Linux, Orchestration, Database, Python, Ruby, Billingstack | ;Endre Karlson (zykes-): DNS, Linux, Orchestration, Database, Python, Ruby, Billingstack | ||
− | ;Ryan Lane (Ryan_Lane): Experience with operating other OpenStack projects, maintainer of legacy nova dns code and maintainer of DNS code for Wikimedia Labs. Will use | + | ;Ryan Lane (Ryan_Lane): Experience with operating other OpenStack projects, maintainer of legacy nova dns code and maintainer of DNS code for Wikimedia Labs. Will use Designate in production soon and will be writing a gdnsd driver. |
== Infrastructure requirements (testing, etc) == | == Infrastructure requirements (testing, etc) == | ||
Line 80: | Line 80: | ||
* [http://moniker.readthedocs.org/ Documentation] | * [http://moniker.readthedocs.org/ Documentation] | ||
− | * [https://wiki.openstack.org/wiki/ | + | * [https://wiki.openstack.org/wiki/Designate Designate on OpenStack Wiki] |
− | * [http://openstacksummitapril2013.sched.org/event/c45a03b565d5302b50e3edc1f43756ea#.UXB8nYdxdok | + | * [http://openstacksummitapril2013.sched.org/event/c45a03b565d5302b50e3edc1f43756ea#.UXB8nYdxdok Designate Talk at the Portland Summit] |
* [https://docs.google.com/document/d/1UFoAc7E17XivlV7h2PD4SCMeEhLecvPw0GAaoq_JKCk/edit Openstack DNS solutions comparison pre-San Diego Summit] | * [https://docs.google.com/document/d/1UFoAc7E17XivlV7h2PD4SCMeEhLecvPw0GAaoq_JKCk/edit Openstack DNS solutions comparison pre-San Diego Summit] | ||
* [https://etherpad.openstack.org/openstack-dns San Diego Summit Etherpad] | * [https://etherpad.openstack.org/openstack-dns San Diego Summit Etherpad] |
Revision as of 20:46, 9 June 2013
Contents
- 1 Project codename
- 2 Summary
- 3 Detailed Description
- 4 Basic roadmap for the project
- 5 Location of project source code
- 6 Programming language, required technology dependencies
- 7 Is project currently open sourced? What license?
- 8 Level of maturity of software and team
- 9 Proposed project technical lead and qualifications
- 10 Other project developers and qualifications
- 11 Infrastructure requirements (testing, etc)
- 12 Have all current contributors agreed to the OpenStack CLA?
- 13 Related Links
- 14 Status
Project codename
Designate
Summary
Designate DNSaaS Project
Detailed Description
Designate is a DNS as-a-service project. It is intended to be used to provide DNS service from the entry point of creating, updating, maintaining and deleting DNS data using the Designate API, to providing DNS resolution for users. It is a very modular project, allowing for the use of whatever DNS server and organization demands, or the database where DNS data is stored. It is also intended to work in conjunction with other components such as Nova.
The purpose of the project is provide managed DNS for the Openstack Ecosystem using a REST API or Designate Sink which consumes events from Nova or Quantum, or any other service that has events that would necessitate DNS changes. It also will replace Nova DNS bindings and provide much more robust and full-featured DNS functionality. Also, advanced DNS record support will be added such as DNSSEC.
Designate is relevant to the mission by adding a missing piece of data-center functionality, namely, one of the most ubiquitous services, DNS. It's relevant to other OpenStack projects by automating the name resolution changes required for the creation and deletion of Nova instances or other components.
Basic roadmap for the project
The current release provides
- REST API for domain/record management
- Multi-tenant
- Integrated with Keystone for authentication
- Framework in place to integrate with Nova and Quantum notifications (for auto-generated records)
- Support for PowerDNS, MySQLBind, and Bind out of the box
- Command Line Interface
- Python Bindings
Future release plans
- DNSSEC
- Development of functionality to utilize designate-sink to process events from Nova and Quantum
- Import/Export of Domains via BIND9 style zone files
- Private/Internal DNS servers
Location of project source code
Programming language, required technology dependencies
- Language
- Python
- Dependencies
- flask, message queue, DNS server, database server
Is project currently open sourced? What license?
Yes, under the Apache 2.0 license.
Level of maturity of software and team
- Software: Private Beta at HPCS. Implementations at other organizations.
- Team: Working together for six months.
Proposed project technical lead and qualifications
- Kiall Mac Innes (kiall)
- Kiall has worked on OpenStack for ~2 years. He has an extensive understanding of DNS and is the lead author of Designate.
Other project developers and qualifications
- Simon McCartney (simonmcc)
- Simon has Extensive DNS, Orchestration, Database, and operation experience.
- Patrick Galbraith (CaptTofu)
- Patrick Galbraith has extensive database, operational and has worked on various aspects of Openstack and related projects (Red Dwarf)
- Endre Karlson (zykes-)
- DNS, Linux, Orchestration, Database, Python, Ruby, Billingstack
- Ryan Lane (Ryan_Lane)
- Experience with operating other OpenStack projects, maintainer of legacy nova dns code and maintainer of DNS code for Wikimedia Labs. Will use Designate in production soon and will be writing a gdnsd driver.
Infrastructure requirements (testing, etc)
Currently on StackForge using Gerrit and Jenkins to runs the unit test suite and pyflakes plus pep8. No additional infrastructure requirements are expected.
Have all current contributors agreed to the OpenStack CLA?
Yes.
Related Links
- Documentation
- Designate on OpenStack Wiki
- Designate Talk at the Portland Summit
- Openstack DNS solutions comparison pre-San Diego Summit
- San Diego Summit Etherpad
Status
To be completed by PPB