Removed deprecated pool-manager implementation

The pool-manager has been deprecated since Newton and
is now being removed with the Train release.

Change-Id: Ib258043d492bb25e1c061d765b40885317c73804

4 files changed, 8 insertions, 84 deletions

diff --git a/doc/source/admin/backends/agent.rst b/doc/source/admin/backends/agent.rst
index 6554e241..1a0e3056 100644
--- a/doc/source/admin/backends/agent.rst
+++ b/doc/source/admin/backends/agent.rst
@@ -16,14 +16,13 @@
 Agent Backend
 =============
 
-This page documents using the Pool Manager Agent backend, and it's accompanying
+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 traffic between `designate-pool-manager`, and `designate-agent` is both
-unauthenticated and unencrypted. Do not run this traffic over unsecured
-networks.
+The `rpc` traffic between designate and the `agent` is both unauthenticated and
+unencrypted. Do not run this traffic over unsecured networks.
 
 Designate Configuration
 -----------------------
diff --git a/doc/source/admin/backends/bind9.rst b/doc/source/admin/backends/bind9.rst
index 0dfb39a8..0b4ccc2e 100644
--- a/doc/source/admin/backends/bind9.rst
+++ b/doc/source/admin/backends/bind9.rst
@@ -18,7 +18,7 @@
 Bind9 Backend
 =============
 
-This page documents using the Pool Manager Bind 9 backend.
+This page documents using the Bind 9 backend.
 The backend uses the rndc utility to create and delete zones remotely.
 
 The traffic between rndc and Bind is authenticated with a key.
@@ -32,7 +32,7 @@ One section for each pool target
    .. literalinclude:: sample_yaml_snippets/bind.yaml
        :language: yaml
 
-The key and config files are relative to the host running Pool Manager
+The key and config files are relative to the host running Designate
 (and can be different from the hosts running Bind)
 
 Then update the pools in designate - see :ref:`designate_manage_pool`
@@ -46,7 +46,7 @@ Bind9 Configuration
 -------------------
 
 Ensure Bind can access the /etc/bind/rndc.conf and /etc/bind/rndc.key files and
-receive rndc traffic from Pool Manager.
+receive rndc traffic from Designate.
 
 Enable rndc addzone/delzone functionality by editing named.conf.options
 or named.conf and add this line under options
diff --git a/doc/source/cli/designate-manage.rst b/doc/source/cli/designate-manage.rst
index 4f8220de..ccd6dc85 100644
--- a/doc/source/cli/designate-manage.rst
+++ b/doc/source/cli/designate-manage.rst
@@ -127,27 +127,6 @@ designate optional arguments
 designate-manage pool
 =====================
 
-.. _designate_manage_pool_export_from_config:
-
-designate-manage pool export_from_config
-----------------------------------------
-
-.. code-block:: console
-
-    usage: designate-manage pool export_from_config [-h] [--file FILE]
-
-
-Export a YAML copy of a Kilo/Liberty pool config.
-
-**Optional arguments:**
-
-``-h, --help``
-  show this help message and exit
-
-``--file FILE``
-  The path to the file the yaml output should be written to
-  (Defaults to /etc/designate/pools.yaml)
-
 .. _designate_manage_pool_generate_file:
 
 designate-manage pool generate_file
@@ -243,52 +222,6 @@ Show what version of the database schema is currently in place
 ``-h, --help``
   show this help message and exit
 
-.. _designate_manage_pool_manager_cache:
-
-designate-manage pool_manager_cache
-===================================
-
-.. _designate_manage_pool_manager_cache_sync:
-
-designate-manage pool_manager_cache sync
-----------------------------------------
-
-.. code-block:: console
-
-    usage: designate-manage pool_manager_cache sync [-h] [--revision REVISION]
-
-
-Update the designate pool manager cache database schema
-
-**Optional arguments:**
-
-``-h, --help``
-  show this help message and exit
-
-``--revision REVISION``
-  The version that the designate pool manager cache database
-  should be synced to.
-  (Defaults to latest version)
-
-
-.. _designate_manage_pool_manager_cache_version:
-
-designate-manage pool_manager_cache version
--------------------------------------------
-
-.. code-block:: console
-
-    usage: designate-manage pool_manager_cache version [-h]
-
-
-Show what version of the pool manager cache database schema
-is currently in place
-
-**Optional arguments:**
-
-``-h, --help``
-  show this help message and exit
-
 .. _designate_manage_powerdns:
 
 designate-manage powerdns
@@ -316,13 +249,9 @@ Update the designate powerdns database schema
   show this help message and exit
 
 ``--revision REVISION``
-  The version that the designate pool manager cache database
-  should be synced to.
+  The version that the designate powerdns database should be synced to.
   (Defaults to latest version)
 
-
-
-
 .. _designate_manage_powerdns_version:
 
 designate-manage powerdns version
@@ -344,5 +273,3 @@ Show what version of the powerdns database schema is currently in place
 
 ``-h, --help``
   show this help message and exit
-
-
diff --git a/doc/source/install/get_started.rst b/doc/source/install/get_started.rst
index 1030b98a..9e3c0c1c 100644
--- a/doc/source/install/get_started.rst
+++ b/doc/source/install/get_started.rst
@@ -16,9 +16,7 @@ The DNS service consists of the following components:
   them to the ``designate-central`` over Remote Procedure Call (RPC).
 
 ``designate-central`` component
-  Orchestrates the creation, deletion and update of Zones and RecordSets, and
-  delegates work to ``designate-pool-manager`` for interaction with the DNS
-  servers
+  Orchestrates the creation, deletion and update of Zones and RecordSets.
 
 ``designate-producer`` component
   Orchestrates periodic tasks that are run by designate.