620fc6ec97
* Add a new backend for DevStack allowing the Agent backend to be configured. * Change the agent to choose a sane port by default, it's extremely unlikely anyone is exposing the agent on port 53 intentionally. * The agent itself is not yet configured, this will come later as it involves refactoring most of the BIND non-agent backend into a lib. * Fail when the user asks for the agent backend, without also enabling the agent service. Change-Id: Iedde58f4f5a2ea89cb9da78aaec1853208af8fc9
1.6 KiB
1.6 KiB
Agent Backend
This page documents using the Pool Manager Agent backend, and it's accompanying service, designate-agent. This backend uses an extension of the DNS protocol itself to send management requests to the remote agent processes, where the requests will be actioned.
The traffic between designate-pool-manager, and designate-agent is both unauthenticated and unencrypted. Do not run this traffic over unsecured networks.
Designate Configuration
For each designate-agent running, add a target to the pools.yaml configuration file, using the following template:
sample_yaml_snippets/agent.yaml
Then update the designate pools database using the
designate-manage pool command - see designate_manage_pool for
further details on the designate-manage pool command:
$ designate-manage pool update