BIND 10 #1648: Abstract pool/lease store: design

BIND 10 Development do-not-reply at isc.org
Mon Jun 11 18:39:24 UTC 2012


#1648: Abstract pool/lease store: design
-------------------------------------+-------------------------------------
                   Reporter:  tomek  |                 Owner:  tomek
                       Type:  task   |                Status:  accepted
                   Priority:         |             Milestone:  DHCP 2012
  medium                             |            Resolution:
                  Component:  data   |             Sensitive:  0
  source                             |           Sub-Project:  DHCP
                   Keywords:         |  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
 * status:  new => accepted


Old description:

> After initial requirements are specified (see #1634 and
> [wiki:DhcpPoolLeaseDesign]), we need to design the API.

New description:

 After initial requirements are specified (see #1634 and
 [wiki:DhcpPoolLeaseRequirements]), we need to design the API.

--

Comment:

 I have updated design document. In particular, I have marked where
 specific information should be kept (data backend or configuration).
 Please comment on those.

 I would like to also ask for review of the following topics:

 1. Pool removal and DB consistency. See A10.
 2. Q3, Q9: Add pools to the design. Reasons: see answer to Q3, Q9 in
 design document (reasons in short form: relay selection, confirm messages,
 parameters for out-of-pool reservations)
 3. Q4: Human readable vs machine readable representation. Human readable
 in DB, keep on wire representation in memory.
 4. Q5: DNS updates.
 5. Q6: Do we want value (t1,t2,prefered,valid) ranges?
 6. Q9: Do we want to support in-pool reservation? Do we want to support
 out-of-pool reservation?
 7. Q12: How do we want to specify DDNS information? Per interface? Per
 subnet/pool?

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


More information about the bind10-tickets mailing list