BIND 10 #2854: memory manager framework

[BIND 10 Development]

#2854: memory manager framework
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:
  jinmei                             |                Status:  new
                       Type:  task   |             Milestone:  Next-Sprint-
                   Priority:         |  Proposed
  medium                             |              Keywords:
                  Component:  shmem  |             Sensitive:  0
  manager                            |           Sub-Project:  DNS
               CVSS Scoring:         |  Estimated Difficulty:  0
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
  shared memory data source          |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
 Subtask of #2830.  Depend on #2853 (if written in Python).

 First, decide which language to use: C++ or Python.  I'm currently
 inclined to Python because major lower level work is done in the C++
 datasrc library, and the rest of the manager isn't performance
 sensitive or system dependent.

 Implement some minimal part of memory manager.  Also fix its name in
 this task (so far it's tentatively named "b10-memmgr", but it doesn't
 have to be so).

 In this task, we'll create:
 - a new daemon program
 - subscribe to the !Memmgr (also tentative, fix it) group
 - import data_sources and its own configurations
 - the memmgr's module spec would be something like (fix it in this task):
   - commands: shutdown, loadzone(like auth), updatezone (details to be
 fixed)
   - configs: mapped-file-dir (string, specifies a directory to store
     memory mapped files)

 loadzone and updatezone can be no-op (maybe just validate args) for
 now.

 From the data source config, it creates a corresponding `ClientList`,
 and builds a list of `SegmentInfo` as described in
 http://bind10.isc.org/wiki/SharedMemoryIPC#a3.ConceptualDataStructures
 (structure/class name is tentative) corresponding to the client list.
 (the entry should probably also contains the memory segment type and
 per type state, such as mapped or not).

 Write minimal man page.

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