[bind10-dev] datasources config

[Stephen Morris]

On 26/09/2011 08:27, Jelte Jansen wrote:
> On 09/22/2011 08:51 PM, JINMEI Tatuya / 神明達哉 wrote:
>> Regarding point 3 (which is also related to how we define config
>> for each data source in the above example), I guess we might want
>> to provide a consistent interface, where the generic BIND 10
>> config only provides minimal level of information to get access
>> to the data source, and detailed config is within the data source
>> itself.  So, for example, the system-wide configuration example
>> would be:
> 
>> [ { type: "sqlite3", config: { db_file:
>> "/var/bind10/sqlite3_data_source.db" } }, { type: "mysql", 
>> config: { server_address: "2001:db8::53", server_port: "53535" }
>> }, { type: "inmemory", config: some way.. }, { type: "static",
>> (probably no config here) } ]
> 
> 
> This is the same as what I proposed, except for the class part.
> 
> I was thinking we might be able to provide more
> in-depth-but-not-online checks by a similar structure as we
> currently use for tsig and logging (i.e. a python minimodule that
> does some checks)
> 
>> (I'm not sure what "config" at this level would be appropriate
>> for the in-memory data source - maybe we'll introduce an on-disk
>> zone table in which a list of supported zones is defined with
>> corresponding zone files).

I like the idea of a data source containing most of its configuration
parameters, but are there any cases where the same data source is used
by two or more components, each requiring a different configuration?
If so, how do we distinguish between them.

Perhaps writing some user stories might make things clearer?

Stephen