BIND 10 #3281: Subnet reconfiguration improvements

[BIND 10 Development]

#3281: Subnet reconfiguration improvements
-------------------------------------+-------------------------------------
                   Reporter:  tomek  |                 Owner:
                       Type:         |                Status:  new
  defect                             |             Milestone:  DHCP
                   Priority:         |  Outstanding Tasks
  medium                             |              Keywords:
                  Component:         |             Sensitive:  0
  dhcpconf                           |           Sub-Project:  DHCP
               CVSS Scoring:         |  Estimated Difficulty:  0
            Defect Severity:         |           Total Hours:  0
  Medium                             |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
 This affects both v4 and v6. Right now there is a static subnet-id counter
 that is reset during every configuration update. It acts so the first
 subnet gets subnet-id = 1, the second subnet-id = 2 and so on. This works
 nicely if the number of subnets doesn't change or a new subnet is added.

 It doesn't work in the following 2 cases:
 a) N subnets is configured. One of the 1..N-1 subnets (i.e. any but not
 the last subnet) is removed. Then subnet X becomes X-1.
 b) subnet X is removed and at the same time, a different subnet is added
 instead.

 Subnet-id is stored in the lease information.

 One possible solution is to allow admins to specify subnet-id manually.
 This may be bothersome, so the default value of 0 should mean "please
 number them automatically".

 It is likely that some sort of database update mechanism during
 reconfiguration is needed.

-- 
Ticket URL: <http://bind10.isc.org/ticket/3281>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development