openstack
/
designate
Code Issues Proposed changes

Merge "Add syntax highlighting to backend docs"

This commit is contained in:
Jenkins 2016-03-10 19:12:31 +00:00 committed by Gerrit Code Review
parent c9ef4c9f07 267369b12a
commit 3bc91f6f35
3 changed files with 21 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/source/backends/bind9.rst
View File

@ -24,7 +24,9 @@ The traffic between rndc and Bind is authenticated with a key.
Designate Configuration
-----------------------
Example configuration required for Bind9 operation. One section for each pool target::
Example configuration required for Bind9 operation. One section for each pool target
.. code-block:: ini
[pool_target:f26e0b32-736f-4f0a-831b-039a415c481e]
options = rndc_host: 192.168.27.100, rndc_port: 953, rndc_config_file: /etc/bind/rndc.conf, rndc_key_file: /etc/bind/rndc.key, port: 53, host: 192.168.27.100, clean_zonefile: false
@ -40,11 +42,15 @@ Bind9 Configuration
Ensure Bind can access the /etc/bind/rndc.conf and /etc/bind/rndc.key files and
receive rndc traffic from Pool Manager.
Enable rndc addzone/delzone functionality by editing named.conf.options or named.conf and add this line under options::
Enable rndc addzone/delzone functionality by editing named.conf.options or named.conf and add this line under options
.. code-block:: c
allow-new-zones yes;
Example configuration of /etc/bind/rndc.key::
Example configuration of /etc/bind/rndc.key
.. code-block:: c
key "rndc-key" {
algorithm hmac-md5;

3
doc/source/backends/infoblox.rst
View File

@ -69,7 +69,7 @@ Designate Backend Configuration
*Example Designate Configuration*
::
.. code-block:: ini
[pool:794ccc2c-d751-44fe-b57f-8894c9f5c842]
#Specify the API service points for each grid
@ -88,7 +88,6 @@ Designate Backend Configuration
host=172.16.98.200
port=53
[backend:infoblox]
# The values below will be used for all targets unless overridden
# in the target configuration. http_* options may only be set here,

14
doc/source/backends/powerdns.rst
View File

@ -45,10 +45,14 @@ You need to configure PowerDNS to use the MySQL backend.
1. First enable the MySQL backend:
.. code-block:: ini
launch = gmysql
2. Configure the MySQL database settings::
.. code-block:: ini
gmysql-host=<host>
gmysql-port=
gmysql-dbname=<dbname>
@ -60,14 +64,16 @@ You need to configure PowerDNS to use the MySQL backend.
.. note::
PowerDNS can connect via socket or host/port.
3. Configure the options for designate-central - specifically "connection" to point to your MySQL database::
3. Configure the options for designate-central - specifically "connection" to point to your MySQL database
.. code-block:: ini
[backend:powerdns]
connection = mysql+pymysql://<username>:<password>@<host>:<port>/<dbname>
4. Setup the database schema.
::
.. code-block:: console
$ designate-manage powerdns init
$ designate-manage powerdns sync
@ -80,7 +86,9 @@ PowerDNS deployment as hidden Master
One deployment scenario can be that the PowerDNS backend will be used as a "hidden" Master DNS for other DNS servers to consume via AXFR.
Say you have 10.0.0.1 and 10.0.0.2 as slaves then configure the backend as follows in addition to other options::
Say you have 10.0.0.1 and 10.0.0.2 as slaves then configure the backend as follows in addition to other options
.. code-block:: ini
[backend:powernds]
domain_type = MASTER