BIND 10 #1843: Profiles of configuration

BIND 10 Development do-not-reply at isc.org
Thu Apr 19 15:05:40 UTC 2012


#1843: Profiles of configuration
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  UnAssigned
  vorner                             |                Status:  reviewing
                       Type:         |             Milestone:
  enhancement                        |  Sprint-20120501
                   Priority:         |            Resolution:
  medium                             |             Sensitive:  0
                  Component:  bind-  |           Sub-Project:  Core
  ctl                                |  Estimated Difficulty:  6
                   Keywords:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by jelte):

 * owner:  jelte => UnAssigned
 * status:  assigned => reviewing


Comment:

 Ok, here's an initial implementation of the idea. I named it 'execute' as
 the command in bindctl, but other suggestions can me made.

 It takes either a file or a built-in set of commands, and the 'language'
 supports comments (with #) and a few simple directives (as suggested by
 stephen), with ! (e.g. !echo foo).

 The builtin sets are hardcoded; we could implement those through files as
 well but i didn't really want to add yet another directory where we need
 to keep track of.

 Currently only one builtin is supported, one that adds all the b10-auth-
 related components to Boss/components (start auth, zonemgr, xfrin and
 xfrout).

 For either, adding the argument 'show' would print all the commands
 instead of executing them.

 We can add more but let's get this approach acked first. Also, I have a
 few ideas about extending this

 I have not updated guide/bindctl documentation for this yet, for kind of
 the same reasons i didn't add more builtin sets.

 I've added one method to config_data, set_local_changes(), which is needed
 to revert config if there was an error. And while i was there i found and
 fixed a half-related issue in find_spec_part().

 Oh, and most of the tests are done in lettuce, essentially these are
 system tests, since most actions from scripts rely on the entire thing
 running.

 Some future expansions ideas:
 - add a 'check' directive which can check (other) config values
 - add parameters, 'execute add zone <zone_name>', and interactive
 questions ('master or slave? if slave, what master do you want to use).
 Possibly combined (so you are not asked if the value is given as a
 parameter, or something)

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


More information about the bind10-tickets mailing list