BIND 10 #2113: Configuration plugin check for datasources

[BIND 10 Development]

#2113: Configuration plugin check for datasources
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  jelte
  vorner                             |                Status:  reviewing
                       Type:         |             Milestone:
  defect                             |  Sprint-20120731
                   Priority:         |            Resolution:
  medium                             |             Sensitive:  0
                  Component:         |           Sub-Project:  DNS
  configuration                      |  Estimated Difficulty:  5
                   Keywords:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by vorner):

 * owner:  vorner => jelte


Comment:

 Hello

 Replying to [comment:6 jelte]:
 > I think the error string in case of bad classes could be better; it
 prints "Unrecognized RR parameter string" which isn't really helpful IMO.

 Is it better now?

 > I also found a small problem with the 'cache disabled' warning I made
 you add in a previous review; I added a MasterFiles configuration with my
 zone and loaded it, but the ClientList logs a warning:
 > 2012-07-31 11:30:46.507 WARN  [b10-cfgmgr.datasrc]
 DATASRC_LIST_NOT_CACHED zone tjeb.nl/IN not cached, cache disabled
 globally. Will not be available.
 >
 > However, the zone appears to be loaded and served fine.
 >
 > {{{
 > 2012-07-31 11:35:39.506 WARN  [b10-cfgmgr.datasrc]
 DATASRC_LIST_NOT_CACHED zone tjeb.nl/IN not cached, cache disabled
 globally. Will not be available.
 > }}}
 > Looks like that is because it isn't called with allow_cache=True in
 datasrc_config_plugin.

 Yes, that's correct ‒ the config manager has the cache disabled, therefore
 it warns. But the auth has it enabled and it serves it.

 But I don't think it is a good idea to enable the cache in the
 configuration manager, because then, it would take a long time to load it
 (imagine a very large zone) and then it would just throw it away anyway.

 So, what do we do about the warning? I probably could mangle the
 configuration to not contain the zones and check them manually only. Would
 that be OK or does it sounds like too much of a hack?

-- 
Ticket URL: <https://bind10.isc.org/ticket/2113#comment:7>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development