
The pool-manager has been deprecated since Newton and is now being removed with the Train release. Change-Id: Ib258043d492bb25e1c061d765b40885317c73804
1.6 KiB
1.6 KiB
Agent Backend
This page documents using the various Agent backends, 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 rpc traffic between designate and the 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