From 30f499bd2d08684ae587ee59d52afedec83ecb38 Mon Sep 17 00:00:00 2001 From: "Jeremy C. Reed" Date: Mon, 11 Aug 2014 16:34:40 +0000 Subject: [PATCH] Remove old out-dated BIND10 content. Mention some more Kea tools and minor rewording. Note that the brief sections on starting and stopping and managing the software are now gone. --- doc/guide/intro.xml | 159 ++++---------------------------------------- 1 file changed, 13 insertions(+), 146 deletions(-) diff --git a/doc/guide/intro.xml b/doc/guide/intro.xml index d2825f1165..32588e1178 100644 --- a/doc/guide/intro.xml +++ b/doc/guide/intro.xml @@ -18,26 +18,9 @@ Kea was initially developed as a part of the BIND 10 framework (). In early 2014, ISC made the decision to discontinue active development of BIND 10 and - continue development of Kea as standalone DHCP software. As a result, - the components and libraries related to the BIND10 framework and DNS - are going to be removed from the Kea source tree over time. - In order to remove the dependency on Python 3, the BIND 10 framework - will be replaced by the server startup and configuration mechanisms - written in C++. + continue development of Kea as standalone DHCP software. - - Kea was implemented in the BIND 10 framework and to certain extent - still depends on various BIND 10 libraries. It also requires the BIND 10 - framework to run, because the BIND 10 configuration mechanisms are used to - configure Kea. As a result, this document still refers to BIND 10 in many - paragraphs. The term "BIND 10" in the context of this document means - "BIND 10 libraries and applications which are necessary for Kea to run - and configure". The term "Kea" means "the collection of binaries and libraries - which, as a whole, implement the DHCP protocols". - - - This guide covers Kea version &__VERSION__;. @@ -70,20 +53,6 @@ - - - Kea was developed as a collection of applications within BIND - 10 framework and it still relies on the remaining parts of - this framework. In particular, the servers' configuration and - startup are still facilitated by the modules which originate - in BIND 10. These modules require at least Python 3.1 to run. - They also work with Python 3.2, 3.3 or 3.4 (). The dependency on Python will - be removed once replacement configuration and startup - mechanisms are developed and released as Kea 0.9. At this - point Kea will be written in pure C++. - - @@ -122,24 +91,13 @@ -
- Starting and Stopping the Server - +
+ Kea Software Kea is modular. Part of this modularity is accomplished using multiple cooperating processes which, together, provide the server functionality. - - - - - At first, running many different processes may seem confusing. - However, these processes are started by running a single - command, bind10. This command starts - a master process, b10-init, which will - start other required processes and other processes when - configured. The processes that may be started have names - starting with "kea-", including: + The following software is included with Kea: @@ -148,17 +106,9 @@ - b10-cfgmgr — - Configuration manager. - This process maintains all of the configuration for BIND 10. - - - - - - b10-cmdctl — - Command and control service. - This process allows external control of the BIND 10 system. + keactrl — + Tool to start, stop, reconfigure, and report status + for the Kea servers. @@ -190,75 +140,15 @@ - b10-msgq — - Message bus daemon. - This process coordinates communication between all of the other - BIND 10 processes. - - - - - - kea-sockcreator — - Socket creator daemon. - This process creates sockets used by - network-listening BIND 10 processes. - - - - - - b10-stats — - Statistics collection daemon. - This process collects and reports statistics data. - - - - - - b10-stats-httpd — - HTTP server for statistics reporting. - This process reports statistics data in XML format over HTTP. + perfdhcp — + DHCP benchmarking tool which simulates multiple clients to + test both IPv4 and IPv6 servers performance. - - These do not need to be manually started independently. - - -
- -
- Managing BIND 10 - - - - Once BIND 10 is running, a few commands are used to interact - directly with the system: - - - - bindctl — - Interactive administration interface. - This is a low-level command-line tool which allows - a developer or an experienced administrator to control - Kea. - - - - - b10-cmdctl-usermgr — - User access control. - This tool allows an administrator to authorize additional users - to manage Kea. - - - - -
@@ -267,33 +157,10 @@ In addition, manual pages are also provided in the default installation. - - - BIND 10 also provides libraries and programmer interfaces - for C++ and Python for the message bus and configuration backend, - and, of course, DHCP. These include detailed developer - documentation and code examples. + Kea also provides C++ libraries and programmer interfaces for + DHCP. These include detailed developer documentation and + code examples. -- 2.47.2