[openstack-dev] [puppet] [oslo] Proposal of adding puppet-oslo to OpenStack

Emilien Macchi emilien at redhat.com
Tue Jan 19 12:44:38 UTC 2016


Adding [oslo] tag for more visibility.

On 01/19/2016 05:01 AM, Xingchao Yu wrote:
> Hi,  all:
>     Recently I submit some patches for adding rabbit_ha_queues and
> correct the section name of memcached_servers params to each modules,
> then I find I just did repeated things:
>        1. Adding one parameters which related to oslo.*  or authtoken to
> all puppet modules
>        2. Correct section of parameters, move it from deprecated section
> to oslo_* section, apply it on all puppet modules
>      We have more than 30+ modules for now, that means we have to repeat
> 10+ or 20+ times if we want to do a simple change on oslo_* common configs.
>      Besides, the number of oslo_* section is growing, for example : 
>        - oslo_messaging_amqp
>        - oslo_messaging_rabbit
>        - oslo_middleware
>        - oslo_policy
>        - oslo_concurrency
>        - oslo_versionedobjects
>        ...
>     Now we maintain these oslo_* parameters separately in each modules,
>  this has lead some problems:
>     1.  oslo_* params are inconsistent in each modules
>     2.  common params explosion in each modules
>     3.  no convenient way for managing oslo_* params
>     When I was doing some work on keystone::resource::authtoken      
>  (https://review.openstack.org/#/c/266723/)
>     Then I have a idea about adding puppet-oslo project, using a bunch
> of define resources to unify oslo_* configs in each modules.
>     I just write a prototype to show how does it works with oslo.cache:
>     https://github.com/NewpTone/puppet-oslo/blob/master/manifests/cache.pp
>     Please let me know your opinion on the same.

We already talked about this topics during Vancouver Summit:

Real output is documented here:

And I already initiated some code 8 months ago:

At this time, we decided not to go this way because some OpenStack
projects were not using the same version of oslo.*. sometimes.
So it could have lead to something like:
"nova using newest version of oslo messaging parameters comparing to
murano" (that's an example, probably wrong...), so puppet-oslo would
have been risky to use here.
I would like to know from Oslo folks if we can safely configure Oslo
projects the same way during a cycle (Ex: Mitaka, then N, etc) or if
some projects are using too old versions of Oslo that makes impossible a
consistent configuration across all OpenStack projects.

So indeed, I'm still convinced this topic should be brought alive again.
We would need to investigate with Oslo team if it makes sense and if we
can safely do that for all our modules.
If we have positive feedback, we can create the new module and
refactorize our modules that will consume puppet-oslo.
It will help a lot in keeping our modules consistent and eventually drop
a lot of duplicated code.


>     Thanks & Regards.
> -- 
>  Xingchao Yu
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Emilien Macchi

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160119/7326cb47/attachment.pgp>

More information about the OpenStack-dev mailing list