BIND 10 #2488: Create DHCP Test Plan
BIND 10 Development
do-not-reply at isc.org
Thu Jan 3 17:09:34 UTC 2013
#2488: Create DHCP Test Plan
-------------------------------------+-------------------------------------
Reporter: stephen | Owner:
Type: task | stephen
Priority: medium | Status:
Component: | reviewing
documentation | Milestone:
Keywords: | Sprint-DHCP-20130103
Sensitive: 0 | Resolution:
Sub-Project: DHCP | CVSS Scoring:
Estimated Difficulty: 0 | Defect Severity: N/A
Total Hours: 0 | Feature Depending on Ticket:
| Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Changes (by tomek):
* owner: tomek => stephen
Comment:
''The document does not describe the tests in detail - that will be
covered elsewhere.''
Where? Does such document exist? We can't run tests if we don't even have
them listed.
I've added several v4 features that were omitted (release a lease,
recycle/reuse expired lease).
Although it is possible to specify multiple subnets in v6, server does not
support relayed traffic. We do not have the ability to specify which
subnet is local if there is more than one defined.
''Option (both v4 and v6): selection of standard options available.''
We should specify them exactly (a range 1 to X with X well specified will
suffice). Which are considered a standard? Everything there is RFC
published for? That's 78 options for DHCPv6 alone.
''Performance tool: ability to simulate a number of clients''.
Need concrete values here. "A number" may mean "more than one" or "a
million".
''Performance'' - we need to clarify that while the ultimate goal is to
have multi-process support, it is not part of this release.
Start/stop: Added 2 cases.
Logging: Added more details about logging.
Pool exhaustion is not supported too well. Currently server will give up
after it tries to allocate an address after 100 tries. This parameter is
not configurable yet.
''Check that a reconfiguration removing a particular address pool causes
clients with leases in that pool to be refused a renewal and to obtain
another address.''
Kea doesn't work that way. If the client gets back to us after the lease
expired and the lease was not assigned to anyone else, we will still give
it back to the original client.
''Check that the server rejects all but DISCOVER and REQUEST messages.''
Kea also accepts RELEASE. The code also responds with empty packets to all
other message types. This part of the code is still what we used to call a
skeleton.
''Check that the server rejects malformed DISCOVER and REQUEST messages.''
That will be interesting to watch. :)
''DHCPv6 features: Set up multiple subnets and pools: using different
client characteristics, check that leases are allocated from the correct
pool.''
See my comment above.
''Check that a reconfiguration removing a particular address pool causes
clients with leases in that pool to be refused a renewal and to obtain
another address.''
Not supported yet.
''Check that the server rejects all but SOLICIT, REQUEST and RENEW
messages.''
RELEASE message is also supported.
Is the perfdhcp part of the official delivery? If not, we should
definitely trim down its validation and focus on server.
Two big things are missing:
1. explicit list of clients we want to test inter-op with
2. the actual list of tests (currently this document only lists
requirements, there are no test descriptions).
For example of actual test descriptions, please take a look at Section 5
of doc/dhcp-test-plan.txt from dhcp-val repository.
--
Ticket URL: <http://bind10.isc.org/ticket/2488#comment:8>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list