[openstack-dev] [devstack] [third-party] how to use a devstack external plugin in gate testing

Chmouel Boudjnah chmouel at enovance.com
Thu Feb 12 11:33:55 UTC 2015


Jaume Devesa <devvesa at gmail.com> writes:

> Following the conversation...
>
> We have seen that glusterfs[1] and ec2api[2] use different approach
> when it comes to repository managing: whereas glusterfs is a single
> 'devstack' directory repository, ec2api is a whole project with a
> 'devstack' directory on it.
>
> We plan to migrate 'python-neutron-plugin-midonet'[3] project to
> Stackforge too. It makes sense to add the 'devstack' directory on it?
> Or do you recommend us to have two different repositories in
> Stackforge: one for the neutron plugin and the other one for the
> devstack plugin?

as you stated I don't think there is a clear advantage or disadvantage
but IMO having too many repositories is not very user friendly and I would
recommend to have the plugin directly in the repo.

For things like glusterfs which is not a native openstack project it
makes sense that the plugin is hosted externally of the project.

Chmouel



More information about the OpenStack-dev mailing list