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

[BIND 10 Development]

#1648: Abstract pool/lease store: design
-------------------------------------+-------------------------------------
                   Reporter:  tomek  |                 Owner:  UnAssigned
                       Type:  task   |                Status:  reviewing
                   Priority:         |             Milestone:  Sprint-
  medium                             |  DHCP-20120703
                  Component:  data   |            Resolution:
  source                             |             Sensitive:  0
                   Keywords:         |           Sub-Project:  DHCP
            Defect Severity:  N/A    |  Estimated Difficulty:  0
Feature Depending on Ticket:         |           Total Hours:  0
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by tomek):

 Replying to [comment:5 marcin]:
 > '''Pool removal and DB consistency'''
 > The description on wiki page says:
 > ''I propose following mechanism: once the lease is marked for removal,
 it is removed immediately, if the number of active leases is 0. Otherwise
 it is marked for removal. No new leases are allowed and existing leases
 are not extended. This will allow for gentle lease removal.''
 >
 > Shouldn't that be?
 > ''I propose following mechanism: once the '''pool''' is marked for
 removal, it is removed immediately, if the number of active leases is 0.
 Otherwise it is marked for removal. No new leases are allowed and existing
 leases are not extended. This will allow for gentle '''pool''' removal.''
 Yes. Thanks for catching this. Fixed.

 > In general I like the idea not to remove things immediately but are
 there possible any corner cases like "infinite leases"? If so, is there
 any way to assign finite expiration time to make sure we will be finally
 able to remove it and parent pool?
 The cleanest way to solve this is to not allow fixed leases in your
 dynamic pool.

 > '''Q6: Do we want to specify fixed values or ranges for timers like t1,
 t2, preferred or valid lifetimes?'''
 > Is this meant to be per/pool configuration or it is global for the
 server?
 Both. See our idea of parameter hierarchy.

 > '''Q9: Reserved leases?'''
 > If we have leases within pools we will not be actually able to remove
 pools as there will be fixed leases referencing this pool in DB. This will
 support idea to split them.
 One more argument for going with out-of-pool fixed leases then.

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