[bind10-dev] Summary of configuration / cc-channel discussions

[Michael Graff]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On today's call we came to various conclusions:

NETCONF, used internally, is probably overly complicated.  It puts a
huge initial implementation step-function in front of any work we do.

Jelte is going to look into

Using SQLite to store configuration data and having various modules pull
their configuration from that is the plan.  The operations should be
API'd so we don't call SQLite directly, but instead call functions like
"Add A Zone" or "Add A Master for a Zone" etc.

We will use the OpenReg (or a simple derivation of it) for the
command/control light-weight message API.  Which still needs a good
name.  I propose Octopus.  Not furry, but descriptive.

Octopus will provide a file descriptor which is used in the client's
normal processing loop.  When it is readable, an API call is made which
may return a message.  Not certain about writing ; I'm tempted to let it
block until the full data is sent, but I'm not certain yet.  We only
sent very small messages in OpenReg.

We may implement NETCONF externally along with SNMP, a RESTful
interface, XMLRPC, and perhaps even SOAP.  It all depends on what we
need and what people ask for.  We should choose one initially and run
with it for the BigTool CLI.  I propose a RESTful interface; this may be
something to discuss on the next call.  If people need examples, I can
make them up fast; REST is just that simple. :)

- --Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqpKHAACgkQ+NNi0s9NRJ3b/wCfUx/yQ5oRMqQLdLs6C+1t/cWo
tAIAmQEEIs7mRk7ToQchAr+CkizEzXvM
=kvJS
-----END PGP SIGNATURE-----