BIND 10 #1787: update in-memory zone after xfrin

[BIND 10 Development]

#1787: update in-memory zone after xfrin
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:
  jinmei                             |                Status:  new
                       Type:  task   |             Milestone:  Next-Sprint-
                   Priority:         |  Proposed
  medium                             |            Resolution:
                  Component:         |             Sensitive:  0
  Unclassified                       |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  0
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:  xfr    |
  for in-memory                      |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Description changed by jinmei:

Old description:

> Currently only the SQLite3 data source can be updated via incoming xfr.
> We can extend this to in-memory with some extensions to b10-auth,
> b10-xfrin, and the in-memory data source implementations.  I propose
> this feature for the end of y3 release.  For the limited period of
> development, it'd have to be a kind of hack, assuming sqlite3 only,
> etc.
>
> This is a meta ticket for that feature.
>
> It consists of the following subtasks:
> - #1788 update auth spec to specify in-memory "filetype" with sqlite3
> backend
> - #1789 update xfrin to maintain in-memory/sqlite3 zones
> - #1790 update xfrin to have auth reload transfered zones
> - #1791 update InMemoryZoneFinder::load() to support sqlite3 backend
> - #1792 update b10-auth config handler to support in-memory/sqlite3
> - #1793 update b10-auth command handler to reload in-memory/sqlite3
>
> Note: this is a meta ticket and doesn't have to have an estimation.

New description:

 Currently only the SQLite3 data source can be updated via incoming xfr.
 We can extend this to in-memory with some extensions to b10-auth,
 b10-xfrin, and the in-memory data source implementations.  I propose
 this feature for the end of y3 release.  For the limited period of
 development, it'd have to be a kind of hack, assuming sqlite3 only,
 etc.

 This is a meta ticket for that feature.

 It consists of the following subtasks:
 - #1788 update auth spec to specify in-memory "filetype" with sqlite3
 backend
 - #1789 update xfrin to maintain in-memory/sqlite3 zones
 - #1790 update xfrin to have auth reload transfered zones
 - #1791 update InMemoryZoneFinder::load() to support sqlite3 backend
 - #1792 update b10-auth config handler to support in-memory/sqlite3
 - #1793 update b10-auth command handler to reload in-memory/sqlite3
 - (#1794 add a lettuce test for "updating in-memory after xfr" feature)

 Note: this is a meta ticket and doesn't have to have an estimation.

--

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