[openstack-dev] [Fuel][Fuel-library] Using librarian-puppet to manage upstream fuel-library modules

Aleksandr Didenko adidenko at mirantis.com
Thu Jun 25 14:21:56 UTC 2015


Hi,

just wanted to mention another tool to work with 'Puppetfile' - r10k:

https://github.com/puppetlabs/r10k/blob/master/doc/puppetfile.mkd

Regards,
Alex

On Wed, Jun 24, 2015 at 11:04 PM, Paul Belanger <pabelanger at redhat.com>
wrote:

> On 06/23/2015 01:51 PM, Alex Schultz wrote:
>
>> Hello everyone,
>>
>> I took some time this morning to write out a document[0] that outlines
>> one possible ways for us to manage our upstream modules in a more
>> consistent fashion. I know we've had a few emails bouncing around
>> lately around this topic of our use of upstream modules and how can we
>> improve this. I thought I would throw out my idea of leveraging
>> librarian-puppet to manage the upstream modules within our
>> fuel-library repository. Ideally, all upstream modules should come
>> from upstream sources and be removed from the fuel-library itself.
>> Unfortunately because of the way our repository sits today, this is a
>> very large undertaking and we do not currently have a way to manage
>> the inclusion of the modules in an automated way. I believe this is
>> where librarian-puppet can come in handy and provide a way to manage
>> the modules. Please take a look at my document[0] and let me know if
>> there are any questions.
>>
>>  I'd suggest looking at librarian-puppet-simple over librarian-puppet.  I
> found the dependency management terrible with librarian-puppet.  The more
> complex your puppet dependencies became, the longer the tooling took to run.
>
> Mine you this was a few years ago.
>
> PB
>
>
>
> __________________________________________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150625/a1c2e9ef/attachment.html>


More information about the OpenStack-dev mailing list