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
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
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
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
Co-authored-by: Chris Hoge <chris@openstack.org>
Co-authored-by: Mark T. Voelker <mvoelker@vmware.com>
Change-Id: I6582124284c66f032649ea7f580f8c7040cd1415
Test [1] was promoted from the advisory group in 2017.01 to become
a required test in 2017.09. Since it requires a second set of user
credential, it should be flagged until the issue is fixed. Or better
yet, we just move it back to the advisory section.
[1] tempest.api.identity.v3.test_projects.IdentityV3ProjectsTest.test_list_projects_returns_only_authorized_projects
Change-Id: I83916504b6f87ff748f6f10b6c0e29b5c3fe6ad8
The Board of Directors deferred it's August 2017 meeting until
September, so the Guideline we intended to ask approval for in August
will now not be voted on until September. Guidelines are named by
the year and month of their approval, so this patch updates references
to "2017.08" to "2017.09".
Change-Id: If7e19ea4524b7c944d503cbda73052ef0b0f55d0
ArkadyKanevsky