[bind10-dev] Config snapshots in git

[Mukund Sivaraman]

Hi Michal

On Thu, Sep 05, 2013 at 01:05:07PM +0200, Michal 'vorner' Vaner wrote:
> This gives a complete history to the user, not just some numbers. I think it is
> simple to implement (I did some equivalents in several CGI scripts where I
> wanted to keep track of history). The only disadvantage is we need git on the
> machine, but we could make it configurable (even runtime-configurable). If user
> wanted to turn this on, git would be required, but otherwise it would not be
> needed.
> 
> What do you think?

I agree that having version numbers in the file would not be desirable.

On git support, I feel this is something that we should not directly
have in BIND 10. If the admin wants to maintain their config in git,
they could do it externally.

If we use git, here are a few points:

* Pretty printing the JSON would be nice. Currently we write out the
  b10-config.db as a single line and it's not simple to edit it (which
  is even discouraged but we do this for lettuce tests, etc.), or do a
  diff against a copy from a different time.

* Instead of calling out to command line programs, we can use a library
  for git instead.

* We don't advise the config db file to be edited directly, but ask for
  users to use bindctl. So what support are we going to have in bindctl
  to see differences from previous versions, or restore previous
  versions?

* Even if we version files, what purpose is the choice of git going to
  solve? The .db files are really small, and we could simply copy it to
  a backup file. If the user is supposed to run the git tools to view
  history, etc. they can also use git add, git commit, etc. without any
  support from BIND 10.

		Mukund
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 2881 bytes
Desc: not available
URL: <https://lists.isc.org/pipermail/bind10-dev/attachments/20130905/d22ed05c/attachment.bin>