<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Mar 26, 2014 at 11:53 PM, Michael Chapman <span dir="ltr"><<a href="mailto:woppin@gmail.com" target="_blank">woppin@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div><div class="h5"><div class="gmail_quote">On Thu, Mar 27, 2014 at 4:10 PM, Robert Collins <span dir="ltr"><<a href="mailto:robertc@robertcollins.net" target="_blank">robertc@robertcollins.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>On 27 March 2014 17:30, Tom Fifield <<a href="mailto:tom@openstack.org" target="_blank">tom@openstack.org</a>> wrote:<br>
<br>
>> Does anyone disagree?<br>
><br>
> /me raises hand<br>
><br>
> When I was an operator, I regularly referred to the sample config files<br>
> in the git repository.<br>
><br>
> If there weren't generated versions of the sample config in the repo, I<br>
> would probably grep the code (not an ideal user experience!). Running<br>
> some random script that I don't know about the existence and might<br>
> depend on having something else installed of is probably not something<br>
> that would happen.<br>
<br>
</div>So, I think its important you have sample configs to refer to.<br>
<br>
Do they need to be in the git repo?<br>
<br>
Note that because libraries now export config options (which is the<br>
root of this problem!) you cannot ever know from the source all the<br>
options for a service - you *must* know the library versions you are<br>
running, to interrogate them for their options.<br>
<br>
We can - and should - have a discussion about the appropriateness of<br>
the layering leak we have today, but in the meantime this is breaking<br>
multiple projects every time any shared library that uses oslo.config<br>
changes any config option... so we need to solve the workflow aspect.<br>
<br>
How about we make a copy of the latest config for each project for<br>
each series - e.g. trunk of everything, Icehouse of servers with trunk<br>
of everything else, etc and make that easily acccessible?<br>
<br>
-Rob<br>
<span><font color="#888888"><br>
--<br>
Robert Collins <<a href="mailto:rbtcollins@hp.com" target="_blank">rbtcollins@hp.com</a>><br>
Distinguished Technologist<br>
HP Converged Cloud<br>
</font></span><div><div><br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br></div></div></blockquote><div><br><br></div></div></div>
</div>There are already some samples in the 'configuration reference' section of docs.openstack, eg:<br>
<br><a href="http://docs.openstack.org/havana/config-reference/content/ch_configuring-openstack-identity.html#sample-configuration-files" target="_blank">http://docs.openstack.org/havana/config-reference/content/ch_configuring-openstack-identity.html#sample-configuration-files</a><br>
<br></div><div class="gmail_extra">However the compute and image sections opt for a formatted table, and the network section is more like an installation guide.<br><br></div><div class="gmail_extra">If the samples are to be removed from github, perhaps our configuration reference section could be first and foremost the set of sample configuration files for each project + plugin, rather than them being merely a part of the reference doc as it currently exists.<br>
<br></div><div class="gmail_extra">I fairly consistently refer to the github copies of the samples. They also allow me to refer to specific lines of the config when explaining concepts over text. I am not against their removal, but if we were to remove them I'd disappointed if I had to search very far on <a href="http://docs.openstack.org" target="_blank">docs.openstack.org</a> to get to them, and I would want the raw files instead of something formatted.</div>
</div></blockquote><div><br></div><div>++, This sounds like a good approach, If we make the config samples very easy to find on <a href="http://docs.openstack.org">docs.openstack.org</a> and make them automatically regenerate to be up to date then the workflow for everyone who used to use the in tree samples only changes slightly, just look at at new website for the same thing.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><span class="HOEnZb"><font color="#888888"><br>
</font></span></div><span class="HOEnZb"><font color="#888888"><div class="gmail_extra"><br></div><div class="gmail_extra"> - Michael<br></div></font></span></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>