Thanks for the comments.
I think the solution from #2 (https://bugs.launchpad.net/neutron/+bug/2017023/comments/2) can be a way forward, keep the APIs in Nova (keep the min. microversion), keep the tests in Tempests, but execute those tests from a "nova-only" job, and change the jobs of other projects to exclude those tests and use the tests which we have in tempest/api/network/test_security_groups.*.py.
What is important to check what we have in tempest/api/network/test_security_group.*.py provides the same coverage as the tests in compute/security_groups.
Or is it enough if we say that we have now up-to-date scenario tests in tempest for security-groups?
By-the-way: the same is true for tempest/compute/floating_ips
Thanks for the comments. /bugs.launchpad .net/neutron/ +bug/2017023/ comments/ 2) can be a way forward, keep the APIs in Nova (keep the min. microversion), keep the tests in Tempests, but execute those tests from a "nova-only" job, and change the jobs of other projects to exclude those tests and use the tests which we have in tempest/ api/network/ test_security_ groups. *.py.
I think the solution from #2 (https:/
What is important to check what we have in tempest/ api/network/ test_security_ group.* .py provides the same coverage as the tests in compute/ security_ groups.
Or is it enough if we say that we have now up-to-date scenario tests in tempest for security-groups?
By-the-way: the same is true for tempest/ compute/ floating_ ips