[bind10-dev] addZone interface for the new loadzone and zone management framework

[JINMEI Tatuya / 神明達哉]

At Thu, 06 Dec 2012 11:09:26 +0100,
Jelte Jansen <jelte at isc.org> wrote:

> > I'd like to note first how I dislike our „short term quick hacks“.
> > It seems our „short term“ is very long and we seem to spend very
> > much time implementing short-term hacks we throw away later. It
> > makes the code quality lower and makes our progress slower (we
> > sometimes gain some short-term advantage like having a feature
> > available for release, but I don't know if it's worth it).
> > 
> > In this sense, I think the addZone approach is slightly better.
> > Optimally, we would have the discussion about how to store and
> > manage zones first (which we failed to have for some long time now
> > already), but I understand it's not possible at this stage.
> 
> My reasoning was that a workaround would probably be as much work,
> even now, actually. The potential problem would be that the interface

I'm afraid the fact that we are having this discussion is it requires
a certain amount of time:-)

> might change, but in terms of implementation code, I don't think the
> add-zone-to-db code would change for that anyway, so might as well
> write that directly there, instead of in another workaround.

Focusing on the short term plan of what to do for this sprint and the
beta release (as I don't think we can have sufficient time to discuss
the larger design issues): I've been thinking about it for a while,
and would like to propose basically keeping the addZone() interface I
proposed, ignoring the atomicity issue for now.  In fact, if I
read the code correctly, BIND 9's "rndc addzone" has the same issue,
and, unless the administrator tries to add a fully new zone while
keeping BIND 10 already running, this is not an issue in practice.

So I'd like to defer other issues to later discussions.  Whichever
initial approach we take, it's pretty likely to be subject to future
changes anyway.

---
JINMEI, Tatuya