[Openstack-operators] Packaging sample config versions
Fischer, Matt
matthew.fischer at twcable.com
Thu Jan 29 00:55:07 UTC 2015
On 1/28/15, 4:45 PM, "Mathieu Gagné" <mgagne at iweb.com> wrote:
>On 2015-01-28 6:30 PM, Tom Fifield wrote:
>> On 29/01/15 07:28, Thomas Goirand wrote:
>>> On 01/27/2015 11:00 PM, Tom Fifield wrote:
>>>> 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?
>>>
>>> It is not. Since it has been already discuss, but we're still not
>>>having
>>> any counter point of argumentation, I shall repeat myself, until sanity
>>> gets restored.
>>>
>>> You are still *not* addressing the main issue: the .sample config files
>>> *must* match your environment and the version of the different libs on
>>> which a given service is going to run. Therefore, any attempt to go
>>>back
>>> to the previous situation (where we have already pre-built config
>>>files)
>>> can be considered a grave regression.
>>
>> Actually, many folks I spoke to didn't really care about this.
>>
>>
>
>I'm very well aware that configs "exported" by 3rd party libraries might
>not reflect exactly what I have in my own environment. This is a
>downside many operators are willing to accept to get back a simple
>sample config file.
>
>Many operators (myself included, of course) used to rely on the sample
>config file found in the repository of the project and it did a *great*
>job. Now it's gone and all proposed/alternative solutions just doesn't
>cut it for us *operators*, not packagers, developers, etc.
Agreed completely. I know it wpn¹t be 100% perfect, but its 95% and right
now I have 0%.
(please ignore the cruft below)...
This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
More information about the OpenStack-operators
mailing list