[openstack-dev] [cinder] 3.rd Party CI requirements for compliance

Sean McGinnis sean.mcginnis at gmx.com
Wed Mar 2 19:59:14 UTC 2016

On Wed, Mar 02, 2016 at 06:14:30PM +0000, Indra Harijono wrote:
> Hi,
> I am new in this forum and openstack dev. so please my sincere apology if I submitted stupid (redundant) questions.
> I am writing this to clarify cinder compliance requirements (and 3.rd Party CI Testing).
> We are developing storage appliance and would like to run cinder on it.
> We don't directly modify API but change the underlying (volume provisioning) mechanisms.
> -          Do we need to set up 3.rd party CI for the compliance?
> -          If yes, do other needs full product level documentation (such as specs etc.)?
> -          How long would it be necessary to provide such 3.rd party CI system for others, or does the CI setup mean
> to be permanently used to check compliance each time openstack code is modified?
> Any comments, suggestions and feedback are highly appreciated.
> Thanks,
> Indra

If I'm understanding this correctly, you are not looking to provide a
driver or modify the cinder code in any way. You are just looking at
delivering a Cinder "appliance" that can be used in an OpenStack cloud.
Is that correct?

If that is the case, we don't really have any kind of certification
process for that type of thing. You could certainly use our third party
CI testing process for Cinder volume drivers to show that everything is
in compliance with expected behavior, but that would be up to you. There
is documentation on [1]. You can also ask questions on the
#openstack-cinder IRC channel.

If you go that route, I would recommend running it permanently. The big
value with setting up CI is being able to quickly identify breaking
changes. Passing the tests just a few times wouldn't necessarily mean
everything is working correctly down the road.

Sean (smcginnis)

[1] https://wiki.openstack.org/wiki/Cinder/how-to-contribute-a-driver

More information about the OpenStack-dev mailing list