[neutron][interop][refstack] New tests and capabilities to track in interop
Slawek Kaplonski
skaplons at redhat.com
Tue Apr 27 20:02:52 UTC 2021
Hi,
Dnia wtorek, 27 kwietnia 2021 21:38:03 CEST Ghanshyam Mann pisze:
> ---- On Tue, 27 Apr 2021 14:33:12 -0500 Kanevsky, Arkady
<Arkady.Kanevsky at dell.com> wrote ----
>
> > Agree. But can we run both tempest and project plug-ins together for the
same project?
>
> Yes, we can run. There is no restriction on that, we can provide regex
matching those tests in Tempest run CLI or tox commands.
Great news for us as we don't need to move the tests to tempest :) Thx.
>
> -gmann
>
> > -----Original Message-----
> > From: Ghanshyam Mann <gmann at ghanshyammann.com>
> > Sent: Tuesday, April 27, 2021 1:15 PM
> > To: Martin Kopec
> > Cc: openstack-discuss; Kanevsky, Arkady; Slawek Kaplonski
> > Subject: Re: [neutron][interop][refstack] New tests and capabilities to
track in interop
> >
> >
> > [EXTERNAL EMAIL]
> >
> > ---- On Mon, 26 Apr 2021 10:48:08 -0500 Martin Kopec <mkopec at redhat.com>
wrote ---- > Hi everyone, > I would like to further discuss the topics we
> > covered with the neutron team during > the PTG [1]. >
> > > * adding address_group API capability > It's tested by tests in
neutron-tempest-plugin. First question is if tests which arenot directly in
tempest can
> > > be a part of a non-add-on marketing program?It's possible to move them
to tempest though, by the time we do so, could they be > marked as advisory?
> > >
> > > * Shall we include QoS tempest tests since we don't know what share of
vendorsenable QoS? Could it be an add-on?These tests are also in
> > > neutron-tempest-plugin, I assume we're talking
aboutneutron_tempest_plugin.api.test_qos tests.If we want to include these
tests, which program should
> > > they belong to? Do we wannacreate a new one? >
> > I remember the discussion on the location of tests required by the
interop group 2-3 years back (when heat and dns adds-on were added).
> > We all agreed that having tests in tempest plugins is all fine, they do
not need to be in Tempest as such. That is why heat and dns or now manila
tests
> > stays in their respective plugins.
> >
> > For neutron also, as there are existing neutron tempest plugin tests we
do not need to move them to Tempest and refstack can run it from
> > neutron-tempest-plugin, if we do move then we might break existing
upstream or downstream testing scripts running those existing tests from the
current
> > location.
> >
> > -gmann
> >
> > > [1]
> > > https://urldefense.com/v3/__https://etherpad.opendev.org/p/neutron-xena-ptg__;!!LpKI!0kxKX2qrtBJop9NFWHvzlJvzFwY4C6P03O-TIqKkamqKSeW9X3rXyDwB2sttrJmqnh
> > > 5M$ [etherpad[.]opendev[.]org] > > Thanks, > -- > Martin Kopec >
Senior Software Quality Engineer > Red Hat EMEA > > > > > >
--
Slawek Kaplonski
Principal Software Engineer
Red Hat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20210427/0342b0f4/attachment-0001.sig>
More information about the openstack-discuss
mailing list