[bind10-dev] Handling regressions due to #213

[Michal 'vorner' Vaner]

Hello

Currently, the #213 is in review (it's the configuration for boss ticket).
However, it turned out quite big already and there are few things to do, some of
them are annoying regressions. The most annoying parts are:

• The brittle mode is gone. We might want to return it or not, as the new way of
  configuration allows admin to specify all components as core, which in turn
  will mean if they die, the whole system goes down. It's just more work to do,
  as the configuration is not global, but per-component and isn't per one run of
  boss.
• The delayed restart is gone, it restarts right away. If there's a problem why
  it can't start, it loops.
• The bindctl handling of named_set isn't the best possible, which means it's
  quite hell to figure out how to configure it.
• No user docs. At all.

I believe these are problematic enough not to give it to users this way. So
there are actually three ways to solve it, each one having some pros and cons,
so I'd like to discuss what should we do about them:
• Act as nothing usual happens, just merge the branch once it's reviewed
  properly, create tickets for them and hope we solve them before release. This
  will pose little problem for us few developers, but we can handle the small
  inconvenience of doing the configuration the hard way.
• Fix it inside the branch, before being merged. It may grow too big, and not
  many people can work on it in parallel.
• Branch from that branch, and merge it back to master once they are solved.
  There could be a problem of the branch growing big (like the resolver one a year
  ago), but nothing else probably will touch boss in the meantime, so there should
  be no collisions, and we could merge master into this branch once every week or
  so to keep it up to day and not have all the collisions at once. The merge back
  should be smooth then.

For myself, I actually prefer the third option.

Thanks for your opinions.

-- 
BOFH Excuse #452:
Somebody ran the operating system through a spelling checker.

Michal 'vorner' Vaner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <https://lists.isc.org/pipermail/bind10-dev/attachments/20111021/0af23ee9/attachment.bin>