[OpenAFS] managing BosConfig in Puppet

[Ken Dreyer]

On Sat, Nov 17, 2012 at 7:55 AM, Jeff Blaine <jblaine@kickflop.net> wrote:
> Ken, I recommend establishing templates for a generalized file server
> and DB server, then passing in the desired parameters per host
> over time as you see fit. Most easily done, take existing BosConfig
> files (copy) and change the obvious pieces to variable references
> to make templates for use. Use paramterized classes to "instan-
> tiate" the right thing per node.

Thanks. I'm curious if you've implementing something like this in
production, and in particular, how you handle reloading the bos
server, since it will always rename the BosConfig.new file to
BosConfig?

I would agree with you about templating if this were a normal system
daemon. My concern is that BosConfig is quite opaque. I want to avoid
re-implementing ReadBozoFile() and WriteBozoFile() in Puppet or Ruby
:) The way AFS treats BosConfig seems more like a database to me and
less like a typical /etc configuration file.

- Ken