BIND 10 #2279: requirements for configuration framework improvements

[BIND 10 Development]

#2279: requirements for configuration framework improvements
-------------------------------------+-------------------------------------
            Reporter:  jelte         |                        Owner:
                Type:  task          |                       Status:  new
            Priority:  medium        |                    Milestone:  Next-
           Component:  Unclassified  |  Sprint-Proposed
           Sensitive:  0             |                     Keywords:
         Sub-Project:  DNS           |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 There are at least 3 'topics' of configuration improvements we can make:

 1 the general framework (classes that hold/transfer/act on configuration
 data)
 2 bindctl itself
 3 the *layout* of configuration

 In principe, the 3rd is somewhat separate (though no less important); and
 2 kind of depends in a lot of things on 1 (due to the lowlevel datatypes
 we have used for both specs and data, bindctl and config_data on the
 python side have gotten quite muddled, and ugly).

 So the first task is to reboot the framework discussion I started some
 time ago; and I think the *real* very first task is to identify, now that
 we have experience with the current system, and what it can and cannot do,
 the requirements, for there turned out to be quite a few more than the
 current system was designed for;

 For instance, we would probably like to have custom data types (to add,
 for instance, an IP address or range, something DHCP certainly needs, and
 which would also be usable in ACLs; if these would be compounds, they may
 also fill the requirement of 'repeated' configuration bits, where
 different configurable things have the same layout (listen ports for auth
 and resolver, to name one). Another thing that is sorely lacking is diffs.
 We also need a more generalized way of checking them, and recover from
 errors. But there is probably much, much more.

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