Open Stack

On Wed, Nov 29, 2017 at 2:28 PM Peng Liu <pliu at redhat.com> wrote:

> Hi Team,
>
> Hi Peng


> I have a question regarding to the API coverage of Patrole. Currently,
> Patrole as a Tempest plugin heavily relys on the Tempest code. However,
> Tempest only contains the API tests for the most common APIs of the most
> common projects(Nova, Neutron, Cinder, Glance, Swift, Keystone).
>
> So I want to know if it is possible to extend Patrole to:
> 1) test the APIs of the common projects which was not yet covered in
> Tempest.
>
2) test projects which was not covered in Tempest?
>

You can use the Patrole framework to test services not covered by Tempest
by taking advantage of Tempest plugin mechanism.
Patrole itself is a Tempest plugin. If you install the plugin of a service
that includes a service client, you should be able to use it to write
Patrole tests for that service.
I believe this has not been done yet by any project though, so there may be
a few technical bits to be sorted out.

I don't think Patrole itself will have to be extended, however Patrole does
not yet include stable APIs.
If you're going to use Patrole APIs in your project you need to be aware
that there may be backward incompatible changes happening without a
deprecation period.

There are several options on where to host such tests: in a dedicated
plugin, in the Tempest plugin for the service or in Patrole itself.
The latter would probably suffer from the same scalability issues that lead
us to create the plugin mechanism to begin with.

Andrea Frittoli (andreaf)


>
> Thanks,
> --
> Peng Liu
> __________________________________________________________________________
> 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/20171129/5f5734c6/attachment.html>