Jump to: navigation, search


Designate: Interactive Workshop - Install and Operate - Openstack Summit, May 2015

Designate provides DNSaaS services for OpenStack.

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.

The workshop will also cover the steps for contributing to the development of Designate.

Several of the Designate contributors will be on hand during the workshop to help attendees work through the deployment.

See also: "Designate: An Overview of DNSaaS for Openstack" and “Designate: Deep Dive for Operators/Deployers”

Designate Installation Instructions

Install Designate

  1. Start the VM
    • vagrant up
  2. Log into the VM
    • vagrant ssh
  3. Install Designate and its dependencies
    • cd /home/vagrant/designate
    • sudo apt-get -y build-dep python-lxml
    • sudo pip install -r requirements.txt -r test-requirements.txt
    • sudo python setup.py develop
  4. Make copies of designate config files from templates
    • cd etc/designate (/home/vagrant/designate/etc/designate)
    • ls *.sample | while read f; do cp $f $(echo $f | sed "s/.sample$//g"); done
  5. Copy over config file with pre-set values to designate.conf
    (Replace contents of designate.conf with contents of file /home/vagrant/designate.conf.wkshp )
    • cp /home/vagrant/designate.conf.wkshp ./designate.conf
  6. Create directory for maintaining designate state information (this directory was referenced by 'state_path' variable in designate.conf file)
    • sudo mkdir /var/lib/designate
  7. Create directory for maintaining designate log files (this directory was referenced by 'logdir' variable in designate.conf file)
    • sudo mkdir /home/vagrant/designate/log

Verify the DNS server (PowerDNS) config

Verify 'gmysql-dbname=pdns' in /etc/powerdns/pdns.d/pdns.local.gmysql

  • cat /etc/powerdns/pdns.d/pdns.local.gmysql

Verify PowerDNS is running on port 53

  • sudo netstat -tnlp (look for pdns_server-in)

Test PowerDNS

  • dig @localhost openstack.com (You should get some response with status:SERVFAIL)

Create, Initialize and sync the databases

The Designate database
  • mysql -e 'CREATE DATABASE `designate` CHARACTER SET utf8 COLLATE utf8_general_ci;'
  • sudo designate-manage database init
  • sudo designate-manage database sync
The PowerDNS database

(Database already exists. Just init and sync)

  • sudo designate-manage powerdns init
  • sudo designate-manage powerdns sync

Start the Designate Central Service

  • sudo designate-central &

Start the Designate API Service

  • sudo designate-api &

Check services are up

  • ps aux | grep designate

Setup the Designate Keystone service and endpoints

First set user 'admin' particulars then create service and endpoint

Install Designate Client

  • cd /home/vagrant/python-designateclient
  • sudo pip install -r requirements.txt -r test-requirements.txt
  • sudo python setup.py develop
Test Designate Client
  • cd /home/vagrant
  • source openrc.admin
  • designate --debug server-list

Exercise the Designate API

Test API locally on VM:
Test API from External Client (e.g. Google Chrome HTTP Client):

More Sample Helpful commands below in "Other Designate Workshop Command Lines"

Other Designate Workshop Command Lines

  • killall designate-api
  • killall designate-central
Also, other log files exist in /var/log (e.g syslog for traces on services such as PowerDNS)

Additional Notes on the workshop

  • PowerDNS was used as the backend rather than BIND as it is better tested as of now.
  • A single node was used so that it is easier to control and easier for newbies to install.