Open Stack

Hi,

Dnia poniedziałek, 26 kwietnia 2021 17:48:08 CEST Martin Kopec pisze:
> 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 are
> not 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
> vendors
> enable QoS? Could it be an add-on?
> These tests are also in neutron-tempest-plugin, I assume we're talking about
> neutron_tempest_plugin.api.test_qos tests.
> If we want to include these tests, which program should they belong to? Do
> we wanna
> create a new one?
> 
> [1] https://etherpad.opendev.org/p/neutron-xena-ptg
> 
> Thanks,
> --
> Martin Kopec
> Senior Software Quality Engineer
> Red Hat EMEA

First of all, sorry that it took so long for me but I finally looked into Neutron related tests 
and capabilities and I think we can possibly add few things there:

- For "networks-security-groups-CRUD" we can add "address_groups" API. It is now 
supported by ML2 plugin [1]. In the neutron-tempest-plugin we just have some scenario 
test [2] but we would probably need also API tests for that, correct?

- For networks-l3-CRUD we can optionally add port_forwarding API. This can be added by 
service plugin [3] so it may not be enabled in all deployments. But maybe there is some 
"optional feature" category in the RefStack, and if so, this could be included there. Tests 
for that are in neutron-tempest-plugin [4] and [5].

- There are also 2 other service plugins, which I think could be included as "optional 
feature" in the RefStack, but IMO don't fit exactly in any of the existing groups. Those are 
QoS [6] and Trunks [7]. Tests for both are in the neutron-tempest-plugin as well: Qos: [8] 
and [9], Trunk [10], [11] and [12].

Please let me know what do You think about it and if that would be ok and if You want me 
to propose some patches with that or maybe You will propose them.

[1] https://review.opendev.org/c/openstack/neutron-lib/+/741784[1]
[2] https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/777833[2]
[3] https://github.com/openstack/neutron/blob/master/neutron/services/portforwarding/
pf_plugin.py[3]
[4] https://github.com/openstack/neutron-tempest-plugin/blob/master/
neutron_tempest_plugin/api/test_port_forwardings.py[4]
[5] https://github.com/openstack/neutron-tempest-plugin/blob/master/
neutron_tempest_plugin/api/test_port_forwarding_negative.py[5]
[6] https://github.com/openstack/neutron/blob/master/neutron/services/qos/
qos_plugin.py[6]
[7] https://github.com/openstack/neutron/blob/master/neutron/services/trunk/
plugin.py[7]
[8] https://github.com/openstack/neutron-tempest-plugin/blob/master/
neutron_tempest_plugin/api/test_qos.py[8]
[9] https://github.com/openstack/neutron-tempest-plugin/blob/master/
neutron_tempest_plugin/api/test_qos_negative.py[9]
[10] https://github.com/openstack/neutron-tempest-plugin/blob/master/
neutron_tempest_plugin/api/test_trunk.py[10]
[11] https://github.com/openstack/neutron-tempest-plugin/blob/master/
neutron_tempest_plugin/api/test_trunk_details.py[11]
[12] https://github.com/openstack/neutron-tempest-plugin/blob/master/
neutron_tempest_plugin/api/test_trunk_negative.py[12]

-- 
Slawek Kaplonski
Principal Software Engineer
Red Hat

--------
[1] https://review.opendev.org/c/openstack/neutron-lib/+/741784
[2] https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/777833
[3] https://github.com/openstack/neutron/blob/master/neutron/services/portforwarding/
pf_plugin.py
[4] https://github.com/openstack/neutron-tempest-plugin/blob/master/
neutron_tempest_plugin/api/test_port_forwardings.py
[5] https://github.com/openstack/neutron-tempest-plugin/blob/master/
neutron_tempest_plugin/api/test_port_forwarding_negative.py
[6] https://github.com/openstack/neutron/blob/master/neutron/services/qos/
qos_plugin.py
[7] https://github.com/openstack/neutron/blob/master/neutron/services/trunk/plugin.py
[8] https://github.com/openstack/neutron-tempest-plugin/blob/master/
neutron_tempest_plugin/api/test_qos.py
[9] https://github.com/openstack/neutron-tempest-plugin/blob/master/
neutron_tempest_plugin/api/test_qos_negative.py
[10] https://github.com/openstack/neutron-tempest-plugin/blob/master/
neutron_tempest_plugin/api/test_trunk.py
[11] https://github.com/openstack/neutron-tempest-plugin/blob/master/
neutron_tempest_plugin/api/test_trunk_details.py
[12] https://github.com/openstack/neutron-tempest-plugin/blob/master/
neutron_tempest_plugin/api/test_trunk_negative.py
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20210524/543bffbc/attachment.html>
-------------- 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/20210524/543bffbc/attachment.sig>