From fd1b16a4456010b060b7fee622f99d18683f64ba Mon Sep 17 00:00:00 2001 From: Tomek Mrugalski Date: Tue, 10 Jun 2014 16:23:24 +0200 Subject: [PATCH] [3418] Several clean-ups in sections 1...3 --- doc/guide/kea-guide.xml | 186 ++++++++++++++++++++-------------------- 1 file changed, 94 insertions(+), 92 deletions(-) diff --git a/doc/guide/kea-guide.xml b/doc/guide/kea-guide.xml index 08f3b343ac..6fb6acc4e7 100644 --- a/doc/guide/kea-guide.xml +++ b/doc/guide/kea-guide.xml @@ -26,8 +26,7 @@ - Kea Guide - Administrator Reference for Kea + Kea Administrator Reference Manual 2010-2014Internet Systems Consortium, Inc. @@ -40,7 +39,6 @@ Consortium (ISC). - This is the reference guide for Kea version &__VERSION__;. The most up-to-date version of this document (in PDF, HTML, @@ -53,18 +51,12 @@ - Introduction Kea is the next generation of DHCP servers developed by ISC. It supports both DHCPv4 and DHCPv6 protocols along with their - extensions (e.g. prefix delegation). It also supports the dynamic - updates to DNS. + extensions, e.g. prefix delegation and dynamic updates to DNS. @@ -87,7 +79,7 @@ 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. + which, as a whole, implement the DHCP protocols". @@ -96,20 +88,18 @@
- Supported Platforms - Kea builds have been tested on (in no particular order) + Kea is officially supported on RedHat Enterprise Linux, + CentOS, Fedora and FreeBSD systems. It is also likely to work on many + other platforms: builds have been tested on (in no particular order) Debian GNU/Linux 6 and unstable, Ubuntu 9.10, NetBSD 5, Solaris 10 and 11, FreeBSD 7 and 8, CentOS Linux 5.3, - MacOS 10.6 and 10.7, and OpenBSD 5.1. - - It has been tested on Sparc, i386, and amd64 hardware - platforms. - - It is planned for Kea to build, install and run on - Windows and standard Unix-type platforms. + MacOS 10.6 and 10.7, and OpenBSD 5.1. Non supported systems + (especially non-Linux) are likely to have issues with directly + connected DHCPv4 clients. + There are currently no plans to port Kea to Windows platforms.
@@ -125,41 +115,56 @@ - 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 + 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 - ()). The dependency - on Python will be removed once a replacing configuration - and startup mechanisms are developed for Kea. At this point - Kea will be written in pure C++. + They also work with Python 3.2, 3.3 or 3.4 (). The dependency on Python will + be removed once a replacing configuration and startup + mechanisms are developed and released as Kea 0.9. At this + point Kea will be written in pure C++. Kea uses the Botan crypto library for C++ (). It requires at least Botan version 1.8. + Kea uses the log4cplus C++ logging library (). It requires at least log4cplus version 1.0.3. - + + + + Kea can use MySQL headers and libraries to build MySQL database backend + that can be used to store leases. This is an optional dependency. When + it is missing, Kea will lack the ability to store leases in MySQL + database. + + + + Kea can use PostgreSQL headers and libraries to build PostgreSQL + database backend that can be used to store leases. This is an optional + dependency. When it is missing, Kea will lack the ability to store + leases in PostgreSQL database.
Starting and Stopping the Server + 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 @@ -261,6 +266,7 @@
Managing BIND 10 + Once BIND 10 is running, a few commands are used to interact @@ -330,20 +336,20 @@ var/ Quick start - This quickly covers the standard steps for installing - and deploying Kea. - For further details, full customizations, and troubleshooting, - see the respective chapters in the Kea guide. + This quickly covers the standard steps for installing and deploying Kea. + For further details, full customizations, and troubleshooting, see the + respective chapters in the Kea guide. -
- Quick start guide for DHCPv6 service +
+ Quick start guide for DHCPv4 and DHCPv6 services - Install required run-time and build dependencies. + Install required run-time and build dependencies. See for details. @@ -360,7 +366,7 @@ var/ Go into the source and run configure: $ cd kea $ autoreconf --install -$ ./configure +$ ./configure [your extra parameters] @@ -378,39 +384,35 @@ $ ./configure - Change directory to the install prefix (by default - /usr/local/): - $ cd /usr/local/ + Edit your configuration file for DHCPv4. See doc/examples/kea4 + for set of examples. + + + + + Start Kea DHCPv4 server (as root): + # b10-dhcp4 -c /path/to/your/kea4/config/file.json - Create a user for yourself: - $ sbin/b10-cmdctl-usermgr add root - and enter a newly chosen password when prompted. - + Test it; for example, use the + ISC DHCP client + to send DHCPv4 queries to the server and verify that the client receives a + configuration from the server: + $ dhclient -4 eth0 + - Start the server (as root): - $ sbin/bind10 - - + Edit your configuration file for DHCPv6. See doc/examples/kea6 + for set of examples. + + - DHCP components are not started in the default - configuration. In another console, enable the DHCPv6 - service (by using the bindctl utility - to configure the b10-dhcp6 component to - run): $ bin/bindctl - (Login with the username and password you used above to create a user.) - -> config add Init/components b10-dhcp6 - -> config set Init/components/b10-dhcp6/kind dispensable -> config commit -> quit - + Start Kea DHCPv6 server (as root): + # b10-dhcp6 -c /path/to/your/kea6/config/file.json @@ -419,9 +421,11 @@ $ ./configure ISC DHCP client to send DHCPv6 queries to the server and verify that the client receives a configuration from the server: - $ dhclient -6 + $ dhclient -6 eth0 + +
@@ -435,17 +439,15 @@ $ ./configure Packages - Some operating systems or software package vendors may - provide ready-to-use, pre-built software packages for Kea. - Installing a pre-built package means you do not need to - install build-only prerequisites and do not need to - make the software. + Some operating systems or software package vendors may provide + ready-to-use, pre-built software packages for Kea. Installing a + pre-built package means you do not need to install build-only + prerequisites and do not need to make the software. - FreeBSD ports, NetBSD pkgsrc, and Debian - testing package collections provide - all the prerequisite packages. + FreeBSD ports, NetBSD pkgsrc, and Debian testing + package collections provide all the prerequisite packages.
@@ -463,6 +465,7 @@ $ ./configure + etc/bind10/ — configuration files. @@ -475,6 +478,7 @@ $ ./configure + libexec/bind10/ — executables that a user wouldn't normally run directly and are not run independently. @@ -490,12 +494,14 @@ $ ./configure + share/bind10/ — configuration specifications. + share/doc/bind10/ — this guide and other supplementary documentation. @@ -508,6 +514,7 @@ $ ./configure + var/bind10/ — data source and configuration databases. @@ -520,10 +527,9 @@ $ ./configure Building Requirements - In addition to the run-time requirements (listed in - ), building Kea - from source code requires various development include headers and - program development tools. + In addition to the run-time requirements (listed in ), building Kea from source code requires + various development include headers and program development tools. @@ -548,6 +554,7 @@ $ ./configure To build Kea, also install the Botan (at least version 1.8) and the log4cplus (at least version 1.0.3) development include headers. + standard development headers, make, and pkg-config. Kea builds have been tested with GCC g++ 3.4.3, 4.1.2, 4.1.3, 4.2.1, 4.3.2, and 4.4.1; Clang++ 2.8; and Sun C++ 5.10. + @@ -589,9 +597,10 @@ as a dependency earlier --> Download Tar File - Kea 0.8 is available as a part of BIND10 1.2 release, which is - a final release of BIND10 from ISC. This release can be downloaded - from: . + Kea 0.8 is available as a part of BIND10 1.2 release, which is a final + release of BIND10 from ISC. This release can be downloaded from: + . Upcoming Kea 0.9 and all + following releases will be shipped as a stand-alone tarball.
@@ -680,8 +689,9 @@ as a dependency earlier --> --with-pythonpath - Define the path to Python 3.1 if it is not in the - standard execution path. + Define the path to Python 3.x if it is not in the + standard execution path. Python 3.x is mandatory for Kea 0.8, + but is no longer required for upcoming Kea 0.9. @@ -725,8 +735,8 @@ as a dependency earlier --> $ ./configure \ --with-boost-include=/usr/pkg/include \ - --with-pythonpath=/usr/pkg/bin/python3.1 \ - --prefix=/opt/bind10 + --with-dhcp-pgsql=/usr/local/bin/pg_config \ + --prefix=/opt/kea @@ -782,18 +792,10 @@ as a dependency earlier -->
- + - -