[Openstack-operators] Packaging sample config versions

Tom Fifield tom at openstack.org
Tue Jan 27 22:00:06 UTC 2015

Hi all,

Based on Gustavo's excellent work below, talking with many ops, and
after a brief chats with Jeremey and a few other TC folks, here's what
I'd propose as an end goal:

* A git repository that has raw, sample configs in it for each project
that will be automagically updated

* Raw configs distributed in the tar files we make as part of the release

Does that seem acceptable for us all?



On 21/01/15 13:22, gustavo panizzo (gfa) wrote:
> On 12/18/2014 09:57 AM, Jeremy Stanley wrote:
>> 4. Set up a service that periodically regenerates sample
>> configuration and tracks it over time. This attempts to address the
>> stated desire to be able to see how sample configurations change,
>> but note that this is a somewhat artificial presentation since there
>> are a lot of variables (described earlier) influencing the contents
>> of such samples--any attempt to render it as a linear/chronological
>> series could be misleading.
> i've setup a github repo where i dump sample config files for the
> projects that autogenerate them, because i know nothing about rpm build
> tools i only do it for debian and ubuntu packages.
> if you build your deb packages you can use my, very simple and basic,
> scripts to autogenerate the sample config files.
> the repo is here
> https://github.com/gfa/os-sample-configs
> i will happily move to osops or other community repo

More information about the OpenStack-operators mailing list