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

Jaume Devesa devvesa at gmail.com
Thu Feb 12 11:10:33 UTC 2015


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

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?

We can not see any big advantage or disadvantage in any of them... so
we have decided to ask to the community if someone is able see what we
can not see.

Regards,

[1]: https://github.com/stackforge/devstack-plugin-glusterfs
[2]: https://github.com/stackforge/ec2-api
[3]: https://github.com/midonet/python-neutron-plugin-midonet

El 11/02/15 a las 17:43, Jaume Devesa escribió:
> Hello,
> 
> I'm working in the same job as Kyle for the midonet plugin, but
> first I need to do some changes in devstack. (Sean's review on my
> patch[1] has lead me to this conversation).
> 
> After talking with Lucas, (Midokura's responsible of Third-party 
> testing), we have a question about this that involve the
> third-party folks: if we get our own Jenkins job that tests
> devstack with midonet and we include this job in the Neutron's gate
> (as non-voting, of course), that would be considered Neutron
> Third-party testing?
> 
> Can we chat about this on next Monday's third party meeting?
> 
> Regards,
> 
> [1]: https://review.openstack.org/#/c/152876
> 
> El 06/02/15 a las 22:54, Kyle Mestery escribió:
>> On Fri, Feb 6, 2015 at 1:36 PM, Sean Dague <sean at dague.net>
>> wrote:
> 
>>> For those that didn't notice, on the Devstack team we've
>>> started to push back on new in-tree support for all the
>>> features. That's intentional. We've got an external plugin
>>> interface now -
>>> 
>>> http://docs.openstack.org/developer/devstack/plugins.html#externally-hosted-plugins
>>>
>>>
>>>
>
>>> 
,
>>> and have a few projects like the ec2api and glusterfs that are
>>>  successfully using it. Our Future direction is to do more of 
>>> this - https://review.openstack.org/#/c/150789/
>>> 
>>> The question people ask a lot is 'but, how do I do a gate job 
>>> with the external plugin?'.
>>> 
>>> Starting with the stackforge/ec2api we have an example up on
>>> how to do that: https://review.openstack.org/#/c/153659/
>>> 
>>> The important bits are as follows:
>>> 
>>> 1. the git repo that you have your external plugin in *must* be
>>>  in gerrit. stackforge is fine, but it has to be hosted in the
>>>  OpenStack infrastructure.
>>> 
>>> 2. The job needs to add your PROJECT to the projects list,
>>> i.e.:
>>> 
>>> export PROJECTS="stackforge/ec2-api $PROJECTS"
>>> 
>>> 3. The job needs to add a DEVSTACK_LOCAL_CONFIG line for the 
>>> plugin enablement:
>>> 
>>> export DEVSTACK_LOCAL_CONFIG="enable_plugin ec2-api 
>>> git://git.openstack.org/stackforge/ec2-api"
>>> 
>>> Beyond that you can define your devstack job however you like. 
>>> It can test with Tempest. It can instead use a post_test_hook 
>>> for functional testing. Whatever is appropriate for your 
>>> project.
>>> 
>>> This is awesome Sean! Thanks for the inspiration here. In
>>> fact, I just
>> pushed a series of patches [1] [2] which do the same for the 
>> networking-odl stackforge project.
> 
>> Thanks, Kyle
> 
>> [1] https://review.openstack.org/#/c/153704/ [2] 
>> https://review.openstack.org/#/c/153705/
> 
>> -Sean
>>> 
>>> -- Sean Dague http://dague.net
>>> 
>>> __________________________________________________________________________
>>>
>>>
>>>
>
>>> 
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
>>>
>
>>> 
>>> 
>>> 
> 
> 
>> __________________________________________________________________________
>
>> 
> 
> 
> 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
>
>> 
> 
> 

- -- 
Jaume Devesa
Software Engineer, Midokura
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJU3IopAAoJEPvO/ogkgqHBRRIP/0PcoPvFBBOg+TdWLGQFS7jf
4cgPe+PAnUFUtaEn78YTYSp5UkK6TzDEA9I0TqD88a2MK7rP+x0XAxtlTBRpIB0s
AbSIJd6Eg0GCnqdPxztzeRcxagr+oTSys79cYd49JWMBfUYgCDjdQBYHq5IacvgM
PG/8EiHWdQAo1nmxXQhy18p7+nMnntt0BBkLBwFPFmo/QnjCqveN0bvHSCcIhLRv
heVnK/clvPzeyx+5tRT67dEmaP0X+xtSdA2Y/HNJIwUl1m6Z6L9JwIyuffHi/py5
GUxScogIHjids4i9IU+EmO/ltrfwZ/Kad5EjareSSPenvuv0Bk78RiYGUhBjvwdw
CrnlK6fCq5SACtw47kgWMyc1UM+Y5gIw/DguX1eQjaKXtr2Mzp0ij4p/Swi5Meo+
Q09tsKbcNWKDtDUiwmKWTkuhe1+V3iYwLARivs7DygthHWaAs2JnDwPiLO/L07i/
dGVel6hrwsHmIJGafLyxGD8pVeFcIHOx0Bc8/AxzybH8Un8kokwNmTMqfZwthWOK
Az61ofATI53+lDy6jo9ilcm1FNifuUhOekRJqBhyEzJqd5ZZwtGCI1sJv5YGanA/
GYAFGPP0noL+nnavQoEbIjrlurXrYX7Rb5AZT643KSuerMy29J7ReChcuV9olkZd
bqQ3f1PqIv/ZUx+qVvHu
=45Da
-----END PGP SIGNATURE-----



More information about the OpenStack-dev mailing list