On Fri, 2011-05-13 at 10:24 -0400, Hugh Brock wrote:
On Fri, May 13, 2011 at 10:11:16AM -0400, John R. Dunning wrote:
Another tidbit, which may have gotten lost in the noise, is that we hypothesize the need for a smallish tool to aid "somebody" in creating these service descriptor snippets. A plausible way for such a thing to work would be
- import conf files (and maybe other bits) from some app or rpm
- run augeous (or other parser of your choice) to extract the relevant configurables.
- Present user with lists of same, allow for selecting the ones which want to be settable as part of this new service we're defining. include default values etc.
- wrap the results up into the above-mentioned service metadata snippet.
In the fullness of time, one can easily imagine this tool getting rather more comprehensive, smarter/bigger etc.
Whether said tool would be part of conductor or something else, I don't much care. It seems to me it would be useful to make it standalone, but somebody should think through who's doing that task, and when.
Yeah I think Mark and I agree with you that creating the service is the hard part of this job and probably merits a dedicated tool.
Yep, I think it's crucial.
I'm fine with the metadata describing a service ending up in an XML file.
But if you're authoring a service in puppet, the canonical location of most the metadata should be the puppet manifest IMHO.
So, maybe the template author only needs to list the $enabled parameter in the puppet class and the authoring tool would be responsible for extracting it and putting it in the template XML
Cheers, Mark.