<div dir="ltr">Hi Xingchao,<div><br></div><div>I think 'puppet-openstacklib' is designed to solve the issue with code duplication. I don't see any strong reason why we should use a puppet-oslo instead.</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr">--<br>
Best regards,<br>
Sergii Golovatiuk,<br>
Skype #golserge<br>
IRC #holser<br></div></div></div>
<br><div class="gmail_quote">On Tue, Jan 19, 2016 at 3:42 PM, Bogdan Dobrelya <span dir="ltr"><<a href="mailto:bdobrelia@mirantis.com" target="_blank">bdobrelia@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 19.01.2016 11:01, Xingchao Yu wrote:<br>
> Hi, all:<br>
><br>
> Recently I submit some patches for adding rabbit_ha_queues and<br>
> correct the section name of memcached_servers params to each modules,<br>
> then I find I just did repeated things:<br>
><br>
> 1. Adding one parameters which related to oslo.* or authtoken to<br>
> all puppet modules<br>
> 2. Correct section of parameters, move it from deprecated section<br>
> to oslo_* section, apply it on all puppet modules<br>
><br>
> We have more than 30+ modules for now, that means we have to repeat<br>
> 10+ or 20+ times if we want to do a simple change on oslo_* common configs.<br>
><br>
> Besides, the number of oslo_* section is growing, for example :<br>
><br>
> - oslo_messaging_amqp<br>
> - oslo_messaging_rabbit<br>
> - oslo_middleware<br>
> - oslo_policy<br>
> - oslo_concurrency<br>
> - oslo_versionedobjects<br>
> ...<br>
><br>
> Now we maintain these oslo_* parameters separately in each modules,<br>
> this has lead some problems:<br>
><br>
> 1. oslo_* params are inconsistent in each modules<br>
> 2. common params explosion in each modules<br>
> 3. no convenient way for managing oslo_* params<br>
><br>
> When I was doing some work on keystone::resource::authtoken<br>
> (<a href="https://review.openstack.org/#/c/266723/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/266723/</a>)<br>
><br>
> Then I have a idea about adding puppet-oslo project, using a bunch<br>
> of define resources to unify oslo_* configs in each modules.<br>
><br>
> I just write a prototype to show how does it works with oslo.cache:<br>
><br>
> <a href="https://github.com/NewpTone/puppet-oslo/blob/master/manifests/cache.pp" rel="noreferrer" target="_blank">https://github.com/NewpTone/puppet-oslo/blob/master/manifests/cache.pp</a><br>
><br>
> Please let me know your opinion on the same.<br>
<br>
</div></div>I liked the idea very much! And the oslo.cache PoC looks simple and elegant.<br>
<span class=""><br>
><br>
> Thanks & Regards.<br>
><br>
> --<br>
> Xingchao Yu<br>
><br>
><br>
><br>
><br>
</span><span class="">> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
<br>
<br>
--<br>
</span>Best regards,<br>
Bogdan Dobrelya,<br>
Irc #bogdando<br>
<div class="HOEnZb"><div class="h5"><br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div>