The patch changes status of the 2022.06 guidelines to approved
and updates symlinks so that they point to the latest guideline
versions.
Change-Id: Ib9840586c55e034bc31b3146bfa69afe36560d2e
The following capabilities are moved from advisory to required:
Compute platform:
identity-v3-list-versions
identity-v3-application-credentials
identity-v3-users
identity-v3-domains
volumes-v3-snapshots-list
compute-images-create
compute-servers-resize
compute-servers-tags-CRUD
compute-servers-tags-tag-CRUD
networks-security-groups-CRUD-2
networks-dhcp
networks-floating-ips-CRUD
images-v2-import
Storage platform:
objectstore-account-update
objectstore-bulk
The following capabilities in the Compute program are moved from
required to deprecated, due to [1]:
compute-servers-metadata-delete
compute-servers-metadata-get
compute-servers-metadata-list
compute-servers-metadata-set
compute-servers-metadata-update
[1] https://review.opendev.org/c/openstack/tempest/+/749527
Change-Id: Ic9337eac8c0883be7908ee438790225df46a81fa
The patch converts the 2021.11 guidelines to a .rst file so that
it can be included in the documentation.
The patch also fixes a few links pointing to the old interop
namespace (osf/) - seems like we accidentally reverted some of the
changes.
Apart from that the patch unifies target_approval format for
shared_file_system add-on so that it matches the format of other
add-ons.
The patch then copies all 2021.11 files to their "next" versions so
that we can build a new guideline on the top of the previous one.
Change-Id: I1dea3743ca6bf657313299177aabe69ddf234784
Changing status of the newest guidelines to approved, updating
symlinks so that they point to the latest guidelines and fixing
a typo in one of the tests.
Change-Id: I5561b91acaf36cd9f1bf18e80f3882a25fa34bca
Includes recommendations from Nova:
* move compute_image_create and compute_server_resize to advisory
since they are ironic dependent
* add compute_servers_tags CRUD and compute_servers_tags_tag_CRUD
advisory
* remove compute_images API from advisory since they are depricated
Change-Id: I9c700bd15909d9f58b25ee51546916d92fe88fdc
The test_create_all_recordset_types test from designate-tempest-plugin
represents series of tests. The series of tests is produced by ddt
library. The issue is that each of the tests has the same idempotent
id.
Also, tests produced by ddt have inconsistent naming. It may
happen that at two different systems the same test gets two different
names.
The test should remain flagged until [1] is resolved.
[1] https://bugs.launchpad.net/designate/+bug/1943115
Change-Id: I437dae576c54811db6a924c8f5f613ab96e6a392
When Tempest loads tests class inheritance plays a big role,
the test name (or path if you will) is affected by the inherited
classes.
ShareNetworksTest class inherits from ShareNetworkListMixin,
see [1], therefore the test in questions appears to be under
ShareNetworksTest and not ShareNetworkListMixin which is its
litteral position.
This issue wasn't uncovered by the consistency checks
because tools/checktest.py parses test files manually and
therefore the check passed as it found the litteral position
of the test not the based on the inheritance.
[1] 8ccbbebe6d/manila_tempest_tests/tests/api/test_share_networks.py
Change-Id: I685d94d045f4c20cfb9430d200b52e1c5cf4d268
Reorganize guidelines into guidelines directory and create
current_guideline that is softlink to the latest approved guideline.
The same with add-ons guidelines - they are moved to guidelines
directory within add-ons one and soft links are created pointing
to the latest guidelines for each add-on.
Also cleaned up some tooling that hardwired where guidelines lived.
Change-Id: I5ad4b91b1afb44a0a6987b339f7efba14f395302
Adds a job which runs all next tests on a devstack master and
experimental jobs which run the same on supported stable releases.
Fix names of a few manila_tempest_tests and designate_tempest_plugin
tests so that they match the names from the plugins.
Change-Id: Iedbaa09e425a29156304eea63b66a1ce69dd77bd
All of the tests defined in the guidelines should be prefixed by
"id-" for 2 reasons:
1. it's a pattern which has been already set with tempest tests -
ids of tempest's tests aren't prefixed with "id-" in tempest,
however, they are in the guidelines.
2. tools/consistency.sh will fail otherwise - tools/checktest.py
adds the prefix to every discovered test [1] - due to the fact
number 1. (although I'm not sure what was first and why the
uuids are prefixed in the first place). If the uuids in
a guideline aren't prefixed, the consistency check will fail.
[1] 23ad4511bb/tools/checktests.py (L116)
Change-Id: I3b7390124b00d65b77b45e1f8c438fd243794210
Reorganize guidelines into previous_guideline directory
and current_guideline that is softlink to the latest approved guideline.
Cleaned up some tooling that hardwired where guidelines lived.
Change-Id: Ia6be9ca6326718488ee5668df3806da5f76dc456
Not all backends support shrinking shares, f.e. LVM doesn't.
We should flag the test so that if it's skipped it doesn't
fail the guideline.
The flag is intentionally missing action value because we
haven't decided yet if we will remove it in the next
guideline or keep it still flagged.
Change-Id: I6b1d30c27fe055849fd0237f1ff46591303bd1d8
Having named the file differntly than the component name defined
within was causing unnecessary troubles in the refstack server
which parses it. Having the names consistent is a better practice
than implementing various ifs in the server's backend and fronted
and may definitely lead to less issues in the future.
Change-Id: Ie491daa752320377d7fb3d3198c329955f65d569
At the Dec 08, 2020 meeting of the Board of Directors,
the Board voted to approve the new guideline for Victoria release.
This commit updates the Board of Directors approval in guidelines
doc also supersedes an old guideline.
Change-Id: I6ebfb761b1c342aaaa3d912153fa59a8a3f8a115
The interop working group intends to present
the Shared File Systems interop guidelines advisory
to the Board for approval for the very first time.
This commit adds a "draft" advisory with the tests
accepted by the interop working group. The
shared file system service (manila) tests rely on
the Victoria release of the manila-tempest-plugin
repository [1]
This commit also modifies the designated_sections
for the advisories that was incorrectly called out
in a previous commit.
[1] https://releases.openstack.org/victoria/#manila-tempest-plugin
Change-Id: I2bd9b41ec62803cf93eb6e90653432ee29d3b4ed
The Board of Directors approved 2020.06 on June 11, 2020. The
Foundation's OpenStack Powered program currently allows vendors to
use either of the newest two guidelines when testing [1]. The
two most recent Guidelines are now 2020.06 and 2019.11, so we need
to mark older Guideliens as superseded. This was missed in the last
round of approvals, so this patch corrects their status.
[1] https://www.openstack.org/brand/interop/
Change-Id: I415ddebe37873847c6a272d9249dfa048428d59c
At the June 11, 2020 meeting of the OpenStack Board of Directors,
the Board voted to approve the new 2020.06 Guideline. As usual,
the approval of a new guideline also supersedes an old Guideline, so
this patch also marks the 2018.02 Guideline as superseded.
Change-Id: I729d991a309192f18aee1702583016f3de5fe9b4
Draft guidelines for 2020.06 inclduing guidelines for
Orchestraion & DNS add-on programs. No changes to test
from last guidelines.
Implement: blueprint bp/iterop-2020.06
Change-Id: I9717c5af1e2eafdac9255413c34430fe7ea8f207
The Board of Directors voted to approve the 2018.11 Guideline at it's
meeting in Berlin on November 12, 2018. This patch marks the new
2018.11 document as approved and the 2017.09 document as superseded.
Change-Id: I9d3df5436d48a7a1cf420a522c207a9a22e1d002