From: "Hugh Brock" hbrock@redhat.com Date: Fri, 13 May 2011 10:24:47 -0400
[...]
> > To my mind, the single most important piece of the implementation of > services at launch time, is the API between the set of stuff coming > down from confserv and the stuff which picks it up in the booting > instance. If that's solid, and *isn't* explicitly puppet-centric, > that leaves the door open for people to pick up and run with those > parameters in their instance, using whatever tools they prefer.
Has this API been described by anyone yet?
"Vector of keyword/value pairs, stored in one or more files".
I confess I'm left wondering why we wouldn't use Puppet's API, which is well developed, for this by default, maybe with some provision that says OK later on we'll provide a way for you to use a different tool of your choice.
It's easy to map from vector of k/v pairs to puppet, hard to map the other way. If we set the precedent up front that it's puppet, that will become cast in concrete, and we'll never change it. I'd *really* like to avoid that.