- .. _config-backend:
+.. _config-backend:
Kea Configuration Backend
=========================
deleting global parameters, shared networks, subnets, pools, options, option
definitions, and client classes. In addition, it provides essential business
logic that ensures the logical integrity of the data. All CB API commands
-start with ``remote-``. See :ref:`commands-cb-cmds` for a complete
-list.
+start with ``remote-``. See
+:ref:`libdhcp-cb-cmds-so-configuration-backend-commands` for more information.
Installation and maintenance of external database software is beyond the scope of this manual.
Once installation is completed, the CB commands API can be used to populate
the database with Kea configuration information.
+.. _cb-sharing:
+
Configuration Sharing and Server Tags
-------------------------------------
Stork uses Kea API calls from the :ischooklib:`libdhcp_host_cmds.so` and
:ischooklib:`libdhcp_subnet_cmds.so` hooks to make changes to Kea's
- configuration. Such usage is incompatible with the :ref:`_config-backend`
+ configuration. Such usage is incompatible with the :ref:`config-backend`
(CB). Stork does not currently implement support for the
:ischooklib:`libdhcp_cb_cmds.so` needed to make changes to CB
configuration. If using the Kea CB, Stork can only be safely used in a