Jump to: navigation, search

Difference between revisions of "Designate/Old Incubation Application"

(Describe the relevance of the project to other OpenStack projects and the OpenStack mission to provide a ubiquitous cloud computing platform:)
 
(25 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Project codename: ==
+
== Project codename ==
  
Moniker
+
Designate
  
== Summary: ==
+
== Summary ==
  
Moniker DNSaaS Project
+
Designate DNSaaS Project
  
== Detailed Description: ==
+
== Detailed Description ==
  
Moniker is a an 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 Moniker 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.
+
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.
  
=== What is the purpose of the project and vision for it? ===
+
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.
  
To provide managed DNS for the Openstack Ecosystem using a REST API or Moniker 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.
  
=== Describe the relevance of the project to other [[OpenStack]] projects and the [[OpenStack]] mission to provide a ubiquitous cloud computing platform: ===
+
== Basic roadmap for the project ==
  
Moniker is adding a missing piece of data-center functionality, namely, one of the most ubiquitous services, DNS. Moniker will automate the name resolution changes required for the creation and deletion of Nova instances or other components.
+
=== The current release provides ===
 
 
== Basic roadmap for the project: ==
 
 
 
The current release provides:
 
  
 
* REST API for domain/record management
 
* REST API for domain/record management
Line 28: Line 24:
 
* Framework in place to integrate with Nova and Quantum notifications (for auto-generated records)
 
* Framework in place to integrate with Nova and Quantum notifications (for auto-generated records)
 
* Support for PowerDNS, MySQLBind, and Bind out of the box
 
* Support for PowerDNS, MySQLBind, and Bind out of the box
 +
* Command Line Interface
 +
* Python Bindings
  
== Location of project source code: ==
+
=== Future release plans ===
  
https://github.com/stackforge/moniker/
+
* 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
  
== Programming language, required technology dependencies: ==
+
== Location of project source code ==
  
Python, Message Queue, PowerDNS, BIND9 or other DNS server
+
* [https://launchpad.net/moniker Designate on Launchpad]
 +
* [https://github.com/stackforge/moniker/ Designate at StackForge]
 +
* [https://github.com/stackforge/python-monikerclient/ python-designateclient at StackForge]
  
== Is project currently open sourced? What license?: ==
+
== Programming language, required technology dependencies ==
  
Yes, under the Apache 2.0 license.
+
;Language: Python
  
== Level of maturity of software and team: ==
+
;Dependencies: flask, message queue, DNS server, database server
  
Software: Private Beta at HPCS. Implementations at other organizations.
+
== Is project currently open sourced? What license? ==
Team: Working together for six months
 
  
== Proposed project technical lead and qualifications: ==
+
Yes, under the Apache 2.0 license.
  
Kiall Mac Innes (kiall)
+
== Level of maturity of software and team ==
  
Kiall has worked on Openstack for 2 years. He has an extensive understand of DNS and is the lead author of Moniker
+
* Software: Private Beta at HP Cloud. Implementations at other organizations.
 +
* Team: Working together for six months.
  
== Other project developers and qualifications: ==
+
== Proposed project technical lead and qualifications ==
  
Simon McCartney (simonmcc)
+
;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.
  
Simon has Extensive DNS, Orchestration, Database, and operation experience.
+
== Other project developers and qualifications ==
  
Patrick Galbraith (capttofu)
+
;Simon McCartney (simonmcc): Simon has Extensive DNS, Orchestration, Database, and operation experience.
  
Patrick Galbraith has extensive database, operational and has worked on various aspects of Openstack and related projects (Red Dwarf)
+
;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-)
+
;Endre Karlson (zykes-): DNS, Linux, Orchestration, Database, Python, Ruby, Billingstack
  
== Infrastructure requirements (testing, etc): ==
+
;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.
  
Currently on StackForge using Gerrit and Jenkins to runs the unit test suite and pyflakes plus pep8.
+
== 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? ==
 
== Have all current contributors agreed to the OpenStack CLA? ==
Line 72: Line 77:
 
Yes.
 
Yes.
  
== Status: ==
+
== Related Links ==
 +
 
 +
* [http://moniker.readthedocs.org/ Documentation]
 +
* [https://wiki.openstack.org/wiki/Designate Designate on OpenStack Wiki]
 +
* [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://etherpad.openstack.org/openstack-dns San Diego Summit Etherpad]
 +
 
 +
== Status ==
  
 
To be completed by PPB
 
To be completed by PPB

Latest revision as of 18:25, 30 April 2014

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 HP Cloud. 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

Status

To be completed by PPB