https://wiki.openstack.org/w/api.php?action=feedcontributions&user=Eankutse&feedformat=atomOpenStack - User contributions [en]2024-03-28T12:14:25ZUser contributionsMediaWiki 1.28.2https://wiki.openstack.org/w/index.php?title=Meetings/Designate&diff=55438Meetings/Designate2014-06-10T19:17:06Z<p>Eankutse: /* Agenda */</p>
<hr />
<div><br />
= DNSaaS Meetings =<br />
<br />
The DNSaaS team holds a weekly IRC meeting in #openstack-meeting-alt on Wednesdays at 17:00 UTC<br />
<br />
Meeting logs are available at http://eavesdrop.openstack.org/meetings/designate/<br />
<br />
== Next meeting ==<br />
<br />
Date of next meeting [http://www.timeanddate.com/worldclock/fixedtime.html?ah=1&iso=20140528T17 Wednesday 4 June, 17:00 UTC]<br />
<br />
We are back to our regularly scheduled IRC meetings after meeting on Google Hangouts for OpenStack Atlanta Summit preparation.<br />
<br />
=== Agenda ===<br />
<br />
* Review action items from last week (See [http://eavesdrop.openstack.org/meetings/designate/ Meeting Logs] for previous week)<br />
* Specific Items:<br />
** How does our [https://blueprints.launchpad.net/designate/+spec/server-pools#deptree dependency tree] get updated based on our [https://etherpad.openstack.org/p/juno-design-summit-designate-session-2 Atlanta sessions]?<br />
* Status of BIND9 backend driver (Ron)<br />
* Mini DNS - is 'mdns-designate-mdns-functional' a place holder or explicit functionality? (eankutse) <br />
**https://blueprints.launchpad.net/designate/+spec/mdns-designate-mdns-functional<br />
* Open Discussion<br />
<br />
== Future meetings ==<br />
<br />
Possible Agenda Topics:<br />
<br />
* Incubation ReDiscussion (Delay to post TC policy changes)<br />
* Incubation Vote</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Incubation_Application&diff=52437Designate/Incubation Application2014-05-15T20:39:17Z<p>Eankutse: /* Emmanuel Ankutse */</p>
<hr />
<div>== Project codename==<br />
Designate<br />
== Trademarks ==<br />
''(Does this project name, codename or contents use any trademarks, and if so, who owns them? List the codenames or other marks for which a trademark search should occur.)''<br />
<br />
No known trademarks. Project codename is "designate"<br />
<br />
== Summary (one sentence abstract of the project) ==<br />
<br />
Designate is a DNS as a Service (DNSaaS) for OpenStack clouds.<br />
<br />
== Parent Program name and PTL ==<br />
=== Program ===<br />
DNS Program. [[Designate/Program_Application]]<br />
<br />
== Mission statement ==<br />
''(if the project is part of a new OpenStack program)''<br />
<br />
[[Designate/Program_Application]]<br />
<br />
== Detailed Description ==<br />
''(what is the purpose of the project and vision for it? describe the relevance of the project to other OpenStack projects and the OpenStack mission to provide a ubiquitous cloud computing platform)''<br />
<br />
Designate is a critical missing piece of the OpenStack driven data center - one of the most ubiquitous services, DNS. Designate is relevant to other OpenStack projects by automating the name resolution changes required for the creation and deletion of Nova instances, Trove databases or other components.<br />
<br />
Designate provides DNS for both end user zones, and for other OpenStack projects. This functionality is exposed through a REST API, that is consistent with the standards in OpenStack projects today. Designate has a vendor neutral plugable architecture that allows nearly all the internal components to be replaced as needed.<br />
<br />
== Basic roadmap for the project ==<br />
=== Near Future ===<br />
# MiniDNS (new method for providing customer facing DNS servers with updates)<br />
# Pools (Allow for designate to control multiple groups of servers)<br />
# Private Pools<br />
# V2 API<br />
<br />
== Location of project source code ==<br />
[https://github.com/stackforge/designate https://github.com/stackforge/designate]<br />
<br />
[https://github.com/stackforge/python-designateclient https://github.com/stackforge/python-designateclient]<br />
<br />
== Programming language, required technology dependencies ==<br />
=== Language: ===<br />
Python<br />
<br />
=== Dependencies ===<br />
Message queue, DNS server, database server, keystone<br />
<br />
== Is project currently open sourced? What license? ==<br />
Yes - Licensed under the Apache License, Version 2.0<br />
<br />
== Level of maturity of software and team ==<br />
=== Software ===<br />
Running as a GA service in HP Helion Public Cloud for over a year, and been in development for over two years.<br />
<br />
=== Team ===<br />
We have a diverse group of highly skilled developers from a range of companies including, HP, Rackspace, eBay Inc. and Red Hat.<br />
<br />
== Project developers qualifications ==<br />
=== Kiall Mac Innes ===<br />
<br />
Kiall is the Technical Lead for the HP "Helion" Cloud DNS team - responsible for both the operation of the production service, and ongoing development. Kiall is also the lead and founding developer of the Designate project and has been involved in OpenStack since Diablo, from both the operational and development sides.<br />
<br />
=== Graham Hayes ===<br />
<br />
=== Endre Karlson ===<br />
<br />
=== Betsy Luzader ===<br />
<br />
=== Vinod Mangalpally ===<br />
Vinod is a software developer at Rackspace working on Designate.<br />
<br />
=== Emmanuel Ankutse ===<br />
Emmanuel Ankutse is a contributor to Designate. He is a software developer at Rackspace and has been with Rackspace since 2009. Emmanuel Ankutse also contributed to the implementation of the current Cloud DNS API solution at Rackspace and has been in enterprise software development since 1990.<br />
<br />
=== Tim Simmons ===<br />
<br />
=== Joe McBride ===<br />
<br />
=== Ron Rickard ===<br />
==== Sr. Cloud Engineer, eBay Inc. ====<br />
Ron is a IT professional with over 25 years experience with emphasis on devops. Ron spent the past 2 years at eBay Inc. working on DNSaaS solutions for eBay's OpenStack cloud including contributions to the Designate open source project.<br />
<br />
=== Rich Megginson ===<br />
<br />
== Infrastructure requirements (testing, etc) ==<br />
We currently use stackforge / gerrit / jenkins for our testing suite - we do not see any additional requirements on top of what the infra team provide<br />
== Have all current contributors agreed to the OpenStack CLA? ==<br />
Yes</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=51582Designate/Atlanta/Workshop 12014-05-07T15:46:59Z<p>Eankutse: </p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#:*vagrant up<br />
# Log into the VM<br />
#:* vagrant ssh<br />
# Install Designate and its dependencies<br />
#:* cd /home/vagrant/designate<br />
#:* ''sudo apt-get -y build-dep python-lxml''<br />
#:* ''sudo pip install -r requirements.txt -r test-requirements.txt''<br />
#:* sudo python setup.py develop<br />
# Make copies of designate config files from templates<br />
#:* cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#:* ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Copy over config file with pre-set values to designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/designate.conf.wkshp )<br />
#:* cp /home/vagrant/designate.conf.wkshp ./designate.conf<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#:* sudo mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#:* sudo mkdir /home/vagrant/designate/log<br />
==== Verify the DNS server (PowerDNS) config ====<br />
Verify 'gmysql-dbname='''pdns'''' in /etc/powerdns/pdns.d/pdns.local.gmysql<br />
:* cat /etc/powerdns/pdns.d/pdns.local.gmysql<br />
<br />
==== Verify PowerDNS is running on port 53 ====<br />
:* sudo netstat -tnlp (look for '''pdns_server-in''')<br />
<br />
==== Test PowerDNS ====<br />
:* dig @localhost openstack.com (You should get some response with status:SERVFAIL)<br />
<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
:* mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
:* sudo designate-manage database init<br />
:* sudo designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
(Database already exists. Just init and sync)<br />
:* sudo designate-manage powerdns init<br />
:* sudo designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
:* sudo designate-central &<br />
<br />
==== Start the Designate API Service ====<br />
:* sudo designate-api &<br />
<br />
==== Check services are up ====<br />
:* ps aux | grep designate<br />
<br />
==== Setup the Designate Keystone service and endpoints ====<br />
First set user 'admin' particulars then create service and endpoint<br />
:* source /home/vagrant/openrc.admin <br />
:* keystone service-create --name designate --type dns --description "Designate Service"<br />
:* keystone endpoint-create --service designate --publicurl http://127.0.0.1:9001/v1 --adminurl http://127.0.0.1:9001/v1 --internalurl http://127.0.0.1:9001/v1<br />
<br />
=== Install Designate Client ===<br />
:* cd /home/vagrant/python-designateclient<br />
:* sudo pip install -r requirements.txt -r test-requirements.txt<br />
:* sudo python setup.py develop<br />
===== Test Designate Client =====<br />
:* cd /home/vagrant<br />
:* source openrc.admin<br />
:* designate --debug server-list<br />
<br />
=== Exercise the Designate API ===<br />
=====Test API locally on VM: =====<br />
:* curl http://localhost:9001<br />
=====Test API from External Client (e.g. Google Chrome HTTP Client):=====<br />
:* http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* killall designate-api <br />
* killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
*PowerDNS was used as the backend rather than BIND as it is better tested as of now. <br />
*A single node was used so that it is easier to control and easier for newbies to install.</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=51578Designate/Atlanta/Workshop 12014-05-07T15:39:19Z<p>Eankutse: </p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#:*vagrant up<br />
# Log into the VM<br />
#:* vagrant ssh<br />
# Install Designate and its dependencies<br />
#:* cd /home/vagrant/designate<br />
#:* ''sudo apt-get -y build-dep python-lxml''<br />
#:* ''sudo pip install -r requirements.txt -r test-requirements.txt''<br />
#:* sudo python setup.py develop<br />
# Make copies of designate config files from templates<br />
#:* cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#:* ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Copy over config file with pre-set values to designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/designate.conf.wkshp )<br />
#:* cp /home/vagrant/designate.conf.wkshp ./designate.conf<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#:* sudo mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#:* sudo mkdir /home/vagrant/designate/log<br />
==== Verify the DNS server (PowerDNS) config ====<br />
Verify 'gmysql-dbname='''pdns'''' in /etc/powerdns/pdns.d/pdns.local.gmysql<br />
:* cat /etc/powerdns/pdns.d/pdns.local.gmysql<br />
<br />
==== Verify PowerDNS is running on port 53 ====<br />
:* sudo netstat -tnlp (look for '''pdns_server-in''')<br />
<br />
==== Test PowerDNS ====<br />
:* dig @localhost openstack.com (You should get some response with status:SERVFAIL)<br />
<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
:* mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
:* sudo designate-manage database init<br />
:* sudo designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
(Database already exists. Just init and sync)<br />
:* sudo designate-manage powerdns init<br />
:* sudo designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
:* sudo designate-central &<br />
<br />
==== Start the Designate API Service ====<br />
:* sudo designate-api &<br />
<br />
==== Check services are up ====<br />
:* ps aux | grep designate<br />
<br />
==== Setup the Designate Keystone service and endpoints ====<br />
First set user 'admin' particulars then create service and endpoint<br />
:* source /home/vagrant/openrc.admin <br />
:* keystone service-create --name designate --type dns --description "Designate Service"<br />
:* keystone endpoint-create --service designate --publicurl http://127.0.0.1:9001/v1 --adminurl http://127.0.0.1:9001/v1 --internalurl http://127.0.0.1:9001/v1<br />
<br />
=== Install Designate Client ===<br />
:* cd /home/vagrant/python-designateclient<br />
:* pip install -r requirements.txt -r test-requirements.txt<br />
:* python setup.py develop<br />
===== Test Designate Client =====<br />
:* cd /home/vagrant<br />
:* source openrc.admin<br />
:* designate --debug server-list<br />
<br />
=== Exercise the Designate API ===<br />
=====Test API locally on VM: =====<br />
:* curl http://localhost:9001<br />
=====Test API from External Client (e.g. Google Chrome HTTP Client):=====<br />
:* http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* killall designate-api <br />
* killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
*PowerDNS was used as the backend rather than BIND as it is better tested as of now. <br />
*A single node was used so that it is easier to control and easier for newbies to install.</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=51576Designate/Atlanta/Workshop 12014-05-07T15:34:05Z<p>Eankutse: </p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#:*vagrant up<br />
# Log into the VM<br />
#:* vagrant ssh<br />
# Install Designate and its dependencies<br />
#:* cd /home/vagrant/designate<br />
#:* ''sudo apt-get -y build-dep python-lxml''<br />
#:* ''sudo pip install -r requirements.txt -r test-requirements.txt''<br />
#:* sudo python setup.py develop<br />
# Make copies of designate config files from templates<br />
#:* cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#:* ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Copy over config file with pre-set values to designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/designate.conf.wkshp )<br />
#:* cp /home/vagrant/designate.conf.wkshp ./designate.conf<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#:* sudo mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#:* sudo mkdir /home/vagrant/designate/log<br />
==== Verify the DNS server (PowerDNS) config ====<br />
Verify 'gmysql-dbname='''pdns'''' in /etc/powerdns/pdns.d/pdns.local.gmysql<br />
:* cat /etc/powerdns/pdns.d/pdns.local.gmysql<br />
<br />
==== Verify PowerDNS is running on port 53 ====<br />
:* sudo netstat -tnlp (look for '''pdns_server-in''')<br />
<br />
==== Test PowerDNS ====<br />
:* dig @localhost openstack.com (You should get some response with status:SERVFAIL)<br />
<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
:* mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
:* sudo designate-manage database init<br />
:* sudo designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
(Database already exists. Just init and sync)<br />
:* sudo designate-manage powerdns init<br />
:* sudo designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
:* designate-central &<br />
<br />
==== Start the Designate API Service ====<br />
:* designate-api &<br />
<br />
==== Check services are up ====<br />
:* ps aux | grep designate<br />
<br />
==== Setup the Designate Keystone service and endpoints ====<br />
First set user 'admin' particulars then create service and endpoint<br />
:* source /home/vagrant/openrc.admin <br />
:* keystone service-create --name designate --type dns --description "Designate Service"<br />
:* keystone endpoint-create --service designate --publicurl http://127.0.0.1:9001/v1 --adminurl http://127.0.0.1:9001/v1 --internalurl http://127.0.0.1:9001/v1<br />
<br />
=== Install Designate Client ===<br />
:* cd /home/vagrant/python-designateclient<br />
:* pip install -r requirements.txt -r test-requirements.txt<br />
:* python setup.py develop<br />
===== Test Designate Client =====<br />
:* cd /home/vagrant<br />
:* source openrc.admin<br />
:* designate --debug server-list<br />
<br />
=== Exercise the Designate API ===<br />
=====Test API locally on VM: =====<br />
:* curl http://localhost:9001<br />
=====Test API from External Client (e.g. Google Chrome HTTP Client):=====<br />
:* http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* killall designate-api <br />
* killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
*PowerDNS was used as the backend rather than BIND as it is better tested as of now. <br />
*A single node was used so that it is easier to control and easier for newbies to install.</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=51575Designate/Atlanta/Workshop 12014-05-07T15:32:37Z<p>Eankutse: </p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#:*vagrant up<br />
# Log into the VM<br />
#:* vagrant ssh<br />
# Install Designate and its dependencies<br />
#:* cd /home/vagrant/designate<br />
#:* ''sudo apt-get -y build-dep python-lxml''<br />
#:* ''sudo pip install -r requirements.txt -r test-requirements.txt''<br />
#:* sudo python setup.py develop<br />
# Make copies of designate config files from templates<br />
#:* cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#:* ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Copy over config file with pre-set values to designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/designate.conf.wkshp )<br />
#:* cp /home/vagrant/designate.conf.wkshp ./designate.conf<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#:* sudo mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#:* sudo mkdir /home/vagrant/designate/log<br />
==== Verify the DNS server (PowerDNS) config ====<br />
Verify 'gmysql-dbname='''pdns'''' in /etc/powerdns/pdns.d/pdns.local.gmysql<br />
:* cat /etc/powerdns/pdns.d/pdns.local.gmysql<br />
<br />
==== Verify PowerDNS is running on port 53 ====<br />
:* sudo netstat -tnlp (look for '''pdns_server-in''')<br />
<br />
==== Test PowerDNS ====<br />
:* dig @localhost openstack.com (You should get some response with status:SERVFAIL)<br />
<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
:* mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
:* sudo designate-manage database init<br />
:* sudo designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
(Database already exists. Just init and sync)<br />
:* designate-manage powerdns init<br />
:* designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
:* designate-central &<br />
<br />
==== Start the Designate API Service ====<br />
:* designate-api &<br />
<br />
==== Check services are up ====<br />
:* ps aux | grep designate<br />
<br />
==== Setup the Designate Keystone service and endpoints ====<br />
First set user 'admin' particulars then create service and endpoint<br />
:* source /home/vagrant/openrc.admin <br />
:* keystone service-create --name designate --type dns --description "Designate Service"<br />
:* keystone endpoint-create --service designate --publicurl http://127.0.0.1:9001/v1 --adminurl http://127.0.0.1:9001/v1 --internalurl http://127.0.0.1:9001/v1<br />
<br />
=== Install Designate Client ===<br />
:* cd /home/vagrant/python-designateclient<br />
:* pip install -r requirements.txt -r test-requirements.txt<br />
:* python setup.py develop<br />
===== Test Designate Client =====<br />
:* cd /home/vagrant<br />
:* source openrc.admin<br />
:* designate --debug server-list<br />
<br />
=== Exercise the Designate API ===<br />
=====Test API locally on VM: =====<br />
:* curl http://localhost:9001<br />
=====Test API from External Client (e.g. Google Chrome HTTP Client):=====<br />
:* http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* killall designate-api <br />
* killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
*PowerDNS was used as the backend rather than BIND as it is better tested as of now. <br />
*A single node was used so that it is easier to control and easier for newbies to install.</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=51574Designate/Atlanta/Workshop 12014-05-07T15:32:05Z<p>Eankutse: </p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#:*vagrant up<br />
# Log into the VM<br />
#:* vagrant ssh<br />
# Install Designate and its dependencies<br />
#:* cd /home/vagrant/designate<br />
#:* ''sudo apt-get -y build-dep python-lxml''<br />
#:* ''sudo pip install -r requirements.txt -r test-requirements.txt''<br />
#:* sudo python setup.py develop<br />
# Make copies of designate config files from templates<br />
#:* cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#:* ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Copy over config file with pre-set values to designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/designate.conf.wkshp )<br />
#:* cp /home/vagrant/designate.conf.wkshp ./designate.conf<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#:* sudo mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#:* sudo mkdir /home/vagrant/designate/log<br />
==== Verify the DNS server (PowerDNS) config ====<br />
Verify 'gmysql-dbname='''pdns'''' in /etc/powerdns/pdns.d/pdns.local.gmysql<br />
:* cat /etc/powerdns/pdns.d/pdns.local.gmysql<br />
<br />
==== Verify PowerDNS is running on port 53 ====<br />
:* sudo netstat -tnlp (look for '''pdns_server-in''')<br />
<br />
==== Test PowerDNS ====<br />
:* dig @localhost openstack.com (You should get some response with status:SERVFAIL)<br />
<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
:* mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
:* designate-manage database init<br />
:* designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
(Database already exists. Just init and sync)<br />
:* designate-manage powerdns init<br />
:* designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
:* designate-central &<br />
<br />
==== Start the Designate API Service ====<br />
:* designate-api &<br />
<br />
==== Check services are up ====<br />
:* ps aux | grep designate<br />
<br />
==== Setup the Designate Keystone service and endpoints ====<br />
First set user 'admin' particulars then create service and endpoint<br />
:* source /home/vagrant/openrc.admin <br />
:* keystone service-create --name designate --type dns --description "Designate Service"<br />
:* keystone endpoint-create --service designate --publicurl http://127.0.0.1:9001/v1 --adminurl http://127.0.0.1:9001/v1 --internalurl http://127.0.0.1:9001/v1<br />
<br />
=== Install Designate Client ===<br />
:* cd /home/vagrant/python-designateclient<br />
:* pip install -r requirements.txt -r test-requirements.txt<br />
:* python setup.py develop<br />
===== Test Designate Client =====<br />
:* cd /home/vagrant<br />
:* source openrc.admin<br />
:* designate --debug server-list<br />
<br />
=== Exercise the Designate API ===<br />
=====Test API locally on VM: =====<br />
:* curl http://localhost:9001<br />
=====Test API from External Client (e.g. Google Chrome HTTP Client):=====<br />
:* http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* killall designate-api <br />
* killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
*PowerDNS was used as the backend rather than BIND as it is better tested as of now. <br />
*A single node was used so that it is easier to control and easier for newbies to install.</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=51322Designate/Atlanta/Workshop 12014-05-05T22:07:51Z<p>Eankutse: /* Verify PowerDNS is running on port 53 */</p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#:*vagrant up<br />
# Log into the VM<br />
#:* vagrant ssh<br />
# Install Designate and its dependencies<br />
#:* cd /home/vagrant/designate<br />
#:* sudo apt-get -y build-dep python-lxml<br />
#:* sudo pip install -r requirements.txt -r test-requirements.txt<br />
#:* sudo python setup.py develop<br />
# Make copies of designate config files from templates<br />
#:* cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#:* ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Copy over config file with pre-set values to designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/designate.conf.wkshp )<br />
#:* cp /home/vagrant/designate.conf.wkshp ./designate.conf<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#:* sudo mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#:* sudo mkdir /home/vagrant/designate/log<br />
==== Verify the DNS server (PowerDNS) config ====<br />
Verify 'gmysql-dbname='''pdns'''' in /etc/powerdns/pdns.d/pdns.local.gmysql<br />
:* cat /etc/powerdns/pdns.d/pdns.local.gmysql<br />
<br />
==== Verify PowerDNS is running on port 53 ====<br />
:* sudo netstat -tnlp (look for '''pdns_server-in''')<br />
<br />
==== Test PowerDNS ====<br />
:* dig @localhost openstack.com (You should get some response with status:SERVFAIL)<br />
<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
:* mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
:* designate-manage database init<br />
:* designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
(Database already exists. Just init and sync)<br />
:* designate-manage powerdns init<br />
:* designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
:* designate-central &<br />
<br />
==== Start the Designate API Service ====<br />
:* designate-api &<br />
<br />
==== Check services are up ====<br />
:* ps aux | grep designate<br />
<br />
==== Setup the Designate Keystone service and endpoints ====<br />
First set user 'admin' particulars then create service and endpoint<br />
:* source /home/vagrant/openrc.admin <br />
:* keystone service-create --name designate --type dns --description "Designate Service"<br />
:* keystone endpoint-create --service designate --publicurl http://127.0.0.1:9001/v1 --adminurl http://127.0.0.1:9001/v1 --internalurl http://127.0.0.1:9001/v1<br />
<br />
=== Install Designate Client ===<br />
:* cd /home/vagrant/python-designateclient<br />
:* pip install -r requirements.txt -r test-requirements.txt<br />
:* python setup.py develop<br />
===== Test Designate Client =====<br />
:* cd /home/vagrant<br />
:* source openrc.admin<br />
:* designate --debug server-list<br />
<br />
=== Exercise the Designate API ===<br />
=====Test API locally on VM: =====<br />
:* curl http://localhost:9001<br />
=====Test API from External Client (e.g. Google Chrome HTTP Client):=====<br />
:* http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* killall designate-api <br />
* killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
*PowerDNS was used as the backend rather than BIND as it is better tested as of now. <br />
*A single node was used so that it is easier to control and easier for newbies to install.</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=51321Designate/Atlanta/Workshop 12014-05-05T22:05:54Z<p>Eankutse: /* Install Designate */</p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#:*vagrant up<br />
# Log into the VM<br />
#:* vagrant ssh<br />
# Install Designate and its dependencies<br />
#:* cd /home/vagrant/designate<br />
#:* sudo apt-get -y build-dep python-lxml<br />
#:* sudo pip install -r requirements.txt -r test-requirements.txt<br />
#:* sudo python setup.py develop<br />
# Make copies of designate config files from templates<br />
#:* cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#:* ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Copy over config file with pre-set values to designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/designate.conf.wkshp )<br />
#:* cp /home/vagrant/designate.conf.wkshp ./designate.conf<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#:* sudo mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#:* sudo mkdir /home/vagrant/designate/log<br />
==== Verify the DNS server (PowerDNS) config ====<br />
Verify 'gmysql-dbname='''pdns'''' in /etc/powerdns/pdns.d/pdns.local.gmysql<br />
:* cat /etc/powerdns/pdns.d/pdns.local.gmysql<br />
<br />
==== Verify PowerDNS is running on port 53 ====<br />
:* netstat -tnlp (look for '''pdns_server-in''')<br />
<br />
==== Test PowerDNS ====<br />
:* dig @localhost openstack.com (You should get some response with status:SERVFAIL)<br />
<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
:* mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
:* designate-manage database init<br />
:* designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
(Database already exists. Just init and sync)<br />
:* designate-manage powerdns init<br />
:* designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
:* designate-central &<br />
<br />
==== Start the Designate API Service ====<br />
:* designate-api &<br />
<br />
==== Check services are up ====<br />
:* ps aux | grep designate<br />
<br />
==== Setup the Designate Keystone service and endpoints ====<br />
First set user 'admin' particulars then create service and endpoint<br />
:* source /home/vagrant/openrc.admin <br />
:* keystone service-create --name designate --type dns --description "Designate Service"<br />
:* keystone endpoint-create --service designate --publicurl http://127.0.0.1:9001/v1 --adminurl http://127.0.0.1:9001/v1 --internalurl http://127.0.0.1:9001/v1<br />
<br />
=== Install Designate Client ===<br />
:* cd /home/vagrant/python-designateclient<br />
:* pip install -r requirements.txt -r test-requirements.txt<br />
:* python setup.py develop<br />
===== Test Designate Client =====<br />
:* cd /home/vagrant<br />
:* source openrc.admin<br />
:* designate --debug server-list<br />
<br />
=== Exercise the Designate API ===<br />
=====Test API locally on VM: =====<br />
:* curl http://localhost:9001<br />
=====Test API from External Client (e.g. Google Chrome HTTP Client):=====<br />
:* http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* killall designate-api <br />
* killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
*PowerDNS was used as the backend rather than BIND as it is better tested as of now. <br />
*A single node was used so that it is easier to control and easier for newbies to install.</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=51320Designate/Atlanta/Workshop 12014-05-05T22:03:26Z<p>Eankutse: /* Install Designate */</p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#:*vagrant up<br />
# Log into the VM<br />
#:* vagrant ssh<br />
# Install Designate and its dependencies<br />
#:* cd /home/vagrant/designate<br />
#:* sudo apt-get -y build-dep python-lxml<br />
#:* sudo pip install -r requirements.txt -r test-requirements.txt<br />
#:* sudo python setup.py develop<br />
# Make copies of designate config files from templates<br />
#:* cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#:* ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Copy over config file with pre-set values to designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/designate.conf.wkshp )<br />
#:* cp /home/vagrant/designate.conf.wkshp ./designate.conf<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#:* mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#:* mkdir /home/vagrant/designate/log<br />
==== Verify the DNS server (PowerDNS) config ====<br />
Verify 'gmysql-dbname='''pdns'''' in /etc/powerdns/pdns.d/pdns.local.gmysql<br />
:* cat /etc/powerdns/pdns.d/pdns.local.gmysql<br />
<br />
==== Verify PowerDNS is running on port 53 ====<br />
:* netstat -tnlp (look for '''pdns_server-in''')<br />
<br />
==== Test PowerDNS ====<br />
:* dig @localhost openstack.com (You should get some response with status:SERVFAIL)<br />
<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
:* mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
:* designate-manage database init<br />
:* designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
(Database already exists. Just init and sync)<br />
:* designate-manage powerdns init<br />
:* designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
:* designate-central &<br />
<br />
==== Start the Designate API Service ====<br />
:* designate-api &<br />
<br />
==== Check services are up ====<br />
:* ps aux | grep designate<br />
<br />
==== Setup the Designate Keystone service and endpoints ====<br />
First set user 'admin' particulars then create service and endpoint<br />
:* source /home/vagrant/openrc.admin <br />
:* keystone service-create --name designate --type dns --description "Designate Service"<br />
:* keystone endpoint-create --service designate --publicurl http://127.0.0.1:9001/v1 --adminurl http://127.0.0.1:9001/v1 --internalurl http://127.0.0.1:9001/v1<br />
<br />
=== Install Designate Client ===<br />
:* cd /home/vagrant/python-designateclient<br />
:* pip install -r requirements.txt -r test-requirements.txt<br />
:* python setup.py develop<br />
===== Test Designate Client =====<br />
:* cd /home/vagrant<br />
:* source openrc.admin<br />
:* designate --debug server-list<br />
<br />
=== Exercise the Designate API ===<br />
=====Test API locally on VM: =====<br />
:* curl http://localhost:9001<br />
=====Test API from External Client (e.g. Google Chrome HTTP Client):=====<br />
:* http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* killall designate-api <br />
* killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
*PowerDNS was used as the backend rather than BIND as it is better tested as of now. <br />
*A single node was used so that it is easier to control and easier for newbies to install.</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=51310Designate/Atlanta/Workshop 12014-05-05T21:29:58Z<p>Eankutse: </p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#:*vagrant up<br />
# Log into the VM<br />
#:* vagrant ssh<br />
# Install Designate and its dependencies<br />
#:* cd /home/vagrant/designate<br />
#:* apt-get -y build-dep python-lxml<br />
#:* pip install -r requirements.txt -r test-requirements.txt<br />
#:* python setup.py develop<br />
# Make copies of designate config files from templates<br />
#:* cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#:* ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Copy over config file with pre-set values to designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/designate.conf.wkshp )<br />
#:* cp /home/vagrant/designate.conf.wkshp ./designate.conf<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#:* mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#:* mkdir /home/vagrant/designate/log<br />
==== Verify the DNS server (PowerDNS) config ====<br />
Verify 'gmysql-dbname='''pdns'''' in /etc/powerdns/pdns.d/pdns.local.gmysql<br />
:* cat /etc/powerdns/pdns.d/pdns.local.gmysql<br />
<br />
==== Verify PowerDNS is running on port 53 ====<br />
:* netstat -tnlp (look for '''pdns_server-in''')<br />
<br />
==== Test PowerDNS ====<br />
:* dig @localhost openstack.com (You should get some response with status:SERVFAIL)<br />
<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
:* mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
:* designate-manage database init<br />
:* designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
(Database already exists. Just init and sync)<br />
:* designate-manage powerdns init<br />
:* designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
:* designate-central &<br />
<br />
==== Start the Designate API Service ====<br />
:* designate-api &<br />
<br />
==== Check services are up ====<br />
:* ps aux | grep designate<br />
<br />
==== Setup the Designate Keystone service and endpoints ====<br />
First set user 'admin' particulars then create service and endpoint<br />
:* source /home/vagrant/openrc.admin <br />
:* keystone service-create --name designate --type dns --description "Designate Service"<br />
:* keystone endpoint-create --service designate --publicurl http://127.0.0.1:9001/v1 --adminurl http://127.0.0.1:9001/v1 --internalurl http://127.0.0.1:9001/v1<br />
<br />
=== Install Designate Client ===<br />
:* cd /home/vagrant/python-designateclient<br />
:* pip install -r requirements.txt -r test-requirements.txt<br />
:* python setup.py develop<br />
===== Test Designate Client =====<br />
:* cd /home/vagrant<br />
:* source openrc.admin<br />
:* designate --debug server-list<br />
<br />
=== Exercise the Designate API ===<br />
=====Test API locally on VM: =====<br />
:* curl http://localhost:9001<br />
=====Test API from External Client (e.g. Google Chrome HTTP Client):=====<br />
:* http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* killall designate-api <br />
* killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
*PowerDNS was used as the backend rather than BIND as it is better tested as of now. <br />
*A single node was used so that it is easier to control and easier for newbies to install.</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=51287Designate/Atlanta/Workshop 12014-05-05T20:48:09Z<p>Eankutse: </p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#:*vagrant up<br />
# Log into the VM<br />
#:* vagrant ssh<br />
# Install Designate and its dependencies<br />
#:* cd /home/vagrant/designate<br />
#:* apt-get -y build-dep python-lxml<br />
#:* pip install -r requirements.txt -r test-requirements.txt<br />
#:* python setup.py develop<br />
# Make copies of designate config files from templates<br />
#:* cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#:* ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Copy over config file with pre-set values to designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/designate.conf.wkshp )<br />
#:* cp /home/vagrant/designate.conf.wkshp ./designate.conf<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#:* mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#:* mkdir /home/vagrant/designate/log<br />
==== Verify the DNS server (PowerDNS) config ====<br />
Verify 'gmysql-dbname='''pdns'''' in /etc/powerdns/pdns.d/pdns.local.gmysql<br />
:* cat /etc/powerdns/pdns.d/pdns.local.gmysql<br />
<br />
==== Verify PowerDNS is running on port 53 ====<br />
:* netstat -tnlp (look for '''pdns_server-in''')<br />
<br />
==== Test PowerDNS ====<br />
:* dig @localhost openstack.com (You should get some response with status:SERVFAIL)<br />
<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
:* mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
:* designate-manage database init<br />
:* designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
(Database already exists. Just init and sync)<br />
:* designate-manage powerdns init<br />
:* designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
:* designate-central &<br />
<br />
==== Start the Designate API Service ====<br />
:* designate-api &<br />
<br />
==== Check services are up ====<br />
:* ps aux | grep designate<br />
<br />
==== Setup the Designate Keystone service and endpoints ====<br />
First set user 'admin' particulars then create service and endpoint<br />
:* source /home/vagrant/openrc.admin <br />
:* keystone service-create --name designate --type dns --description "Designate Service"<br />
:* keystone endpoint-create --service designate --publicurl http://127.0.0.1:9001/v1 --adminurl http://127.0.0.1:9001/v1 --internalurl http://127.0.0.1:9001/v1<br />
<br />
=== Install Designate Client ===<br />
:* cd /home/vagrant/python-designateclient<br />
:* pip install -r requirements.txt -r test-requirements.txt<br />
:* python setup.py develop<br />
===== Test Designate Client =====<br />
:* cd /home/vagrant<br />
:* source openrc.admin<br />
:* designate --debug server-list<br />
<br />
=== Exercise the Designate API ===<br />
Test API locally on VM: <br />
:* curl http://localhost:9001<br />
Test API from External Client (e.g. Google Chrome HTTP Client):<br />
:* http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* killall designate-api <br />
* killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
*PowerDNS was used as the backend rather than BIND as it is better tested as of now. <br />
*A single node was used so that it is easier to control and easier for newbies to install.</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=51285Designate/Atlanta/Workshop 12014-05-05T20:47:14Z<p>Eankutse: </p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#:*vagrant up<br />
# Log into the VM<br />
#:* vagrant ssh<br />
# Install Designate and its dependencies<br />
#:* cd /home/vagrant/designate<br />
#:* apt-get -y build-dep python-lxml<br />
#:* pip install -r requirements.txt -r test-requirements.txt<br />
#:* python setup.py develop<br />
# Make copies of designate config files from templates<br />
#:* cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#:* ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Copy over config file with pre-set values to designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/designate.conf.wkshp )<br />
#:* cp /home/vagrant/designate.conf.wkshp ./designate.conf<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#:* mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#:* mkdir /home/vagrant/designate/log<br />
==== Verify the DNS server (PowerDNS) config ====<br />
Verify 'gmysql-dbname='''pdns'''' in /etc/powerdns/pdns.d/pdns.local.gmysql<br />
:* cat /etc/powerdns/pdns.d/pdns.local.gmysql<br />
<br />
==== Verify PowerDNS is running on port 53 ====<br />
:* netstat -tnlp (look for '''pdns_server-in''')<br />
<br />
==== Test PowerDNS ====<br />
:* dig @localhost openstack.com (You should get some response with status:SERVFAIL)<br />
<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
:* mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
:* designate-manage database init<br />
:* designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
(Database already exists. Just init and sync)<br />
:* designate-manage powerdns init<br />
:* designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
:* designate-central &<br />
<br />
==== Start the Designate API Service ====<br />
:* designate-api &<br />
<br />
==== Check services are up ====<br />
:* ps aux | grep designate<br />
<br />
==== Setup the Designate Keystone service and endpoints ====<br />
First set user 'admin' particulars then create service and endpoint<br />
:* source /home/vagrant/openrc.admin <br />
:* keystone service-create --name designate --type dns --description "Designate Service"<br />
:* keystone endpoint-create --service designate --publicurl http://127.0.0.1:9001/v1 --adminurl http://127.0.0.1:9001/v1 --internalurl http://127.0.0.1:9001/v1<br />
<br />
=== Install Designate Client ===<br />
:* cd /home/vagrant/python-designateclient<br />
:* pip install -r requirements.txt -r test-requirements.txt<br />
:* python setup.py develop<br />
===== Test Designate Client =====<br />
:* cd /home/vagrant<br />
:* source openrc.admin<br />
:* designate --debug server-list<br />
<br />
=== Exercise the Designate API ===<br />
Test API locally on VM: <br />
:* curl http://localhost:9001<br />
Test API from External Client (e.g. Google Chrome HTTP Client):<br />
:* http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* killall designate-api <br />
* killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
PowerDNS was used as the backend rather than BIND as it is better tested as of now. <br />
A single node was used so that it is easier to control and easier for newbies to install.</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=51284Designate/Atlanta/Workshop 12014-05-05T20:44:57Z<p>Eankutse: /* Install Designate */</p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#:*vagrant up<br />
# Log into the VM<br />
#:* vagrant ssh<br />
# Install Designate and its dependencies<br />
#:* cd /home/vagrant/designate<br />
#:* apt-get -y build-dep python-lxml<br />
#:* pip install -r requirements.txt -r test-requirements.txt<br />
#:* python setup.py develop<br />
# Make copies of designate config files from templates<br />
#:* cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#:* ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Copy over config file with pre-set values to designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/designate.conf.wkshp )<br />
#:* cp /home/vagrant/designate.conf.wkshp ./designate.conf<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#:* mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#:* mkdir /home/vagrant/designate/log<br />
==== Verify the DNS server (PowerDNS) config ====<br />
Verify 'gmysql-dbname='''pdns'''' in /etc/powerdns/pdns.d/pdns.local.gmysql<br />
:* cat /etc/powerdns/pdns.d/pdns.local.gmysql<br />
<br />
==== Verify PowerDNS is running on port 53 ====<br />
:* netstat -tnlp (look for '''pdns_server-in''')<br />
<br />
==== Test PowerDNS ====<br />
:* dig @localhost openstack.com (You should get some response with status:SERVFAIL)<br />
<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
:* mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
:* designate-manage database init<br />
:* designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
(Database already exists. Just init and sync)<br />
:* designate-manage powerdns init<br />
:* designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
:* designate-central &<br />
<br />
==== Start the Designate API Service ====<br />
:* designate-api &<br />
<br />
==== Check services are up ====<br />
:* ps aux | grep designate<br />
<br />
==== Setup the Designate Keystone service and endpoints ====<br />
First set user 'admin' particulars then create service and endpoint<br />
:* source /home/vagrant/openrc.admin <br />
:* keystone service-create --name designate --type dns --description "Designate Service"<br />
:* keystone endpoint-create --service designate --publicurl http://127.0.0.1:9001/v1 --adminurl http://127.0.0.1:9001/v1 --internalurl http://127.0.0.1:9001/v1<br />
<br />
=== Install Designate Client ===<br />
:* cd /home/vagrant/python-designateclient<br />
:* pip install -r requirements.txt -r test-requirements.txt<br />
:* python setup.py develop<br />
===== Test Designate Client =====<br />
:* cd /home/vagrant<br />
:* source openrc.admin<br />
:* designate --debug server-list<br />
<br />
=== Exercise the Designate API ===<br />
Test API locally on VM: <br />
:* curl http://localhost:9001<br />
Test API from External Client (e.g. Google Chrome HTTP Client):<br />
:* http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* killall designate-api <br />
* killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
<br />
PowerDNS was used as the backend rather than BIND as it is better 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.</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=51280Designate/Atlanta/Workshop 12014-05-05T20:39:23Z<p>Eankutse: </p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#:*vagrant up<br />
# Log into the VM<br />
#:* vagrant ssh<br />
# Install Designate and its dependencies<br />
#:* cd /home/vagrant/designate<br />
#:* apt-get -y build-dep python-lxml<br />
#:* pip install -r requirements.txt -r test-requirements.txt<br />
#:* python setup.py develop<br />
# Copy sample designate files and edit<br />
#:* cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#:* ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Now Edit designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/designate.conf.wkshp )<br />
#:* cp /home/vagrant/designate.conf.wkshp ./designate.conf<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#:* mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#:* mkdir /home/vagrant/designate/log<br />
==== Verify the DNS server (PowerDNS) config ====<br />
Verify 'gmysql-dbname='''pdns'''' in /etc/powerdns/pdns.d/pdns.local.gmysql<br />
:* cat /etc/powerdns/pdns.d/pdns.local.gmysql<br />
<br />
==== Verify PowerDNS is running on port 53 ====<br />
:* netstat -tnlp (look for '''pdns_server-in''')<br />
<br />
==== Test PowerDNS ====<br />
:* dig @localhost openstack.com (You should get some response with status:SERVFAIL)<br />
<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
:* mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
:* designate-manage database init<br />
:* designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
(Database already exists. Just init and sync)<br />
:* designate-manage powerdns init<br />
:* designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
:* designate-central &<br />
<br />
==== Start the Designate API Service ====<br />
:* designate-api &<br />
<br />
==== Check services are up ====<br />
:* ps aux | grep designate<br />
<br />
==== Setup the Designate Keystone service and endpoints ====<br />
First set user 'admin' particulars then create service and endpoint<br />
:* source /home/vagrant/openrc.admin <br />
:* keystone service-create --name designate --type dns --description "Designate Service"<br />
:* keystone endpoint-create --service designate --publicurl http://127.0.0.1:9001/v1 --adminurl http://127.0.0.1:9001/v1 --internalurl http://127.0.0.1:9001/v1<br />
<br />
=== Install Designate Client ===<br />
:* cd /home/vagrant/python-designateclient<br />
:* pip install -r requirements.txt -r test-requirements.txt<br />
:* python setup.py develop<br />
===== Test Designate Client =====<br />
:* cd /home/vagrant<br />
:* source openrc.admin<br />
:* designate --debug server-list<br />
<br />
=== Exercise the Designate API ===<br />
Test API locally on VM: <br />
:* curl http://localhost:9001<br />
Test API from External Client (e.g. Google Chrome HTTP Client):<br />
:* http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* killall designate-api <br />
* killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
<br />
PowerDNS was used as the backend rather than BIND as it is better 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.</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=51278Designate/Atlanta/Workshop 12014-05-05T20:36:19Z<p>Eankutse: </p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#:*vagrant up<br />
# Log into the VM<br />
#:* vagrant ssh<br />
# Install Designate and its dependencies<br />
#:* cd /home/vagrant/designate<br />
#:* apt-get -y build-dep python-lxml<br />
#:* pip install -r requirements.txt -r test-requirements.txt<br />
#:* python setup.py develop<br />
# Copy sample designate files and edit<br />
#:* cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#:* ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Now Edit designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/designate.conf.wkshp )<br />
#:* cp /home/vagrant/designate.conf.wkshp ./designate.conf<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#:* mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#:* mkdir /home/vagrant/designate/log<br />
==== Verify the DNS server (PowerDNS) config ====<br />
Verify 'gmysql-dbname='''pdns'''' in /etc/powerdns/pdns.d/pdns.local.gmysql<br />
:* cat /etc/powerdns/pdns.d/pdns.local.gmysql<br />
<br />
==== Verify PowerDNS is running on port 53 ====<br />
:* netstat -tnlp (look for '''pdns_server-in''')<br />
<br />
==== Test PowerDNS ====<br />
:* dig @localhost openstack.com (You should get some response with status:SERVFAIL)<br />
<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
:* mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
:* designate-manage database init<br />
:* designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
(Database already exists. Just init and sync)<br />
:* designate-manage powerdns init<br />
:* designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
:* designate-central &<br />
<br />
==== Start the Designate API Service ====<br />
:* designate-api &<br />
<br />
==== Check services are up ====<br />
:* ps aux | grep designate<br />
<br />
==== Setup the Designate Keystone service and endpoints ====<br />
First set user 'admin' particulars then create service and endpoint<br />
:* source /home/vagrant/openrc.admin <br />
:* keystone service-create --name designate --type dns --description "Designate Service"<br />
:* keystone endpoint-create --service designate --publicurl http://127.0.0.1:9001/v1 --adminurl http://127.0.0.1:9001/v1 --internalurl http://127.0.0.1:9001/v1<br />
<br />
=== Install Designate Client ===<br />
:* cd /home/vagrant/python-designateclient<br />
:* pip install -r requirements.txt -r test-requirements.txt<br />
:* python setup.py develop<br />
===== Test Designate Client =====<br />
:* cd /home/vagrant<br />
:* source openrc.admin<br />
:* designate --debug server-list<br />
<br />
=== Exercise the Designate API ===<br />
Test API locally on VM: <br />
:* curl http://localhost:9001<br />
Test API from External Client (e.g. Google Chrome HTTP Client):<br />
:* http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* killall designate-api <br />
* killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=51271Designate/Atlanta/Workshop 12014-05-05T20:27:48Z<p>Eankutse: </p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#:*vagrant up<br />
# Log into the VM<br />
#:* vagrant ssh<br />
# Install Designate and its dependencies<br />
#:* cd /home/vagrant/designate<br />
#:* apt-get -y build-dep python-lxml<br />
#:* pip install -r requirements.txt -r test-requirements.txt<br />
#:* python setup.py develop<br />
# Copy sample designate files and edit<br />
#:* cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#:* ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Now Edit designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/designate.conf.wkshp )<br />
#:* cp /home/vagrant/designate.conf.wkshp ./designate.conf<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#:* mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#:* mkdir /home/vagrant/designate/log<br />
==== Verify the DNS server (PowerDNS) config ====<br />
Verify 'gmysql-dbname='''pdns'''' in /etc/powerdns/pdns.d/pdns.local.gmysql<br />
* cat /etc/powerdns/pdns.d/pdns.local.gmysql<br />
<br />
==== Verify PowerDNS is running on port 53 ====<br />
* netstat -tnlp (look for '''pdns_server-in''')<br />
<br />
==== Test PowerDNS ====<br />
* dig @localhost openstack.com (You should get some response with status:SERVFAIL)<br />
<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* designate-manage database init<br />
* designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
(Database already exists. Just init and sync)<br />
* designate-manage powerdns init<br />
* designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* designate-central &<br />
<br />
==== Start the Designate API Service ====<br />
* designate-api &<br />
<br />
==== Check services are up ====<br />
* ps aux | grep designate<br />
<br />
==== Setup the Designate Keystone service and endpoints ====<br />
* source /home/vagrant/openrc.admin (set user 'admin' particulars)<br />
* keystone service-create --name designate --type dns --description "Designate Service"<br />
* keystone endpoint-create --service designate --publicurl http://127.0.0.1:9001/v1 --adminurl http://127.0.0.1:9001/v1 --internalurl http://127.0.0.1:9001/v1<br />
<br />
=== Install Designate Client ===<br />
* cd /home/vagrant/python-designateclient<br />
* pip install -r requirements.txt -r test-requirements.txt<br />
* python setup.py develop<br />
===== Test Designate Client =====<br />
* cd /home/vagrant<br />
* source openrc.admin<br />
* designate --debug server-list<br />
<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* killall designate-api <br />
* killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=51266Designate/Atlanta/Workshop 12014-05-05T20:03:11Z<p>Eankutse: /* Configure the DNS server (PowerDNS) */</p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd /home/vagrant/designate<br />
#: $ apt-get -y build-dep python-lxml<br />
#: $ pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Now Edit designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/designate.conf.wkshp )<br />
#: $ cp /home/vagrant/designate.conf.wkshp ./designate.conf<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /home/vagrant/designate/log<br />
==== Verify the DNS server (PowerDNS) config ====<br />
Verify 'gmysql-dbname='''pdns'''' in /etc/powerdns/pdns.d/pdns.local.gmysql<br />
* $ cat /etc/powerdns/pdns.d/pdns.local.gmysql<br />
<br />
==== Verify PowerDNS is running on port 53 ====<br />
* $ netstat -tnlp (look for '''pdns_server-in''')<br />
<br />
==== Test PowerDNS ====<br />
* $ dig @localhost openstack.com (You should get some response with status:SERVFAIL)<br />
<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
(Database already exists. Just init and sync)<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central &<br />
<br />
==== Start the Designate API Service ====<br />
* $ designate-api &<br />
<br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
<br />
==== Setup the Designate Keystone service and endpoints ====<br />
* $ keystone service-create --name designate --type dns --description "Designate Service"<br />
* $ keystone endpoint-create --service designate --publicurl http://127.0.0.1:9001/v1 --adminurl http://127.0.0.1:9001/v1 --internalurl http://127.0.0.1:9001/v1<br />
<br />
=== Install Designate Client ===<br />
* $ cd /home/vagrant/python-designateclient<br />
* $ pip install -r requirements.txt -r test-requirements.txt<br />
* $ python setup.py develop<br />
===== Test Designate Client =====<br />
*$ cd /home/vagrant<br />
*$ source openrc.admin<br />
*$ designate --debug server-list<br />
<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=51265Designate/Atlanta/Workshop 12014-05-05T19:57:03Z<p>Eankutse: /* Configure the DNS server (PowerDNS) */</p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd /home/vagrant/designate<br />
#: $ apt-get -y build-dep python-lxml<br />
#: $ pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Now Edit designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/designate.conf.wkshp )<br />
#: $ cp /home/vagrant/designate.conf.wkshp ./designate.conf<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /home/vagrant/designate/log<br />
==== Configure the DNS server (PowerDNS) ====<br />
Verify 'gmysql-dbname='''pdns'''' in /etc/powerdns/pdns.d/pdns.local.gmysql<br />
* $ cat /etc/powerdns/pdns.d/pdns.local.gmysql<br />
<br />
==== Verify PowerDNS is running on port 53 ====<br />
* $ netstat -tnlp (look for '''pdns_server-in''')<br />
<br />
==== Test PowerDNS ====<br />
* $ dig @localhost openstack.com (You should get some response with status:SERVFAIL)<br />
<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
(Database already exists. Just init and sync)<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central &<br />
<br />
==== Start the Designate API Service ====<br />
* $ designate-api &<br />
<br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
<br />
==== Setup the Designate Keystone service and endpoints ====<br />
* $ keystone service-create --name designate --type dns --description "Designate Service"<br />
* $ keystone endpoint-create --service designate --publicurl http://127.0.0.1:9001/v1 --adminurl http://127.0.0.1:9001/v1 --internalurl http://127.0.0.1:9001/v1<br />
<br />
=== Install Designate Client ===<br />
* $ cd /home/vagrant/python-designateclient<br />
* $ pip install -r requirements.txt -r test-requirements.txt<br />
* $ python setup.py develop<br />
===== Test Designate Client =====<br />
*$ cd /home/vagrant<br />
*$ source openrc.admin<br />
*$ designate --debug server-list<br />
<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=51264Designate/Atlanta/Workshop 12014-05-05T19:55:32Z<p>Eankutse: /* Re-Start PowerDNS */</p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd /home/vagrant/designate<br />
#: $ apt-get -y build-dep python-lxml<br />
#: $ pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Now Edit designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/designate.conf.wkshp )<br />
#: $ cp /home/vagrant/designate.conf.wkshp ./designate.conf<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /home/vagrant/designate/log<br />
==== Configure the DNS server (PowerDNS) ====<br />
In /etc/powerdns/pdns.d/pdns.local.gmysql, verify (set) 'gmysql-dbname='''pdns''''<br />
* $ cat /etc/powerdns/pdns.d/pdns.local.gmysql<br />
<br />
==== Verify PowerDNS is running on port 53 ====<br />
* $ netstat -tnlp (look for '''pdns_server-in''')<br />
<br />
==== Test PowerDNS ====<br />
* $ dig @localhost openstack.com (You should get some response with status:SERVFAIL)<br />
<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
(Database already exists. Just init and sync)<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central &<br />
<br />
==== Start the Designate API Service ====<br />
* $ designate-api &<br />
<br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
<br />
==== Setup the Designate Keystone service and endpoints ====<br />
* $ keystone service-create --name designate --type dns --description "Designate Service"<br />
* $ keystone endpoint-create --service designate --publicurl http://127.0.0.1:9001/v1 --adminurl http://127.0.0.1:9001/v1 --internalurl http://127.0.0.1:9001/v1<br />
<br />
=== Install Designate Client ===<br />
* $ cd /home/vagrant/python-designateclient<br />
* $ pip install -r requirements.txt -r test-requirements.txt<br />
* $ python setup.py develop<br />
===== Test Designate Client =====<br />
*$ cd /home/vagrant<br />
*$ source openrc.admin<br />
*$ designate --debug server-list<br />
<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=51263Designate/Atlanta/Workshop 12014-05-05T19:54:49Z<p>Eankutse: /* Configure the DNS server (PowerDNS) */</p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd /home/vagrant/designate<br />
#: $ apt-get -y build-dep python-lxml<br />
#: $ pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Now Edit designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/designate.conf.wkshp )<br />
#: $ cp /home/vagrant/designate.conf.wkshp ./designate.conf<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /home/vagrant/designate/log<br />
==== Configure the DNS server (PowerDNS) ====<br />
In /etc/powerdns/pdns.d/pdns.local.gmysql, verify (set) 'gmysql-dbname='''pdns''''<br />
* $ cat /etc/powerdns/pdns.d/pdns.local.gmysql<br />
<br />
==== Re-Start PowerDNS ====<br />
* $ service pdns restart<br />
==== Verify PowerDNS is running on port 53 ====<br />
* $ netstat -tnlp (look for '''pdns_server-in''')<br />
<br />
==== Test PowerDNS ====<br />
* $ dig @localhost openstack.com (You should get some response with status:SERVFAIL)<br />
<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
(Database already exists. Just init and sync)<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central &<br />
<br />
==== Start the Designate API Service ====<br />
* $ designate-api &<br />
<br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
<br />
==== Setup the Designate Keystone service and endpoints ====<br />
* $ keystone service-create --name designate --type dns --description "Designate Service"<br />
* $ keystone endpoint-create --service designate --publicurl http://127.0.0.1:9001/v1 --adminurl http://127.0.0.1:9001/v1 --internalurl http://127.0.0.1:9001/v1<br />
<br />
=== Install Designate Client ===<br />
* $ cd /home/vagrant/python-designateclient<br />
* $ pip install -r requirements.txt -r test-requirements.txt<br />
* $ python setup.py develop<br />
===== Test Designate Client =====<br />
*$ cd /home/vagrant<br />
*$ source openrc.admin<br />
*$ designate --debug server-list<br />
<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=50822Designate/Atlanta/Workshop 12014-05-01T17:31:59Z<p>Eankutse: </p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd /home/vagrant/designate<br />
#: $ apt-get -y build-dep python-lxml<br />
#: $ pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Now Edit designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/designate.conf.wkshp )<br />
#: $ cp /home/vagrant/designate.conf.wkshp ./designate.conf<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /home/vagrant/designate/log<br />
==== Configure the DNS server (PowerDNS) ====<br />
In /etc/powerdns/pdns.d/pdns.local.gmysql, verify (set) 'gmysql-dbname='''pdns''''<br />
* $ vi /etc/powerdns/pdns.d/pdns.local.gmysql<br />
==== Re-Start PowerDNS ====<br />
* $ service pdns restart<br />
==== Verify PowerDNS is running on port 53 ====<br />
* $ netstat -tnlp (look for '''pdns_server-in''')<br />
<br />
==== Test PowerDNS ====<br />
* $ dig @localhost openstack.com (You should get some response with status:SERVFAIL)<br />
<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
(Database already exists. Just init and sync)<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central&<br />
==== Start the Designate API Service ====<br />
* $ designate-api&<br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
<br />
==== Setup the Designate Keystone service and endpoints ====<br />
* $ keystone service-create --name designate --type dns --description "Designate Service"<br />
* $ keystone endpoint-create --service designate --publicurl http://127.0.0.1:9001/v1 --adminurl http://127.0.0.1:9001/v1 --internalurl http://127.0.0.1:9001/v1<br />
<br />
=== Install Designate Client ===<br />
* $ cd /home/vagrant/python-designateclient<br />
* $ pip install -r requirements.txt -r test-requirements.txt<br />
* $ python setup.py develop<br />
===== Test Designate Client =====<br />
*$ cd /home/vagrant<br />
*$ source openrc.admin<br />
*$ designate --debug server-list<br />
<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=50817Designate/Atlanta/Workshop 12014-05-01T17:07:01Z<p>Eankutse: /* Re-Start PowerDNS */</p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd /home/vagrant/designate<br />
#: $ apt-get -y build-dep python-lxml<br />
#: $ pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Now Edit designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/designate.conf.wkshp )<br />
#: $ cp /home/vagrant/designate.conf.wkshp ./designate.conf<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /home/vagrant/designate/log<br />
==== Configure the DNS server (PowerDNS) ====<br />
In /etc/powerdns/pdns.d/pdns.local.gmysql, verify (set) 'gmysql-dbname='''pdns''''<br />
* $ vi /etc/powerdns/pdns.d/pdns.local.gmysql<br />
==== Re-Start PowerDNS ====<br />
* $ service pdns restart<br />
==== Verify PowerDNS is running on port 53 ====<br />
* $ netstat -tnlp (look for '''pdns_server-in''')<br />
<br />
==== Test PowerDNS ====<br />
* $ dig @localhost openstack.com (You should get some response with status:SERVFAIL)<br />
<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
(Database already exists. Just init and sync)<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central&<br />
==== Start the Designate API Service ====<br />
* $ designate-api&<br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
<br />
=== Install Designate Client ===<br />
* $ cd /home/vagrant/python-designateclient<br />
* $ pip install -r requirements.txt -r test-requirements.txt<br />
* $ python setup.py develop<br />
<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=50816Designate/Atlanta/Workshop 12014-05-01T17:01:41Z<p>Eankutse: </p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd /home/vagrant/designate<br />
#: $ apt-get -y build-dep python-lxml<br />
#: $ pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Now Edit designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/designate.conf.wkshp )<br />
#: $ cp /home/vagrant/designate.conf.wkshp ./designate.conf<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /home/vagrant/designate/log<br />
==== Configure the DNS server (PowerDNS) ====<br />
In /etc/powerdns/pdns.d/pdns.local.gmysql, verify (set) 'gmysql-dbname='''pdns''''<br />
* $ vi /etc/powerdns/pdns.d/pdns.local.gmysql<br />
==== Re-Start PowerDNS ====<br />
* $ service pdns restart<br />
<br />
==== Test PowerDNS ====<br />
* $ dig @localhost openstack.com (You should get some response with status:SERVFAIL)<br />
<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
(Database already exists. Just init and sync)<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central&<br />
==== Start the Designate API Service ====<br />
* $ designate-api&<br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
<br />
=== Install Designate Client ===<br />
* $ cd /home/vagrant/python-designateclient<br />
* $ pip install -r requirements.txt -r test-requirements.txt<br />
* $ python setup.py develop<br />
<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=50808Designate/Atlanta/Workshop 12014-05-01T16:00:08Z<p>Eankutse: </p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd /home/vagrant/designate<br />
#: $ apt-get -y build-dep python-lxml<br />
#: $ pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Now Edit designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/designate.conf.wkshp )<br />
#: $ cp /home/vagrant/designate.conf.wkshp ./designate.conf<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /home/vagrant/designate/log<br />
==== Configure the DNS server (PowerDNS) ====<br />
In /etc/powerdns/pdns.d/pdns.local.gmysql, verify (set) 'gmysql-dbname='''pdns''''<br />
* $ vi /etc/powerdns/pdns.d/pdns.local.gmysql<br />
==== Re-Start PowerDNS ====<br />
* $ service pdns restart<br />
<br />
==== Test PowerDNS ====<br />
* $ dig @localhost openstack.com (You should get some response with status:SERVFAIL)<br />
<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
* $ mysql -e 'CREATE DATABASE `pdns` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central&<br />
==== Start the Designate API Service ====<br />
* $ designate-api&<br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
<br />
=== Install Designate Client ===<br />
* $ cd /home/vagrant/python-designateclient<br />
* $ pip install -r requirements.txt -r test-requirements.txt<br />
* $ python setup.py develop<br />
<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=50806Designate/Atlanta/Workshop 12014-05-01T15:58:45Z<p>Eankutse: /* Re-Start PowerDNS */</p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd /home/vagrant/designate<br />
#: $ apt-get -y build-dep python-lxml<br />
#: $ pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Now Edit designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/designate.conf.wkshp )<br />
#: $ cp /home/vagrant/designate.conf.wkshp ./designate.conf<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /home/vagrant/designate/log<br />
==== Configure the DNS server (PowerDNS) ====<br />
In /etc/powerdns/pdns.d/pdns.local.gmysql, verify (set) 'gmysql-dbname='''pdns''''<br />
* $ vi /etc/powerdns/pdns.d/pdns.local.gmysql<br />
==== Re-Start PowerDNS ====<br />
* $ service pdns restart<br />
==== Test PowerDNS ====<br />
* $ dig @localhost openstack.com (You should get some response with status:SERVFAIL)<br />
<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
* $ mysql -e 'CREATE DATABASE `pdns` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central&<br />
==== Start the Designate API Service ====<br />
* $ designate-api&<br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
<br />
=== Install Designate Client ===<br />
* $ cd /home/vagrant/python-designateclient<br />
* $ pip install -r requirements.txt -r test-requirements.txt<br />
* $ python setup.py develop<br />
<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=50802Designate/Atlanta/Workshop 12014-05-01T15:47:52Z<p>Eankutse: /* Install Designate */</p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd /home/vagrant/designate<br />
#: $ apt-get -y build-dep python-lxml<br />
#: $ pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Now Edit designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/designate.conf.wkshp )<br />
#: $ cp /home/vagrant/designate.conf.wkshp ./designate.conf<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /home/vagrant/designate/log<br />
==== Configure the DNS server (PowerDNS) ====<br />
In /etc/powerdns/pdns.d/pdns.local.gmysql, verify (set) 'gmysql-dbname='''pdns''''<br />
* $ vi /etc/powerdns/pdns.d/pdns.local.gmysql<br />
==== Re-Start PowerDNS ====<br />
* $ service pdns restart<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
* $ mysql -e 'CREATE DATABASE `pdns` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central&<br />
==== Start the Designate API Service ====<br />
* $ designate-api&<br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
<br />
=== Install Designate Client ===<br />
* $ cd /home/vagrant/python-designateclient<br />
* $ pip install -r requirements.txt -r test-requirements.txt<br />
* $ python setup.py develop<br />
<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=50801Designate/Atlanta/Workshop 12014-05-01T15:45:20Z<p>Eankutse: </p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd /home/vagrant/designate<br />
#: $ apt-get build-dep python-lxml. Respond "Y" to question (or just hit enter)<br />
#: $ pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Now Edit designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/designate.conf.wkshp )<br />
#: $ cp /home/vagrant/designate.conf.wkshp ./designate.conf<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /home/vagrant/designate/log<br />
==== Configure the DNS server (PowerDNS) ====<br />
In /etc/powerdns/pdns.d/pdns.local.gmysql, verify (set) 'gmysql-dbname='''pdns''''<br />
* $ vi /etc/powerdns/pdns.d/pdns.local.gmysql<br />
==== Re-Start PowerDNS ====<br />
* $ service pdns restart<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
* $ mysql -e 'CREATE DATABASE `pdns` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central&<br />
==== Start the Designate API Service ====<br />
* $ designate-api&<br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
<br />
=== Install Designate Client ===<br />
* $ cd /home/vagrant/python-designateclient<br />
* $ pip install -r requirements.txt -r test-requirements.txt<br />
* $ python setup.py develop<br />
<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=50778Designate/Atlanta/Workshop 12014-05-01T14:07:29Z<p>Eankutse: /* Install Designate */</p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd /home/vagrant/designate<br />
#: $ apt-get build-dep python-lxml. Respond "Y" to question (or just hit enter)<br />
#: $ pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Now Edit designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/designate.conf.wkshp )<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /home/vagrant/designate/log<br />
==== Configure the DNS server (PowerDNS) ====<br />
In /etc/powerdns/pdns.d/pdns.local.gmysql, verify (set) 'gmysql-dbname='''pdns''''<br />
* $ vi /etc/powerdns/pdns.d/pdns.local.gmysql<br />
==== Re-Start PowerDNS ====<br />
* $ service pdns restart<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
* $ mysql -e 'CREATE DATABASE `pdns` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central&<br />
==== Start the Designate API Service ====<br />
* $ designate-api&<br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
<br />
=== Install Designate Client ===<br />
* $ cd /home/vagrant/python-designateclient<br />
* $ pip install -r requirements.txt -r test-requirements.txt<br />
* $ python setup.py develop<br />
<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=50775Designate/Atlanta/Workshop 12014-05-01T13:25:50Z<p>Eankutse: </p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd /home/vagrant/designate<br />
#: $ apt-get build-dep python-lxml. Respond "Y" to question (or just hit enter)<br />
#: $ pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Now Edit designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/dedesignate.conf.wkshp )<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /home/vagrant/designate/log<br />
==== Configure the DNS server (PowerDNS) ====<br />
In /etc/powerdns/pdns.d/pdns.local.gmysql, verify (set) 'gmysql-dbname='''pdns''''<br />
* $ vi /etc/powerdns/pdns.d/pdns.local.gmysql<br />
==== Re-Start PowerDNS ====<br />
* $ service pdns restart<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
* $ mysql -e 'CREATE DATABASE `pdns` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central&<br />
==== Start the Designate API Service ====<br />
* $ designate-api&<br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
<br />
=== Install Designate Client ===<br />
* $ cd /home/vagrant/python-designateclient<br />
* $ pip install -r requirements.txt -r test-requirements.txt<br />
* $ python setup.py develop<br />
<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=50728Designate/Atlanta/Workshop 12014-04-30T21:33:58Z<p>Eankutse: </p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd /home/vagrant/designate<br />
#: $ apt-get build-dep python-lxml. Respond "Y" to question (or just hit enter)<br />
#: $ pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Now Edit designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/designate/etc/designate/designate.conf.wksp )<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /home/vagrant/designate/log<br />
==== Configure the DNS server (PowerDNS) ====<br />
In /etc/powerdns/pdns.d/pdns.local.gmysql, verify (set) 'gmysql-dbname='''pdns''''<br />
* $ vi /etc/powerdns/pdns.d/pdns.local.gmysql<br />
==== Re-Start PowerDNS ====<br />
* $ service pdns restart<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
* $ mysql -e 'CREATE DATABASE `pdns` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central&<br />
==== Start the Designate API Service ====<br />
* $ designate-api&<br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
<br />
=== Install Designate Client ===<br />
* $ cd /home/vagrant/python-designateclient<br />
* $ pip install -r requirements.txt -r test-requirements.txt<br />
* $ python setup.py develop<br />
<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=50727Designate/Atlanta/Workshop 12014-04-30T21:24:37Z<p>Eankutse: </p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd /home/vagrant/designate<br />
#: $ apt-get build-dep python-lxml. Respond "Y" to question (or just hit enter)<br />
#: $ pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Now Edit designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/designate/etc/designate/designate.conf.wksp )<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /home/vagrant/designate/log<br />
==== Configure the DNS server (PowerDNS) ====<br />
:In /etc/powerdns/pdns.d/pdns.local.gmysql, verify (set) 'gmysql-dbname=pdns'<br />
* $ vi /etc/powerdns/pdns.d/pdns.local.gmysql<br />
==== Re-Start PowerDNS ====<br />
* $ service pdns restart<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
* $ mysql -e 'CREATE DATABASE `pdns` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central&<br />
==== Start the Designate API Service ====<br />
* $ designate-api&<br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
<br />
=== Install Designate Client ===<br />
* $ cd /home/vagrant/python-designateclient<br />
* $ pip install -r requirements.txt -r test-requirements.txt<br />
* $ python setup.py develop<br />
<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=50726Designate/Atlanta/Workshop 12014-04-30T21:15:59Z<p>Eankutse: </p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions ==<br />
<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd /home/vagrant/designate<br />
#: $ apt-get build-dep python-lxml. Respond "Y" to question (or just hit enter)<br />
#: $ pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Now Edit designate.conf<br />
#: (Replace contents of designate.conf with contents of file /home/vagrant/designate/etc/designate/designate.conf.wksp )<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /home/vagrant/designate/log<br />
==== Install the DNS server (PowerDNS) ====<br />
: Suppress default behavior of PowerDNS package creating it's own database, then install<br />
* $ echo "pdns-backend-mysql pdns-backend-mysql/dbconfig-install boolean false" | debconf-set-selections<br />
* $ DEBIAN_FRONTEND=noninteractive apt-get install pdns-server pdns-backend-mysql<br />
: (Hit <Enter> or enter 'Y' to question 'Do you want to continue [Y/n]?')<br />
:Verify that file /etc/powerdns/pdns.d/pdns.local.gmysql contains 'gmysql-dbname=pdns':<br />
* $ cat /etc/powerdns/pdns.d/pdns.local.gmysql<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
* $ mysql -e 'CREATE DATABASE `pdns` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central&<br />
==== Start the Designate API Service ====<br />
* $ designate-api&<br />
==== Start PowerDNS ====<br />
* $ service pdns start <br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
<br />
=== Install Designate Client ===<br />
* $ cd /home/vagrant/python-designateclient<br />
* $ pip install -r requirements.txt -r test-requirements.txt<br />
* $ python setup.py develop<br />
<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=50713Designate/Atlanta/Workshop 12014-04-30T20:00:06Z<p>Eankutse: </p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions - DRAFT ==<br />
=== Verify VM and Openstack core components are installed and correctly configured ===<br />
# verify python environment is installed<br />
#:$ which pip<br />
#:''/usr/bin/pip''<br />
#:$ which virtualenv<br />
#:''/usr/bin/virtualenv''<br />
# verify RabbitMQ Server is installed and configured correctly:<br />
# verify Glance Service is installed and configured correctly:<br />
# verify Glance Client is installed and configured correctly:<br />
# verify Keystone Service is installed and configured correctly:<br />
# verify Keystone Client is installed and configured correctly:<br />
# verify Neutron Service is installed and configured correctly:<br />
# verify Neutron Client is installed and configured correctly:<br />
# verify Nova Service is installed and configured correctly:<br />
# verify Nova Client is installed and configured correctly:<br />
# verify MySQL is installed: <cmd><br />
# verify MySQl is configured correctly:<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd /home/vagrant/designate<br />
#: $ apt-get build-dep python-lxml. Respond "Y" to question (or just hit enter)<br />
#: $ pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Now Edit designate.conf<br />
#: (See section below for config values - "Designate Workshop Configuration")<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /home/vagrant/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /home/vagrant/designate/log<br />
==== Install the DNS server (PowerDNS) ====<br />
: Suppress default behavior of PowerDNS package creating it's own database, then install<br />
* $ echo "pdns-backend-mysql pdns-backend-mysql/dbconfig-install boolean false" | debconf-set-selections<br />
* $ DEBIAN_FRONTEND=noninteractive apt-get install pdns-server pdns-backend-mysql<br />
: (Hit <Enter> or enter 'Y' to question 'Do you want to continue [Y/n]?')<br />
:Verify that file /etc/powerdns/pdns.d/pdns.local.gmysql contains 'gmysql-dbname=pdns':<br />
* $ cat /etc/powerdns/pdns.d/pdns.local.gmysql<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
* $ mysql -e 'CREATE DATABASE `pdns` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central&<br />
==== Start the Designate API Service ====<br />
* $ designate-api&<br />
==== Start PowerDNS ====<br />
* $ service pdns start <br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
=== [Sample] Designate Workshop Configuration ===<br />
[DEFAULT]<br />
:Show more verbose log output (sets INFO log level output)<br />
:'''verbose = True'''<br />
:Show debugging output in logs (sets DEBUG log level output)<br />
:'''debug = True'''<br />
:Top-level directory for maintaining designate's state<br />
:'''state_path = /home/vagrant/designate'''<br />
:Log directory<br />
:'''logdir = /home/vagrant/designate/log'''<br />
:Driver used for issuing notifications<br />
:'''notification_driver = designate.openstack.common.notifier.rpc_notifier'''<br />
:Notification Topics<br />
:'''notification_topics = notifications'''<br />
:'''root_helper = sudo'''<br />
[service:central]<br />
:Driver used for backend communication (e.g. fake, rpc, bind9, powerdns)<br />
:'''backend_driver = powerdns'''<br />
:Maximum domain name length<br />
:'''max_domain_name_len = 255'''<br />
:Maximum record name length<br />
:'''max_record_name_len = 255'''<br />
:[service:api]<br />
:Address to bind the API server<br />
:'''api_host = 0.0.0.0'''<br />
:Port the bind the API server to<br />
:'''api_port = 9001'''<br />
:Authentication strategy to use - can be either "noauth" or "keystone"<br />
:'''auth_strategy = keystone'''<br />
:Enable Version 1 API<br />
:'''enable_api_v1 = True'''<br />
<br />
:Enable Version 2 API (experimental)<br />
:'''enable_api_v2 = True'''<br />
<br />
:Show the pecan HTML based debug interface (v2 only)<br />
:'''pecan_debug = False'''<br />
<br />
:Enabled API Version 1 extensions<br />
:'''enabled_extensions_v1 = diagnostics, quotas, reports, sync, touch'''<br />
:[service:agent]<br />
:Driver used for backend communication (e.g. bind9, powerdns)<br />
:'''backend_driver = powerdns'''<br />
<br />
:SQLAlchemy Storage<br />
:[storage:sqlalchemy]<br />
:Database connection string - to configure options for a given implementation<br />
:like sqlalchemy or other see below<br />
:'''database_connection = mysql://root@127.0.0.1:3306/designate'''<br />
:'''connection_debug = 100'''<br />
:'''connection_trace = False'''<br />
:'''sqlite_synchronous = True'''<br />
:'''idle_timeout = 3600'''<br />
:'''max_retries = 10'''<br />
:'''retry_interval = 10'''<br />
<br />
:PowerDNS Backend<br />
:[backend:powerdns]<br />
:'''database_connection = mysql://root@127.0.0.1:3306/pdns'''<br />
:'''connection_debug = 100'''<br />
:'''connection_trace = False'''<br />
:'''sqlite_synchronous = True'''<br />
:'''idle_timeout = 3600'''<br />
:'''max_retries = 10'''<br />
:'''retry_interval = 10'''<br />
<br />
<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=50515Designate/Atlanta/Workshop 12014-04-29T20:46:31Z<p>Eankutse: /* Other Designate Workshop Command Lines */</p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions - DRAFT ==<br />
=== Verify VM and Openstack core components are installed and correctly configured ===<br />
# verify python environment is installed<br />
#:$ which pip<br />
#:''/usr/bin/pip''<br />
#:$ which virtualenv<br />
#:''/usr/bin/virtualenv''<br />
# verify RabbitMQ Server is installed and configured correctly:<br />
# verify Glance Service is installed and configured correctly:<br />
# verify Glance Client is installed and configured correctly:<br />
# verify Keystone Service is installed and configured correctly:<br />
# verify Keystone Client is installed and configured correctly:<br />
# verify Neutron Service is installed and configured correctly:<br />
# verify Neutron Client is installed and configured correctly:<br />
# verify Nova Service is installed and configured correctly:<br />
# verify Nova Client is installed and configured correctly:<br />
# verify MySQL is installed: <cmd><br />
# verify MySQl is configured correctly:<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd /home/vagrant/designate<br />
#: $ apt-get build-dep python-lxml. Respond "Y" to question (or just hit enter)<br />
#: $ pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Now Edit designate.conf<br />
#: (See section below for config values - "Designate Workshop Configuration")<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /home/vagrant/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /home/vagrant/designate/log<br />
==== Install the DNS server (PowerDNS) ====<br />
: Suppress default behavior of PowerDNS package creating it's own database, then install<br />
* $ echo "pdns-backend-mysql pdns-backend-mysql/dbconfig-install boolean false" | debconf-set-selections<br />
* $ DEBIAN_FRONTEND=noninteractive apt-get install pdns-server pdns-backend-mysql<br />
: (Hit <Enter> or enter 'Y' to question 'Do you want to continue [Y/n]?')<br />
:Verify the 'gmysql-dbname' entry in /etc/powerdns/pdns.d/pdns.local.gmysql points to appropriate database as ff:<br />
* gmysql-dbname=pdns <br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
* $ mysql -e 'CREATE DATABASE `pdns` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central&<br />
==== Start the Designate API Service ====<br />
* $ designate-api&<br />
==== Start PowerDNS ====<br />
* $ service pdns start <br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
=== [Sample] Designate Workshop Configuration ===<br />
[DEFAULT]<br />
:Show more verbose log output (sets INFO log level output)<br />
:'''verbose = True'''<br />
:Show debugging output in logs (sets DEBUG log level output)<br />
:'''debug = True'''<br />
:Top-level directory for maintaining designate's state<br />
:'''state_path = /home/vagrant/designate'''<br />
:Log directory<br />
:'''logdir = /home/vagrant/designate/log'''<br />
:Driver used for issuing notifications<br />
:'''notification_driver = designate.openstack.common.notifier.rpc_notifier'''<br />
:Notification Topics<br />
:'''notification_topics = notifications'''<br />
:'''root_helper = sudo'''<br />
[service:central]<br />
:Driver used for backend communication (e.g. fake, rpc, bind9, powerdns)<br />
:'''backend_driver = powerdns'''<br />
:Maximum domain name length<br />
:'''max_domain_name_len = 255'''<br />
:Maximum record name length<br />
:'''max_record_name_len = 255'''<br />
:[service:api]<br />
:Address to bind the API server<br />
:'''api_host = 0.0.0.0'''<br />
:Port the bind the API server to<br />
:'''api_port = 9001'''<br />
:Authentication strategy to use - can be either "noauth" or "keystone"<br />
:'''auth_strategy = keystone'''<br />
:Enable Version 1 API<br />
:'''enable_api_v1 = True'''<br />
<br />
:Enable Version 2 API (experimental)<br />
:'''enable_api_v2 = True'''<br />
<br />
:Show the pecan HTML based debug interface (v2 only)<br />
:'''pecan_debug = False'''<br />
<br />
:Enabled API Version 1 extensions<br />
:'''enabled_extensions_v1 = diagnostics, quotas, reports, sync, touch'''<br />
:[service:agent]<br />
:Driver used for backend communication (e.g. bind9, powerdns)<br />
:'''backend_driver = powerdns'''<br />
<br />
:SQLAlchemy Storage<br />
:[storage:sqlalchemy]<br />
:Database connection string - to configure options for a given implementation<br />
:like sqlalchemy or other see below<br />
:'''database_connection = mysql://root@127.0.0.1:3306/designate'''<br />
:'''connection_debug = 100'''<br />
:'''connection_trace = False'''<br />
:'''sqlite_synchronous = True'''<br />
:'''idle_timeout = 3600'''<br />
:'''max_retries = 10'''<br />
:'''retry_interval = 10'''<br />
<br />
:PowerDNS Backend<br />
:[backend:powerdns]<br />
:'''database_connection = mysql://root@127.0.0.1:3306/pdns'''<br />
:'''connection_debug = 100'''<br />
:'''connection_trace = False'''<br />
:'''sqlite_synchronous = True'''<br />
:'''idle_timeout = 3600'''<br />
:'''max_retries = 10'''<br />
:'''retry_interval = 10'''<br />
<br />
<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for traces on services such as PowerDNS)<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=50506Designate/Atlanta/Workshop 12014-04-29T19:49:12Z<p>Eankutse: /* Other Designate Workshop Command Lines */</p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions - DRAFT ==<br />
=== Verify VM and Openstack core components are installed and correctly configured ===<br />
# verify python environment is installed<br />
#:$ which pip<br />
#:''/usr/bin/pip''<br />
#:$ which virtualenv<br />
#:''/usr/bin/virtualenv''<br />
# verify RabbitMQ Server is installed and configured correctly:<br />
# verify Glance Service is installed and configured correctly:<br />
# verify Glance Client is installed and configured correctly:<br />
# verify Keystone Service is installed and configured correctly:<br />
# verify Keystone Client is installed and configured correctly:<br />
# verify Neutron Service is installed and configured correctly:<br />
# verify Neutron Client is installed and configured correctly:<br />
# verify Nova Service is installed and configured correctly:<br />
# verify Nova Client is installed and configured correctly:<br />
# verify MySQL is installed: <cmd><br />
# verify MySQl is configured correctly:<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd /home/vagrant/designate<br />
#: $ apt-get build-dep python-lxml. Respond "Y" to question (or just hit enter)<br />
#: $ pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Now Edit designate.conf<br />
#: (See section below for config values - "Designate Workshop Configuration")<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /home/vagrant/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /home/vagrant/designate/log<br />
==== Install the DNS server (PowerDNS) ====<br />
: Suppress default behavior of PowerDNS package creating it's own database, then install<br />
* $ echo "pdns-backend-mysql pdns-backend-mysql/dbconfig-install boolean false" | debconf-set-selections<br />
* $ DEBIAN_FRONTEND=noninteractive apt-get install pdns-server pdns-backend-mysql<br />
: (Hit <Enter> or enter 'Y' to question 'Do you want to continue [Y/n]?')<br />
:Verify the 'gmysql-dbname' entry in /etc/powerdns/pdns.d/pdns.local.gmysql points to appropriate database as ff:<br />
* gmysql-dbname=pdns <br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
* $ mysql -e 'CREATE DATABASE `pdns` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central&<br />
==== Start the Designate API Service ====<br />
* $ designate-api&<br />
==== Start PowerDNS ====<br />
* $ service pdns start <br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
=== [Sample] Designate Workshop Configuration ===<br />
[DEFAULT]<br />
:Show more verbose log output (sets INFO log level output)<br />
:'''verbose = True'''<br />
:Show debugging output in logs (sets DEBUG log level output)<br />
:'''debug = True'''<br />
:Top-level directory for maintaining designate's state<br />
:'''state_path = /home/vagrant/designate'''<br />
:Log directory<br />
:'''logdir = /home/vagrant/designate/log'''<br />
:Driver used for issuing notifications<br />
:'''notification_driver = designate.openstack.common.notifier.rpc_notifier'''<br />
:Notification Topics<br />
:'''notification_topics = notifications'''<br />
:'''root_helper = sudo'''<br />
[service:central]<br />
:Driver used for backend communication (e.g. fake, rpc, bind9, powerdns)<br />
:'''backend_driver = powerdns'''<br />
:Maximum domain name length<br />
:'''max_domain_name_len = 255'''<br />
:Maximum record name length<br />
:'''max_record_name_len = 255'''<br />
:[service:api]<br />
:Address to bind the API server<br />
:'''api_host = 0.0.0.0'''<br />
:Port the bind the API server to<br />
:'''api_port = 9001'''<br />
:Authentication strategy to use - can be either "noauth" or "keystone"<br />
:'''auth_strategy = keystone'''<br />
:Enable Version 1 API<br />
:'''enable_api_v1 = True'''<br />
<br />
:Enable Version 2 API (experimental)<br />
:'''enable_api_v2 = True'''<br />
<br />
:Show the pecan HTML based debug interface (v2 only)<br />
:'''pecan_debug = False'''<br />
<br />
:Enabled API Version 1 extensions<br />
:'''enabled_extensions_v1 = diagnostics, quotas, reports, sync, touch'''<br />
:[service:agent]<br />
:Driver used for backend communication (e.g. bind9, powerdns)<br />
:'''backend_driver = powerdns'''<br />
<br />
:SQLAlchemy Storage<br />
:[storage:sqlalchemy]<br />
:Database connection string - to configure options for a given implementation<br />
:like sqlalchemy or other see below<br />
:'''database_connection = mysql://root@127.0.0.1:3306/designate'''<br />
:'''connection_debug = 100'''<br />
:'''connection_trace = False'''<br />
:'''sqlite_synchronous = True'''<br />
:'''idle_timeout = 3600'''<br />
:'''max_retries = 10'''<br />
:'''retry_interval = 10'''<br />
<br />
:PowerDNS Backend<br />
:[backend:powerdns]<br />
:'''database_connection = mysql://root@127.0.0.1:3306/pdns'''<br />
:'''connection_debug = 100'''<br />
:'''connection_trace = False'''<br />
:'''sqlite_synchronous = True'''<br />
:'''idle_timeout = 3600'''<br />
:'''max_retries = 10'''<br />
:'''retry_interval = 10'''<br />
<br />
<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
:Also, other log files exist in '''/var/log''' (e.g syslog for PowerDNS traces)<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=50493Designate/Atlanta/Workshop 12014-04-29T19:12:37Z<p>Eankutse: </p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions - DRAFT ==<br />
=== Verify VM and Openstack core components are installed and correctly configured ===<br />
# verify python environment is installed<br />
#:$ which pip<br />
#:''/usr/bin/pip''<br />
#:$ which virtualenv<br />
#:''/usr/bin/virtualenv''<br />
# verify RabbitMQ Server is installed and configured correctly:<br />
# verify Glance Service is installed and configured correctly:<br />
# verify Glance Client is installed and configured correctly:<br />
# verify Keystone Service is installed and configured correctly:<br />
# verify Keystone Client is installed and configured correctly:<br />
# verify Neutron Service is installed and configured correctly:<br />
# verify Neutron Client is installed and configured correctly:<br />
# verify Nova Service is installed and configured correctly:<br />
# verify Nova Client is installed and configured correctly:<br />
# verify MySQL is installed: <cmd><br />
# verify MySQl is configured correctly:<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd /home/vagrant/designate<br />
#: $ apt-get build-dep python-lxml. Respond "Y" to question (or just hit enter)<br />
#: $ pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Now Edit designate.conf<br />
#: (See section below for config values - "Designate Workshop Configuration")<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /home/vagrant/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /home/vagrant/designate/log<br />
==== Install the DNS server (PowerDNS) ====<br />
: Suppress default behavior of PowerDNS package creating it's own database, then install<br />
* $ echo "pdns-backend-mysql pdns-backend-mysql/dbconfig-install boolean false" | debconf-set-selections<br />
* $ DEBIAN_FRONTEND=noninteractive apt-get install pdns-server pdns-backend-mysql<br />
: (Hit <Enter> or enter 'Y' to question 'Do you want to continue [Y/n]?')<br />
:Verify the 'gmysql-dbname' entry in /etc/powerdns/pdns.d/pdns.local.gmysql points to appropriate database as ff:<br />
* gmysql-dbname=pdns <br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
* $ mysql -e 'CREATE DATABASE `pdns` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central&<br />
==== Start the Designate API Service ====<br />
* $ designate-api&<br />
==== Start PowerDNS ====<br />
* $ service pdns start <br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
=== [Sample] Designate Workshop Configuration ===<br />
[DEFAULT]<br />
:Show more verbose log output (sets INFO log level output)<br />
:'''verbose = True'''<br />
:Show debugging output in logs (sets DEBUG log level output)<br />
:'''debug = True'''<br />
:Top-level directory for maintaining designate's state<br />
:'''state_path = /home/vagrant/designate'''<br />
:Log directory<br />
:'''logdir = /home/vagrant/designate/log'''<br />
:Driver used for issuing notifications<br />
:'''notification_driver = designate.openstack.common.notifier.rpc_notifier'''<br />
:Notification Topics<br />
:'''notification_topics = notifications'''<br />
:'''root_helper = sudo'''<br />
[service:central]<br />
:Driver used for backend communication (e.g. fake, rpc, bind9, powerdns)<br />
:'''backend_driver = powerdns'''<br />
:Maximum domain name length<br />
:'''max_domain_name_len = 255'''<br />
:Maximum record name length<br />
:'''max_record_name_len = 255'''<br />
:[service:api]<br />
:Address to bind the API server<br />
:'''api_host = 0.0.0.0'''<br />
:Port the bind the API server to<br />
:'''api_port = 9001'''<br />
:Authentication strategy to use - can be either "noauth" or "keystone"<br />
:'''auth_strategy = keystone'''<br />
:Enable Version 1 API<br />
:'''enable_api_v1 = True'''<br />
<br />
:Enable Version 2 API (experimental)<br />
:'''enable_api_v2 = True'''<br />
<br />
:Show the pecan HTML based debug interface (v2 only)<br />
:'''pecan_debug = False'''<br />
<br />
:Enabled API Version 1 extensions<br />
:'''enabled_extensions_v1 = diagnostics, quotas, reports, sync, touch'''<br />
:[service:agent]<br />
:Driver used for backend communication (e.g. bind9, powerdns)<br />
:'''backend_driver = powerdns'''<br />
<br />
:SQLAlchemy Storage<br />
:[storage:sqlalchemy]<br />
:Database connection string - to configure options for a given implementation<br />
:like sqlalchemy or other see below<br />
:'''database_connection = mysql://root@127.0.0.1:3306/designate'''<br />
:'''connection_debug = 100'''<br />
:'''connection_trace = False'''<br />
:'''sqlite_synchronous = True'''<br />
:'''idle_timeout = 3600'''<br />
:'''max_retries = 10'''<br />
:'''retry_interval = 10'''<br />
<br />
:PowerDNS Backend<br />
:[backend:powerdns]<br />
:'''database_connection = mysql://root@127.0.0.1:3306/pdns'''<br />
:'''connection_debug = 100'''<br />
:'''connection_trace = False'''<br />
:'''sqlite_synchronous = True'''<br />
:'''idle_timeout = 3600'''<br />
:'''max_retries = 10'''<br />
:'''retry_interval = 10'''<br />
<br />
<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=50490Designate/Atlanta/Workshop 12014-04-29T19:10:09Z<p>Eankutse: </p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions - DRAFT ==<br />
=== Verify VM and Openstack core components are installed and correctly configured ===<br />
# verify python environment is installed<br />
#:$ which pip<br />
#:''/usr/bin/pip''<br />
#:$ which virtualenv<br />
#:''/usr/bin/virtualenv''<br />
# verify RabbitMQ Server is installed and configured correctly:<br />
# verify Glance Service is installed and configured correctly:<br />
# verify Glance Client is installed and configured correctly:<br />
# verify Keystone Service is installed and configured correctly:<br />
# verify Keystone Client is installed and configured correctly:<br />
# verify Neutron Service is installed and configured correctly:<br />
# verify Neutron Client is installed and configured correctly:<br />
# verify Nova Service is installed and configured correctly:<br />
# verify Nova Client is installed and configured correctly:<br />
# verify MySQL is installed: <cmd><br />
# verify MySQl is configured correctly:<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd /home/vagrant/designate<br />
#: $ apt-get build-dep python-lxml. Respond "Y" to question (or just hit enter)<br />
#: $ pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Now Edit designate.conf<br />
#: (See section below for config values - "Designate Workshop Configuration")<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /home/vagrant/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /home/vagrant/designate/log<br />
==== Install the DNS server (PowerDNS) ====<br />
: Suppress default behavior of PowerDNS package creating it's own database, then install<br />
* $ echo "pdns-backend-mysql pdns-backend-mysql/dbconfig-install boolean false" | debconf-set-selections<br />
* $ DEBIAN_FRONTEND=noninteractive apt-get install pdns-server pdns-backend-mysql<br />
: (Hit <Enter> or enter 'Y' to question 'Do you want to continue [Y/n]?')<br />
:Verify the 'gmysql-dbname' entry in /etc/powerdns/pdns.d/pdns.local.gmysql points to appropriate database as ff:<br />
* gmysql-dbname=pdns <br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
* $ mysql -e 'CREATE DATABASE `pdns` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central&<br />
==== Start the Designate API Service ====<br />
* $ designate-api&<br />
==== Start PowerDNS ====<br />
* $ service pdns start <br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
=== [Sample] Designate Workshop Configuration ===<br />
[DEFAULT]<br />
:General Configuration<br />
:Show more verbose log output (sets INFO log level output)<br />
:'''verbose = True'''<br />
:Show debugging output in logs (sets DEBUG log level output)<br />
:'''debug = True'''<br />
:Top-level directory for maintaining designate's state<br />
:'''state_path = /home/vagrant/designate'''<br />
:Log directory<br />
:'''logdir = /home/vagrant/designate/log'''<br />
:Driver used for issuing notifications<br />
:'''notification_driver = designate.openstack.common.notifier.rpc_notifier'''<br />
:Notification Topics<br />
:'''notification_topics = notifications'''<br />
:'''root_helper = sudo'''<br />
[service:central]<br />
:Driver used for backend communication (e.g. fake, rpc, bind9, powerdns)<br />
:'''backend_driver = powerdns'''<br />
:Maximum domain name length<br />
:'''max_domain_name_len = 255'''<br />
:Maximum record name length<br />
:'''max_record_name_len = 255'''<br />
:[service:api]<br />
:Address to bind the API server<br />
:'''api_host = 0.0.0.0'''<br />
:Port the bind the API server to<br />
:'''api_port = 9001'''<br />
:Authentication strategy to use - can be either "noauth" or "keystone"<br />
:'''auth_strategy = keystone'''<br />
:Enable Version 1 API<br />
:'''enable_api_v1 = True'''<br />
<br />
:Enable Version 2 API (experimental)<br />
:'''enable_api_v2 = True'''<br />
<br />
:Show the pecan HTML based debug interface (v2 only)<br />
:'''pecan_debug = False'''<br />
<br />
:Enabled API Version 1 extensions<br />
'''enabled_extensions_v1 = diagnostics, quotas, reports, sync, touch'''<br />
:[service:agent]<br />
:Driver used for backend communication (e.g. bind9, powerdns)<br />
:'''backend_driver = powerdns'''<br />
<br />
:SQLAlchemy Storage<br />
:[storage:sqlalchemy]<br />
:Database connection string - to configure options for a given implementation<br />
:like sqlalchemy or other see below<br />
:'''database_connection = mysql://root@127.0.0.1:3306/designate'''<br />
:'''connection_debug = 100'''<br />
:'''connection_trace = False'''<br />
:'''sqlite_synchronous = True'''<br />
:'''idle_timeout = 3600'''<br />
:'''max_retries = 10'''<br />
:'''retry_interval = 10'''<br />
<br />
:PowerDNS Backend<br />
:[backend:powerdns]<br />
:'''database_connection = mysql://root@127.0.0.1:3306/pdns'''<br />
:'''connection_debug = 100'''<br />
:'''connection_trace = False'''<br />
:'''sqlite_synchronous = True'''<br />
:'''idle_timeout = 3600'''<br />
:'''max_retries = 10'''<br />
:'''retry_interval = 10'''<br />
<br />
<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=50483Designate/Atlanta/Workshop 12014-04-29T18:48:20Z<p>Eankutse: </p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions - DRAFT ==<br />
=== Verify VM and Openstack core components are installed and correctly configured ===<br />
# verify python environment is installed<br />
#:$ which pip<br />
#:''/usr/bin/pip''<br />
#:$ which virtualenv<br />
#:''/usr/bin/virtualenv''<br />
# verify RabbitMQ Server is installed and configured correctly:<br />
# verify Glance Service is installed and configured correctly:<br />
# verify Glance Client is installed and configured correctly:<br />
# verify Keystone Service is installed and configured correctly:<br />
# verify Keystone Client is installed and configured correctly:<br />
# verify Neutron Service is installed and configured correctly:<br />
# verify Neutron Client is installed and configured correctly:<br />
# verify Nova Service is installed and configured correctly:<br />
# verify Nova Client is installed and configured correctly:<br />
# verify MySQL is installed: <cmd><br />
# verify MySQl is configured correctly:<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd /home/vagrant/designate<br />
#: $ apt-get build-dep python-lxml. Respond "Y" to question (or just hit enter)<br />
#: $ pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Now Edit designate.conf<br />
#: (See section below for config values - "Designate Workshop Configuration")<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /home/vagrant/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /home/vagrant/designate/log<br />
==== Install the DNS server (PowerDNS) ====<br />
: Suppress default behavior of PowerDNS package creating it's own database, then install<br />
* $ echo "pdns-backend-mysql pdns-backend-mysql/dbconfig-install boolean false" | debconf-set-selections<br />
* $ DEBIAN_FRONTEND=noninteractive apt-get install pdns-server pdns-backend-mysql<br />
: (Hit <Enter> or enter 'Y' to question 'Do you want to continue [Y/n]?')<br />
:Verify the 'gmysql-dbname' entry in /etc/powerdns/pdns.d/pdns.local.gmysql points to appropriate database as ff:<br />
* gmysql-dbname=pdns <br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
* $ mysql -e 'CREATE DATABASE `pdns` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central&<br />
==== Start the Designate API Service ====<br />
* $ designate-api&<br />
==== Start PowerDNS ====<br />
* $ service pdns start <br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
=== [Sample] Designate Workshop Configuration ===<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=50469Designate/Atlanta/Workshop 12014-04-29T17:55:07Z<p>Eankutse: </p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions - DRAFT ==<br />
=== Verify VM and Openstack core components are installed and correctly configured ===<br />
# verify python environment is installed<br />
#:$ which pip<br />
#:''/usr/bin/pip''<br />
#:$ which virtualenv<br />
#:''/usr/bin/virtualenv''<br />
# verify RabbitMQ Server is installed and configured correctly:<br />
# verify Glance Service is installed and configured correctly:<br />
# verify Glance Client is installed and configured correctly:<br />
# verify Keystone Service is installed and configured correctly:<br />
# verify Keystone Client is installed and configured correctly:<br />
# verify Neutron Service is installed and configured correctly:<br />
# verify Neutron Client is installed and configured correctly:<br />
# verify Nova Service is installed and configured correctly:<br />
# verify Nova Client is installed and configured correctly:<br />
# verify MySQL is installed: <cmd><br />
# verify MySQl is configured correctly:<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd /home/vagrant/designate<br />
#: $ apt-get build-dep python-lxml. Respond "Y" to question (or just hit enter)<br />
#: $ [sudo] pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Now Edit designate.conf<br />
#: (See section below for config values - "Other Designate Workshop Command Lines")<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /var/log/designate<br />
==== Install the DNS server (PowerDNS) ====<br />
: Suppress default behavior of PowerDNS package creating it's own database, then install<br />
* $ echo "pdns-backend-mysql pdns-backend-mysql/dbconfig-install boolean false" | debconf-set-selections<br />
* $ DEBIAN_FRONTEND=noninteractive apt-get install pdns-server pdns-backend-mysql<br />
: (Hit <Enter> or enter 'Y' to question 'Do you want to continue [Y/n]?')<br />
:Change the 'gmysql-dbname' entry in /etc/powerdns/pdns.d/pdns.local.gmysql to point to appropriate location as ff:<br />
* gmysql-dbname=/var/lib/designate/pdns<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
* $ mysql -e 'CREATE DATABASE `pdns` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central&<br />
==== Start the Designate API Service ====<br />
* $ designate-api&<br />
==== Start PowerDNS ====<br />
* $ service pdns start <br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=50335Designate/Atlanta/Workshop 12014-04-28T20:58:53Z<p>Eankutse: /* Install Designate */</p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions - DRAFT ==<br />
=== Verify VM and Openstack core components are installed and correctly configured ===<br />
# verify python environment is installed<br />
#:$ which pip<br />
#:''/usr/bin/pip''<br />
#:$ which virtualenv<br />
#:''/usr/bin/virtualenv''<br />
# verify RabbitMQ Server is installed and configured correctly:<br />
# verify Glance Service is installed and configured correctly:<br />
# verify Glance Client is installed and configured correctly:<br />
# verify Keystone Service is installed and configured correctly:<br />
# verify Keystone Client is installed and configured correctly:<br />
# verify Neutron Service is installed and configured correctly:<br />
# verify Neutron Client is installed and configured correctly:<br />
# verify Nova Service is installed and configured correctly:<br />
# verify Nova Client is installed and configured correctly:<br />
# verify MySQL is installed: <cmd><br />
# verify MySQl is configured correctly:<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd /home/vagrant/designate<br />
#: $ apt-get build-dep python-lxml. Respond "Y" to question (or just hit enter)<br />
#: $ [sudo] pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
# Now Edit designate.conf<br />
#: (See section below for config values - "Other Designate Workshop Command Lines")<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /var/log/designate<br />
==== Install the DNS server (PowerDNS) ====<br />
: Suppress default behavior of PowerDNS package creating it's own database, then install <br />
* $ echo 'set pdns-backend-mysql/dbconfig-install false' | debconf-communicate<br />
* $ DEBIAN_FRONTEND=noninteractive apt-get install pdns-server pdns-backend-mysql<br />
: (Hit <Enter> or enter 'Y' to question 'Do you want to continue [Y/n]?')<br />
:Change the 'gmysql-dbname' entry in /etc/powerdns/pdns.d/pdns.local.gmysql to point to appropriate location as ff:<br />
* gmysql-dbname=/var/lib/designate/pdns<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
* $ mysql -e 'CREATE DATABASE `pdns` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central&<br />
==== Start the Designate API Service ====<br />
* $ designate-api&<br />
==== Start PowerDNS ====<br />
* $ service pdns start <br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=50328Designate/Atlanta/Workshop 12014-04-28T19:54:01Z<p>Eankutse: /* The Designate database */</p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions - DRAFT ==<br />
=== Verify VM and Openstack core components are installed and correctly configured ===<br />
# verify python environment is installed<br />
#:$ which pip<br />
#:''/usr/bin/pip''<br />
#:$ which virtualenv<br />
#:''/usr/bin/virtualenv''<br />
# verify RabbitMQ Server is installed and configured correctly:<br />
# verify Glance Service is installed and configured correctly:<br />
# verify Glance Client is installed and configured correctly:<br />
# verify Keystone Service is installed and configured correctly:<br />
# verify Keystone Client is installed and configured correctly:<br />
# verify Neutron Service is installed and configured correctly:<br />
# verify Neutron Client is installed and configured correctly:<br />
# verify Nova Service is installed and configured correctly:<br />
# verify Nova Client is installed and configured correctly:<br />
# verify MySQL is installed: <cmd><br />
# verify MySQl is configured correctly:<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd /home/vagrant/designate<br />
#: $ apt-get build-dep python-lxml. Respond "Y" to question (or just hit enter)<br />
#: $ [sudo] pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
#: (See section below for config values - "Other Designate Workshop Command Lines")<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /var/log/designate<br />
==== Install the DNS server (PowerDNS) ====<br />
: Suppress default behavior of PowerDNS package creating it's own database, then install <br />
* $ echo 'set pdns-backend-mysql/dbconfig-install false' | debconf-communicate<br />
* $ DEBIAN_FRONTEND=noninteractive apt-get install pdns-server pdns-backend-mysql<br />
: (Hit <Enter> or enter 'Y' to question 'Do you want to continue [Y/n]?')<br />
:Change the 'gmysql-dbname' entry in /etc/powerdns/pdns.d/pdns.local.gmysql to point to appropriate location as ff:<br />
* gmysql-dbname=/var/lib/designate/pdns<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
<br />
===== The PowerDNS database =====<br />
* $ mysql -e 'CREATE DATABASE `pdns` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central&<br />
==== Start the Designate API Service ====<br />
* $ designate-api&<br />
==== Start PowerDNS ====<br />
* $ service pdns start <br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=50321Designate/Atlanta/Workshop 12014-04-28T19:18:37Z<p>Eankutse: /* Install Designate */</p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions - DRAFT ==<br />
=== Verify VM and Openstack core components are installed and correctly configured ===<br />
# verify python environment is installed<br />
#:$ which pip<br />
#:''/usr/bin/pip''<br />
#:$ which virtualenv<br />
#:''/usr/bin/virtualenv''<br />
# verify RabbitMQ Server is installed and configured correctly:<br />
# verify Glance Service is installed and configured correctly:<br />
# verify Glance Client is installed and configured correctly:<br />
# verify Keystone Service is installed and configured correctly:<br />
# verify Keystone Client is installed and configured correctly:<br />
# verify Neutron Service is installed and configured correctly:<br />
# verify Neutron Client is installed and configured correctly:<br />
# verify Nova Service is installed and configured correctly:<br />
# verify Nova Client is installed and configured correctly:<br />
# verify MySQL is installed: <cmd><br />
# verify MySQl is configured correctly:<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd /home/vagrant/designate<br />
#: $ apt-get build-dep python-lxml. Respond "Y" to question (or just hit enter)<br />
#: $ [sudo] pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
#: (See section below for config values - "Other Designate Workshop Command Lines")<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /var/log/designate<br />
==== Install the DNS server (PowerDNS) ====<br />
: Suppress default behavior of PowerDNS package creating it's own database, then install <br />
* $ echo 'set pdns-backend-mysql/dbconfig-install false' | debconf-communicate<br />
* $ DEBIAN_FRONTEND=noninteractive apt-get install pdns-server pdns-backend-mysql<br />
: (Hit <Enter> or enter 'Y' to question 'Do you want to continue [Y/n]?')<br />
:Change the 'gmysql-dbname' entry in /etc/powerdns/pdns.d/pdns.local.gmysql to point to appropriate location as ff:<br />
* gmysql-dbname=/var/lib/designate/pdns<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
===== The PowerDNS database =====<br />
* $ mysql -e 'CREATE DATABASE `pdns` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central&<br />
==== Start the Designate API Service ====<br />
* $ designate-api&<br />
==== Start PowerDNS ====<br />
* $ service pdns start <br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=50317Designate/Atlanta/Workshop 12014-04-28T19:03:34Z<p>Eankutse: </p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions - DRAFT ==<br />
=== Verify VM and Openstack core components are installed and correctly configured ===<br />
# verify python environment is installed<br />
#:$ which pip<br />
#:''/usr/bin/pip''<br />
#:$ which virtualenv<br />
#:''/usr/bin/virtualenv''<br />
# verify RabbitMQ Server is installed and configured correctly:<br />
# verify Glance Service is installed and configured correctly:<br />
# verify Glance Client is installed and configured correctly:<br />
# verify Keystone Service is installed and configured correctly:<br />
# verify Keystone Client is installed and configured correctly:<br />
# verify Neutron Service is installed and configured correctly:<br />
# verify Neutron Client is installed and configured correctly:<br />
# verify Nova Service is installed and configured correctly:<br />
# verify Nova Client is installed and configured correctly:<br />
# verify MySQL is installed: <cmd><br />
# verify MySQl is configured correctly:<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd to /home/vagrant/designate<br />
#: $ apt-get build-dep python-lxml. Respond "Y" to question (or just hit enter)<br />
#: $ [sudo] pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
#: (See section below for config values - "Other Designate Workshop Command Lines")<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /var/log/designate<br />
==== Install the DNS server (PowerDNS) ====<br />
: Suppress default behavior of PowerDNS package creating it's own database, then install <br />
* $ echo 'set pdns-backend-mysql/dbconfig-install false' | debconf-communicate<br />
* $ DEBIAN_FRONTEND=noninteractive apt-get install pdns-server pdns-backend-mysql<br />
: (Hit <Enter> or enter 'Y' to question 'Do you want to continue [Y/n]?')<br />
:Change the 'gmysql-dbname' entry in /etc/powerdns/pdns.d/pdns.local.gmysql to point to appropriate location as ff:<br />
* gmysql-dbname=/var/lib/designate/pdns<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
===== The PowerDNS database =====<br />
* $ mysql -e 'CREATE DATABASE `pdns` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central&<br />
==== Start the Designate API Service ====<br />
* $ designate-api&<br />
==== Start PowerDNS ====<br />
* $ service pdns start <br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=50294Designate/Atlanta/Workshop 12014-04-28T16:33:44Z<p>Eankutse: </p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions - DRAFT ==<br />
=== Verify VM and Openstack core components are installed and correctly configured ===<br />
# verify python environment is installed<br />
#:$ which pip<br />
#:''/usr/bin/pip''<br />
#:$ which virtualenv<br />
#:''/usr/bin/virtualenv''<br />
# verify RabbitMQ Server is installed and configured correctly:<br />
# verify Glance Service is installed and configured correctly:<br />
# verify Glance Client is installed and configured correctly:<br />
# verify Keystone Service is installed and configured correctly:<br />
# verify Keystone Client is installed and configured correctly:<br />
# verify Neutron Service is installed and configured correctly:<br />
# verify Neutron Client is installed and configured correctly:<br />
# verify Nova Service is installed and configured correctly:<br />
# verify Nova Client is installed and configured correctly:<br />
# verify MySQL is installed: <cmd><br />
# verify MySQl is configured correctly:<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd to /home/vagrant/designate<br />
#: $ apt-get build-dep python-lxml. Respond "Y" to question (or just hit enter)<br />
#: $ [sudo] pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
#: (See section below for config values - "Other Designate Workshop Command Lines")<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /var/log/designate<br />
==== Install the DNS server (PowerDNS) ====<br />
: Suppress default behavior of PowerDNS package creating it's own database, then install <br />
* $ echo 'set pdns-backend-mysql/dbconfig-install false' | debconf-communicate<br />
* $ DEBIAN_FRONTEND=noninteractive apt-get install pdns-server pdns-backend-mysql<br />
: (Hit <Enter> or enter 'Y' to question 'Do you want to continue [Y/n]?')<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
===== The PowerDNS database =====<br />
* $ mysql -e 'CREATE DATABASE `pdns` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central&<br />
==== Start the Designate API Service ====<br />
* $ designate-api&<br />
==== Start PowerDNS ====<br />
* $ service pdns start <br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=50280Designate/Atlanta/Workshop 12014-04-28T15:40:38Z<p>Eankutse: </p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions - DRAFT ==<br />
=== Verify VM and Openstack core components are installed and correctly configured ===<br />
# verify python environment is installed<br />
#:$ which pip<br />
#:''/usr/bin/pip''<br />
#:$ which virtualenv<br />
#:''/usr/bin/virtualenv''<br />
# verify RabbitMQ Server is installed and configured correctly:<br />
# verify Glance Service is installed and configured correctly:<br />
# verify Glance Client is installed and configured correctly:<br />
# verify Keystone Service is installed and configured correctly:<br />
# verify Keystone Client is installed and configured correctly:<br />
# verify Neutron Service is installed and configured correctly:<br />
# verify Neutron Client is installed and configured correctly:<br />
# verify Nova Service is installed and configured correctly:<br />
# verify Nova Client is installed and configured correctly:<br />
# verify MySQL is installed: <cmd><br />
# verify MySQl is configured correctly:<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd to /home/vagrant/designate<br />
#: $ apt-get build-dep python-lxml. Respond "Y" to question (or just hit enter)<br />
#: $ [sudo] pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
#: (See section below for config values - "Other Designate Workshop Command Lines")<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /var/log/designate<br />
==== Install the DNS server (PowerDNS) ====<br />
* $ DEBIAN_FRONTEND=noninteractive apt-get install pdns-server pdns-backend-mysql<br />
: (Hit <Enter> or enter 'Y' to question 'Do you want to continue [Y/n]?')<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
===== The PowerDNS database =====<br />
* $ mysql -e 'CREATE DATABASE `pdns` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central&<br />
==== Start the Designate API Service ====<br />
* $ designate-api&<br />
==== Start PowerDNS ====<br />
* $ service pdns start <br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=50258Designate/Atlanta/Workshop 12014-04-28T14:40:16Z<p>Eankutse: </p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions - DRAFT ==<br />
=== Verify VM and Openstack core components are installed and correctly configured ===<br />
# verify python environment is installed<br />
#:$ which pip<br />
#:''/usr/bin/pip''<br />
#:$ which virtualenv<br />
#:''/usr/bin/virtualenv''<br />
# verify RabbitMQ Server is installed and configured correctly:<br />
# verify Glance Service is installed and configured correctly:<br />
# verify Glance Client is installed and configured correctly:<br />
# verify Keystone Service is installed and configured correctly:<br />
# verify Keystone Client is installed and configured correctly:<br />
# verify Neutron Service is installed and configured correctly:<br />
# verify Neutron Client is installed and configured correctly:<br />
# verify Nova Service is installed and configured correctly:<br />
# verify Nova Client is installed and configured correctly:<br />
# verify MySQL is installed: <cmd><br />
# verify MySQl is configured correctly:<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd to /home/vagrant/designate<br />
#: $ apt-get build-dep python-lxml. Respond "Y" to question (or just hit enter)<br />
#: $ [sudo] pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
#: (See section below for config values - "Other Designate Workshop Command Lines")<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /var/log/designate<br />
==== Install the DNS server (powerDNS) ====<br />
*<br />
==== Create, Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
===== The PowerDNS database =====<br />
* $ mysql -e 'CREATE DATABASE `pdns` CHARACTER SET utf8 COLLATE utf8_general_ci;'<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central&<br />
==== Start the Designate API Service ====<br />
* $ designate-api&<br />
==== Start PowerDNS ====<br />
* $ service pdns start <br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=50042Designate/Atlanta/Workshop 12014-04-25T16:37:41Z<p>Eankutse: </p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions - DRAFT ==<br />
=== Verify VM and Openstack core components are installed and correctly configured ===<br />
# verify python environment is installed<br />
#:$ which pip<br />
#:''/usr/bin/pip''<br />
#:$ which virtualenv<br />
#:''/usr/bin/virtualenv''<br />
# verify RabbitMQ Server is installed and configured correctly:<br />
# verify Glance Service is installed and configured correctly:<br />
# verify Glance Client is installed and configured correctly:<br />
# verify Keystone Service is installed and configured correctly:<br />
# verify Keystone Client is installed and configured correctly:<br />
# verify Neutron Service is installed and configured correctly:<br />
# verify Neutron Client is installed and configured correctly:<br />
# verify Nova Service is installed and configured correctly:<br />
# verify Nova Client is installed and configured correctly:<br />
# verify MySQL is installed: <cmd><br />
# verify MySQl is configured correctly:<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd to /home/vagrant/designate<br />
#: $ apt-get build-dep python-lxml. Respond "Y" to question (or just hit enter)<br />
#: $ [sudo] pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
#: (See section below for config values - "Other Designate Workshop Command Lines")<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /var/log/designate<br />
==== Install the DNS server (powerDNS) ====<br />
*<br />
==== Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
===== The PowerDNS database =====<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Start the Designate Central Service ====<br />
* $ designate-central&<br />
==== Start the Designate API Service ====<br />
* $ designate-api&<br />
==== Start PowerDNS ====<br />
* $ service pdns start <br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=49938Designate/Atlanta/Workshop 12014-04-24T21:00:59Z<p>Eankutse: /* Exercise the Designate API */</p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions - DRAFT ==<br />
=== Verify VM and Openstack core components are installed and correctly configured ===<br />
# verify python environment is installed<br />
#:$ which pip<br />
#:''/usr/bin/pip''<br />
#:$ which virtualenv<br />
#:''/usr/bin/virtualenv''<br />
# verify RabbitMQ Server is installed and configured correctly:<br />
# verify Glance Service is installed and configured correctly:<br />
# verify Glance Client is installed and configured correctly:<br />
# verify Keystone Service is installed and configured correctly:<br />
# verify Keystone Client is installed and configured correctly:<br />
# verify Neutron Service is installed and configured correctly:<br />
# verify Neutron Client is installed and configured correctly:<br />
# verify Nova Service is installed and configured correctly:<br />
# verify Nova Client is installed and configured correctly:<br />
# verify MySQL is installed: <cmd><br />
# verify MySQl is configured correctly:<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd to /home/vagrant/designate<br />
#: $ apt-get build-dep python-lxml. Respond "Y" to question (or just hit enter)<br />
#: $ [sudo] pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
#: (See section below for config values - "Other Designate Workshop Command Lines")<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /var/log/designate<br />
==== Install the DNS server (powerDNS) ====<br />
*<br />
==== Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
===== The PowerDNS database =====<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Initialize & Start the Designate Central Service ====<br />
* $ designate-central&<br />
==== Initialize & Start the Designate API Service ====<br />
* $ designate-api&<br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
More Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutsehttps://wiki.openstack.org/w/index.php?title=Designate/Atlanta/Workshop_1&diff=49936Designate/Atlanta/Workshop 12014-04-24T20:58:58Z<p>Eankutse: </p>
<hr />
<div>= Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2014 =<br />
<br />
Designate provides DNSaaS services for OpenStack.<br />
<br />
This interactive workshop will guide attendees on how Designate can be installed with PowerDNS. For the purposes of the workshop the various designate components will be installed on a single node. Once installed it shows some of the V1 and V2 APIs for domain and record management. The workshop will conclude by using a tool like dig to retrieve the added records from the PowerDNS backend, showing a fully functional by-hand deployment.<br />
<br />
The workshop will also cover the steps for contributing to the development of Designate.<br />
<br />
Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.<br />
<br />
See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”<br />
<br />
== Designate Installation Instructions - DRAFT ==<br />
=== Verify VM and Openstack core components are installed and correctly configured ===<br />
# verify python environment is installed<br />
#:$ which pip<br />
#:''/usr/bin/pip''<br />
#:$ which virtualenv<br />
#:''/usr/bin/virtualenv''<br />
# verify RabbitMQ Server is installed and configured correctly:<br />
# verify Glance Service is installed and configured correctly:<br />
# verify Glance Client is installed and configured correctly:<br />
# verify Keystone Service is installed and configured correctly:<br />
# verify Keystone Client is installed and configured correctly:<br />
# verify Neutron Service is installed and configured correctly:<br />
# verify Neutron Client is installed and configured correctly:<br />
# verify Nova Service is installed and configured correctly:<br />
# verify Nova Client is installed and configured correctly:<br />
# verify MySQL is installed: <cmd><br />
# verify MySQl is configured correctly:<br />
=== Install Designate ===<br />
# Start the VM<br />
#: $ vagrant up<br />
# Log into the VM<br />
#: $ vagrant ssh<br />
# Be super user<br />
#: $ sudo su -<br />
# Install Designate and its dependencies<br />
#: $ cd to /home/vagrant/designate<br />
#: $ apt-get build-dep python-lxml. Respond "Y" to question (or just hit enter)<br />
#: $ [sudo] pip install -r requirements.txt -r test-requirements.txt<br />
#: $ python setup.py develop<br />
# Copy sample designate files and edit<br />
#: $ cd etc/designate (/home/vagrant/designate/etc/designate)<br />
#: $ ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done<br />
#: (See section below for config values - "Other Designate Workshop Command Lines")<br />
# Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)<br />
#: $ mkdir /var/lib/designate<br />
# Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)<br />
#: $ mkdir /var/log/designate<br />
==== Install the DNS server (powerDNS) ====<br />
*<br />
==== Initialize and sync the databases ====<br />
===== The Designate database =====<br />
* $ designate-manage database init<br />
* $ designate-manage database sync<br />
===== The PowerDNS database =====<br />
* $ designate-manage powerdns init<br />
* $ designate-manage powerdns sync<br />
==== Initialize & Start the Designate Central Service ====<br />
* $ designate-central&<br />
==== Initialize & Start the Designate API Service ====<br />
* $ designate-api&<br />
==== Check services are up ====<br />
* $ ps aux | grep designate<br />
=== Exercise the Designate API ===<br />
# Test API locally on VM: <br />
#: $ curl http://localhost:9001<br />
# Test API from External Client (e.g. Google Chrome HTTP Client):<br />
#: http://localhost:9001/v2/<br />
<br />
Sample Helpful commands below in "Other Designate Workshop Command Lines"<br />
<br />
<br />
== Other Designate Workshop Command Lines ==<br />
* $ killall designate-api <br />
* $ killall designate-central<br />
<br />
= Additional Notes on the workshop =<br />
<br />
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.<br />
<br />
= Removed =<br />
<br />
<br />
:<br />
<br />
* REST API for domain & record management<br />
* Multi-tenant<br />
* Integrated with Keystone for authentication<br />
* Framework in place to integrate with Nova and Neutron notifications (for auto-generated records)<br />
* Support for PowerDNS and Bind9 out of the box</div>Eankutse