BIND 10 #2316: Extend "Subnet" with OptionCollection structure

[BIND 10 Development]

#2316: Extend "Subnet" with OptionCollection structure
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  UnAssigned
  marcin                             |                Status:  reviewing
                       Type:  task   |             Milestone:  Sprint-
                   Priority:         |  DHCP-20121018
  medium                             |            Resolution:
                  Component:  dhcp   |             Sensitive:  0
                   Keywords:         |           Sub-Project:  DHCP
            Defect Severity:  N/A    |  Estimated Difficulty:  0
Feature Depending on Ticket:  2318   |           Total Hours:  0
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by marcin):

 * owner:  marcin => UnAssigned
 * status:  accepted => reviewing
 * feature:   => 2318


Comment:

 I added new container (called OptionCotainer) in the Subnet class.
 Primarily this container is a storage for options that have been
 configured via Config Manager. There is a way to tag added option as
 'persistent' or 'non-persistent'. The former means that option is always
 sent to the client (even if option is not requested), the latter means
 that option is just sent when requested.

 Other than that, OptionContainer allows to search for the options using
 their code or using the 'persistency' flag. It will be extended to support
 searching using option spaces once we implement option spaces.

 I am making #2318 dependent on this ticket because #2318 would use the
 container to check that option values have been set up for the subnet when
 new configuration is committed.

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