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
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
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
There are a number of inconsistencies between the latest active
guidelines (next.json, 2018.02.json, and 2017.09.json) and
Tempest. This patch corrects the following errors:
* There are several duplicte tests between the new ServersTestJSON
and the old ServersTestManualDisk classes. This patch removes
all of the tests from ServersTestManualDisk as duplicates. While
technically the tests from ServersTestManualDisk should be
flagged, doing do would remove active tests from the guideline
because of name collisions in RefStack test result processing.
No functional change is made to the required capabilitied by
removing the duplicate entries, and adding a aliases to the
ServersTestJSON entry preserves old valid test results.
* A syntax error for an idempotent id was fixed.
* Some network router tests were updated to require admin capabilities
and have been flagged.
* Some volume tests were removed from Tempest or refactored, and
have been flagged.
* Some volume and object store tests were renamed, and new aliases
have been added to reflect the name changes.
Change-Id: Ib26ed051f42b8a528e6dd349141ec49f330243f3
Idempotent id expects the form of id-<UUID>. One of the entries
is of the form <UUID>. This patch corrects the typo.
Change-Id: Ie5ad764487097ef841750e0cd5a0046ab7448ac0
In general, when attach/detach volumes, there are several
internal APIs which only used to update volume status and
to indicate the intermediate state. For example, os-attach
and os-detach, they have already been discussed in the
maillist [2] and marked as deprecated in patch [1].
Since the complete attach/detach process has already been
covered by "compute-volume-attach" capability.
This patch proposes to deprecate volume "reserve&unreserve"
capability as well. These tests could break defcore testing
for OpenStack clouds, especially for public clouds.
1. Remove V2 and V3 reserve&unreserve from 2017.09
2. Remove V2 and V3 reserve&unreserve from 2018.02
3. Remove V2 and V3 reserve&unreserve from next
[1]: d234631f4f
[2]: http://lists.openstack.org/pipermail/interop-wg/2017-April/000116.html
Change-Id: I1599c1c3721e72a415be65af8b474206b174f241
There's a typo in an alias:
tempest.api.volume.test_snapshot_metadata.VolumesMetadataTest.test_iupdate_snapshot_metadata
Should not have the extraneous "i" before "update".
Change-Id: I8eaf359ff9e74f15056dc64217d69c9e7e0d6c73
The Board of Directors will meet on Feb. 26, 2018 at the PTG
in Dublin to vote on the 2018.02 Guideline proposal. The Board
report can be found at:
https://docs.google.com/document/d/1kgmdHTb0ve340sdwO8-8-vKTaCqFSNtGxSBvSwofeJE/edit#heading=h.yjel5gfxgg3h
This patchset should be merged if and when the Board approves the
new Guideline. It marks 2018.02 as approved and 2017.01 as
superseded.
Change-Id: I93291e54bc56e41977a2b19ed30b733013a0c837
Some of the volume v3 tests have been reorganized over time[1], so
we need to add a few aliases for tests required in 2018.02.
[1] For example: https://review.openstack.org/#/c/396159/
Change-Id: I56167c3cec4d6708f8333429eaac652ddb5e111c
Last year some network tests were moved out of test_routers and
into an admin path because they require admin credentials [1].
These include a couple of tests that are in the 2018.02 Guideline,
so we need to flag them.
[1] https://review.openstack.org/#/c/462741/
Change-Id: Ib8fad4bf39cdfd884b89ef87bb431311c6540a2b
The id field in the 2018.02 was left as "next" rather than being
updated with a proper date. This patch fixes the oversight.
Change-Id: If499f2e38e4e6d142f75b39c5cf22c2606c10a7a
This commit creates the 2018.02 guideline that will be presented to
the Board of Directors at the February 2018 meeting for approval.
This commit moves all capabilities that were advisory in 2017.09
to required status.
This patch also refreshes the next.json document to prepare for the
fall 2018 guideline drafting process. As the meeting date for the
BoD meeting at the fall PTG has not yet been determined, it uses an
arbitrary date in August for the time being (we can change this
later once we have a firm date). It also moves items that were
advisory in 2018.02 to required status.
This patch can be merged now as it sets the 2018.02 document to
advisory status--we will change it to approved if and when the BoD
votes to approve it next month.
Change-Id: I634e2dc1273e7b67103c86436b4ea5489cae3543