[openstack-dev] [Fuel][Fuel-library] Using librarian-puppet to manage upstream fuel-library modules
spasquier at mirantis.com
Fri Jul 10 14:22:16 UTC 2015
Alex, could you enable the comments for all on your document?
On Thu, Jul 9, 2015 at 11:07 AM, Bogdan Dobrelya <bdobrelia at mirantis.com>
> > Hello everyone,
> > I took some time this morning to write out a document 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 and let me know if
> > there are any questions.
> > Thanks,
> > -Alex
> > 
> The document is great, Alex!
> I'm fully support the idea to start adapting fuel-library by
> the suggested scheme. The "monitoring" feature of ibrarian looks not
> intrusive and we have no blockers to start using the librarian just
> Best regards,
> Bogdan Dobrelya,
> Irc #bogdando
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev