BIND 10 #2598: DHCP Testing: Start/Stop, Logging, and Configuration

[BIND 10 Development]

#2598: DHCP Testing: Start/Stop, Logging, and Configuration
-------------------------------------+-------------------------------------
            Reporter:  stephen       |                        Owner:
                Type:  task          |  jwright
            Priority:  medium        |                       Status:
           Component:  dhcp          |  accepted
            Keywords:                |                    Milestone:
           Sensitive:  0             |  Sprint-DHCP-20130214
         Sub-Project:  DHCP          |                   Resolution:
Estimated Difficulty:  0             |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:  N/A
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by jwright):

 From http://bind10.isc.org/wiki/DhcpTestPlan:

 The following tests of the servers are needed. Where a client is required
 for a test, the ISC DHCP client will be used.

 Start/stop
 Start/stop the DHCPv4/v6 server via bindctl and check that it is
 running/stopped.
 Starting and stopping the DHCPv4/6 server many times in quick succession.
 Verify that the DHCPv4/v6 server starts with the whole BIND10, if
 configured to do so.
 Verify that the DHCPv4/v6 server stops with the whole BIND10.
 Logging
 Enabling logging (verbose) and check that messages from the V4/V6 server
 are being logged.
 Enabling logging (non-verbose) and check that only "important" messages
 are logged.
 Verify that logging can be configured using various levels (debug, info,
 warning, error).
 Configuration
 Check that the configuration is preserved when server is restarted.
 Check that the existing configuration can be completely removed.
 Check that the configuration can be applied with several commits (each
 applying a portion of whole configuration). Each step (a separate commit)
 must be self consistent.
 Check that an existing subnet, pool, option value can be modified
 (updated)

-- 
Ticket URL: <http://bind10.isc.org/ticket/2598#comment:3>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development