BIND 10 #670: identify a secondary zone

[BIND 10 Development]

#670: identify a secondary zone
-------------------------------------+-------------------------------------
                 Reporter:  jreed    |                Owner:  UnAssigned
                     Type:  defect   |               Status:  reviewing
                 Priority:  blocker  |            Milestone:  A-Team-
                Component:           |  Sprint-20110316
  secondary manager                  |           Resolution:
                 Keywords:           |            Sensitive:  0
Estimated Number of Hours:  0.0      |  Add Hours to Ticket:  0
                Billable?:  1        |          Total Hours:  0
                Internal?:  0        |
-------------------------------------+-------------------------------------
Changes (by vorner):

 * owner:  vorner => UnAssigned
 * status:  accepted => reviewing


Comment:

 Hello

 I think it is ready for review. But I'm not exactly sure inside the zone
 manager, it seems to be quite chaotic piece of code (or it might be just
 me, getting lost in python). So, don't spare me.

 It loads only the zones listed in secondary_zones variable, instead of
 everything that is in the database.

 I also noticed it kind of relies on sqlite3 data source and completely
 ignores the class of zone. Is some larger-scale rewrite of zone manager
 planned?

 The changelog could be:
 {{{
 [func]*      vorner
 Zone manager no longer thinks it is secondary master for all zones in the
 database They are listed in Zonemgr/secondary_zones configuration variable
 (in the form [{"name": "example.com", "class": "IN"}]).
 }}}

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