Open Stack

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.

FWIW - Over in Infra we also have a giant pile of external modules we
use. We looked at and chose not to use librarian because of complexity
and also fragility.

Instead, we wrote a simple script and a simple manifest file:

http://git.openstack.org/cgit/openstack-infra/system-config/tree/modules.env

http://git.openstack.org/cgit/openstack-infra/system-config/tree/install_modules.sh

Feel free to make use of that if it's helpful.