Open Stack

Sean,

In such case, can we configure which tests should be run for the
python-cinderclient
src job?

Regards,
Ivan Kolodyazhny,
http://blog.e0ne.info/

On Wed, Mar 2, 2016 at 1:45 PM, Sean Dague <sean at dague.net> wrote:

> On 03/02/2016 05:24 AM, Ivan Kolodyazhny wrote:
> > Sean,
> >
> > I do understand why we have tempest for python-cinderclient now.
> >
> > But my point is: tempest runs more than 200 tests per each cinderclient
> > change request which takes a lot of time. Why can't we just introduce
> > few integration tests which will tests nova<=>python-cinderclient API.
> >
> > Also, Nova is not only one consumer of cinderclient. What about Heat? We
> > don't want to break it too but to run all Heat-related Tempest tests is
> > not a good idea. We have to implement integration tests between Heat and
> > python-cinderclient too.
>
> You can add any new tests that you want in additional test jobs.
>
> Cinder can not remove the python-cinderclient src job anytime soon.
> That's table stakes for being part of openstack given how deeply that is
> coupled between Nova / Neutron / Cinder.
>
>         -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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160302/03af5d11/attachment.html>