BIND 10 #2835: add interface to get properties of datasrc clients from ClientList
BIND 10 Development
do-not-reply at isc.org
Fri Mar 1 17:52:47 UTC 2013
#2835: add interface to get properties of datasrc clients from ClientList
-------------------------------------+-------------------------------------
Reporter: jinmei | Owner:
Type: task | Status: new
Priority: medium | Milestone: Next-
Component: data source | Sprint-Proposed
Keywords: | Resolution:
Sensitive: 0 | CVSS Scoring:
Sub-Project: DNS | Defect Severity: N/A
Estimated Difficulty: 0 | Feature Depending on Ticket:
Total Hours: 0 | shared memory data source
| Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Comment (by jinmei):
Replying to [comment:1 vorner]:
> I'm not sure about the name. It is possible to have multiple 'sqlite3'
clients in the same list, for example.
Right, so the default (using the data source type) may not always
work. `ClientList` will check the uniqueness when it validates the
given configuration.
So, if we have this config:
{{{
"IN": [{
"type": "sqlite3",
"params": {"database_file": "/usr/local/var/bind10/zone.sqlite3"}
}],
"CH": [{
"type": "sqlite3",
"params": {"database_file": "/usr/local/var/bind10/zone.sqlite3"}
}],
}}}
The default "sqlite3" name will be assumed for both clients, and this
configuration will be rejected. The administrator needs to give a
unique name explicitly:
{{{
"IN": [{
"type": "sqlite3",
"name": "sqlite3-in",
"params": {"database_file": "/usr/local/var/bind10/zone.sqlite3"}
}],
"CH": [{
"type": "sqlite3",
"name": "sqlite3-ch",
"params": {"database_file": "/usr/local/var/bind10/zone.sqlite3"}
}],
}}}
(in this case, one of the "name" param can be omitted)
--
Ticket URL: <http://bind10.isc.org/ticket/2835#comment:2>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list