[Openstack] [Networking/DNS] Proposal to make Moniker the default for DNS
Hi, I would like to propose Moniker as the default for DNS going forwards. We where picked in a vote by several interested people to be the default DNS implementation last year out of the available projects. The current state of the project is: * Several DNSaaS is built on Moniker - HP Cloud's for one. * Support for multiple record types A, , SPF, CNAME, NS, MX, configurable TTLs. * Pluggable storage layer - currently only SQLAlchemy. * Pluggable DNS backends that can either be run in a Central process or in agents on seperate servers for redundancy - Bind9, Bind9 with MySQL, PowerDNS, DNSMasq * Pluggable notification handling - Support for Quantum and Nova via MQ notifications. * REST API using Flask and JSONSchema. * python-monikerclient for bindings / cli. Github / Code: http://github.com/stackforge/moniker Bugs / LP: http://launchpad.net/moniker IRC: #openstack-dns Endre Karlson ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Networking/DNS] Proposal to make Moniker the default for DNS
Obviously, I'm biased, But I'll +1 this! I'll also add that we have a conference session at 11:50am on the Monday, and an unconference room at 2:40pm on the same day. Anyone who's interested, please attend :) Hope to see you there! Kiall Mac Innes HP Cloud Services - DNSaaS Mobile: +353 86 345 9333 Landline: +353 1 524 2177 GPG: E9498407 On 19/03/13 08:40, Endre Karlson wrote: Hi, I would like to propose Moniker as the default for DNS going forwards. We where picked in a vote by several interested people to be the default DNS implementation last year out of the available projects. The current state of the project is: * Several DNSaaS is built on Moniker - HP Cloud's for one. * Support for multiple record types A, , SPF, CNAME, NS, MX, configurable TTLs. * Pluggable storage layer - currently only SQLAlchemy. * Pluggable DNS backends that can either be run in a Central process or in agents on seperate servers for redundancy - Bind9, Bind9 with MySQL, PowerDNS, DNSMasq * Pluggable notification handling - Support for Quantum and Nova via MQ notifications. * REST API using Flask and JSONSchema. * python-monikerclient for bindings / cli. Github / Code: http://github.com/stackforge/moniker Bugs / LP: http://launchpad.net/moniker IRC: #openstack-dns Endre Karlson ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Networking/DNS] Proposal to make Moniker the default for DNS
Sounds great! I'm using moniker + keystone in production with bind9. It fits perfectly in the big picture (IMO). Davide. On 19/mar/2013, at 12:04, Mac Innes, Kiall ki...@hp.com wrote: Obviously, I'm biased, But I'll +1 this! I'll also add that we have a conference session at 11:50am on the Monday, and an unconference room at 2:40pm on the same day. Anyone who's interested, please attend :) Hope to see you there! Kiall Mac Innes HP Cloud Services - DNSaaS Mobile: +353 86 345 9333 Landline: +353 1 524 2177 GPG: E9498407 On 19/03/13 08:40, Endre Karlson wrote: Hi, I would like to propose Moniker as the default for DNS going forwards. We where picked in a vote by several interested people to be the default DNS implementation last year out of the available projects. The current state of the project is: * Several DNSaaS is built on Moniker - HP Cloud's for one. * Support for multiple record types A, , SPF, CNAME, NS, MX, configurable TTLs. * Pluggable storage layer - currently only SQLAlchemy. * Pluggable DNS backends that can either be run in a Central process or in agents on seperate servers for redundancy - Bind9, Bind9 with MySQL, PowerDNS, DNSMasq * Pluggable notification handling - Support for Quantum and Nova via MQ notifications. * REST API using Flask and JSONSchema. * python-monikerclient for bindings / cli. Github / Code: http://github.com/stackforge/moniker Bugs / LP: http://launchpad.net/moniker IRC: #openstack-dns Endre Karlson ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Networking/DNS] Proposal to make Moniker the default for DNS
+1 -- Diego Parrilla http://www.stackops.com/*CEO* *www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 | skype:diegoparrilla* * http://www.stackops.com/ * * On Tue, Mar 19, 2013 at 9:39 AM, Endre Karlson endre.karl...@gmail.comwrote: Hi, I would like to propose Moniker as the default for DNS going forwards. We where picked in a vote by several interested people to be the default DNS implementation last year out of the available projects. The current state of the project is: * Several DNSaaS is built on Moniker - HP Cloud's for one. * Support for multiple record types A, , SPF, CNAME, NS, MX, configurable TTLs. * Pluggable storage layer - currently only SQLAlchemy. * Pluggable DNS backends that can either be run in a Central process or in agents on seperate servers for redundancy - Bind9, Bind9 with MySQL, PowerDNS, DNSMasq * Pluggable notification handling - Support for Quantum and Nova via MQ notifications. * REST API using Flask and JSONSchema. * python-monikerclient for bindings / cli. Github / Code: http://github.com/stackforge/moniker Bugs / LP: http://launchpad.net/moniker IRC: #openstack-dns Endre Karlson ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Networking/DNS] Proposal to make Moniker the default for DNS
On 03/19/2013 01:39 AM, Endre Karlson wrote: Hi, I would like to propose Moniker as the default for DNS going forwards. We where picked in a vote by several interested people to be the default DNS implementation last year out of the available projects. The current state of the project is: * Several DNSaaS is built on Moniker - HP Cloud's for one. * Support for multiple record types A, , SPF, CNAME, NS, MX, configurable TTLs. * Pluggable storage layer - currently only SQLAlchemy. * Pluggable DNS backends that can either be run in a Central process or in agents on seperate servers for redundancy - Bind9, Bind9 with MySQL, PowerDNS, DNSMasq * Pluggable notification handling - Support for Quantum and Nova via MQ notifications. * REST API using Flask and JSONSchema. * python-monikerclient for bindings / cli. Recommend applying for incubation. An example request: https://lists.launchpad.net/openstack/msg14700.html The process can be found here: https://wiki.openstack.org/wiki/Governance/Approved/Incubation Github / Code: http://github.com/stackforge/moniker Bugs / LP: http://launchpad.net/moniker IRC: #openstack-dns Endre Karlson ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
