BIND 10 #2469: DHCPv6 Config Parser: when setting global value, values in subnets should be changed.

[BIND 10 Development]

#2469: DHCPv6 Config Parser: when setting global value, values in subnets should
be changed.
-------------------------------------+-------------------------------------
            Reporter:  marcin        |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  medium        |                    Milestone:
           Component:  dhcpconf      |  Sprint-DHCP-20121115
           Sensitive:  0             |                     Keywords:
         Sub-Project:  DHCP          |              Defect Severity:
Estimated Difficulty:  0             |  Medium
         Total Hours:  0             |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 The following scenario will not work properly with DHCPv6 config parser:
 1. Set global configuration values
 2. Add new subnet without any values other than subnet and pool (this
 makes the subnet inherit global values)
 3. Change any of the global values - this should force change of the
 particular value in the subnet object but it doesn't.

 In the step 3. function that does configuration will receive the request
 to change global value and only global value is changed. Another thing
 that should happen at this point is the check that global value has been
 changed and all corresponding values within subnets should be affected but
 parsing algorithm does not force this by itself. We need to implement a
 logic that will iterate through all existing subnets and if their
 configuration is inherited from global configuration they should be
 updated accordingly. The major problem here is that when we create a
 subnet we do not record whether it is dependent on global values or local
 values. This has to be recorded on subnet object creation.

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