[bind10-dev] Xfrout Re: Year 4 usability goals

[Jelte Jansen]

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


(mainly, notify out)

- -----------------------------------------------------------
12. xfrin/xfrout Improvements
- ----
The current xfrin/xfrout have not really been designed for high-volume
setups, and are not tested for this. That work must be done at some
point. [Is this usability related or not?]

  xfrin/xfrout Improvement Work
  ----
  12.1 Retro-fit a requirements document [4d]
  12.2 Retro-fit a design document [4d]
  12.3 Retro-fit unit tests [5d]
  12.4 Lettuce tests [4d]
  12.5 Benchmark design and setup [10d]
  12.6 Updates to xfrin [10d]
  12.7 Updates to xfrout [5d]
- -----------------------------------------------------------

I am working on the 'send notify' command, which is in itself not a
big task (the command handler is mostly there, just needs a few
tweaks). But I did want to look into making it a little more flexible,
and looking at notify_out, I would like to see three specific things
for xfrout:;

One is to be able to specify (both on the notify command, and through
config) exactly where to send the notifies to. Currently this is
derived from the zone data, and cannot be modified. Whether or not
this should be done in the first place is another discussion though 9
does it so i guess we'll have to), and I could live with that as a
default, but currently it looks like the entire design is based around
that. It may be possible to work around that, but it might be that we
need to change its internal tracking-of-current-work structures.

The second one is that it is hardcoded to use the sqlite datasource.
Depending on which way we go regarding other datasources this may or
may not be a problem. Though at least being able to use any datasource
would most likely be the right thing :p

The third one is that it is quite insisting on notifying itself too,
had we a configurable notification list then this problem can be
worked around, but ideally it should know which addresses Auth is
listening on, and not send anything to that. So really this is
something that needs an addition to auth too, the ability to ask it
what addresses it is listening on (and, should we have some
views-sort-of-thing, what addresses it is listening on for a specific
zone). This can't be directly derived from configuration, since
configuration could simply be '::' or '0.0.0.0'. If we have that I
think it is relatively easy to not send notifies to oneself.

Jelte
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk9aMcwACgkQ4nZCKsdOncWcjgCeJ2lC+XXQHxD7osmdaQUvivd8
4B8AoIBnrKNEC5EcSzi3vnX23tMLlSbF
=vSo9
-----END PGP SIGNATURE-----