BIND 10 #2832: extend data source config to specify shmem segment params

BIND 10 Development do-not-reply at isc.org
Fri Mar 15 03:40:51 UTC 2013


#2832: extend data source config to specify shmem segment params
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  task          |                       Status:  new
            Priority:  medium        |                    Milestone:  Next-
           Component:  Unclassified  |  Sprint-Proposed
            Keywords:                |                   Resolution:
           Sensitive:  0             |                 CVSS Scoring:
         Sub-Project:  DNS           |              Defect Severity:  N/A
Estimated Difficulty:  2             |  Feature Depending on Ticket:
         Total Hours:  0             |  shared memory data source
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by jinmei):

 * milestone:  Previous-Sprint-Proposed => Next-Sprint-Proposed


Old description:

> subtask of #2830.  no dependency.
>
> We'll extend the data source configuration so we can specify the type
> of cache (in memory) memory segment type and its parameter, if any.
> It would look like this:
>
> {{{
> "IN": [{
>     "type": "sqlite3",
>     "params": {"database_file":
> "/Users/jinmei/src/isc/git/bind10/zone.sqlite3"},
>     "cache-zones": ["jinmei.org", "kame.net"],
>     "cache-enable": true,
>     "cache-segment-type": "mapped",
>     "cache-segment-params": {
>       "mapped-file-base": "/usr/local/var/bind10/zone.mapped"
>     }
> }]
> }}}
>
> cache-segment-type has the default of "local".
> the default of cache-segment-params is empty.
>
> For now we only extend the spec.  It will be simply ignored if
> specified in the actual config.
>
> Note: mapped-file-base would have some reasonable default so the user
> can omit it.

New description:

 subtask of #2830.  no dependency.

 We'll extend the data source configuration so we can specify the type
 of cache (in memory) memory segment type and its parameter, if any.
 It would look like this:

 {{{
 "IN": [{
     "type": "sqlite3",
     "name": "sqlite3",
     "params": {"database_file": "/var/bind10/zone.sqlite3"},
     "cache-zones": ["example.org", "example.com"],
     "cache-enable": true,
     "cache-segment-type": "mapped"
 }]
 }}}

 The default value of the "name" is the data source type (as that would
 usually be unique).  If there are more than one instances of the
 same data source type, the administrator is responsible for giving
 them unique names; the configuration checker should validate the
 uniqueness.

 cache-segment-type has the default of "local".

 For now we only extend the spec.  It will be simply ignored if
 specified in the actual config.

--

Comment:

 (I've revised the description based on the latest design).

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


More information about the bind10-tickets mailing list