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
Clouds are hard. English, doubly so. We have a longstanding
spelling error in the schema: "superceded" should be spelled
"superseded". This patch corrects it and updates all the documents
the typo was propagated to over time.
Change-Id: I72f24bf026919f4ccce0ce0c42e1c33c4042aca4
Co-authored-by: Chris Hoge <chris@openstack.org>
Co-authored-by: Mark T. Voelker <mvoelker@vmware.com>
Change-Id: I6582124284c66f032649ea7f580f8c7040cd1415
A new volume api test [1] will be added to the function
test_update_volume_metadata_item, the test name will be
changed on Tempest side. This patch adds aliases for
following this Tempest change.
[1] https://review.openstack.org/#/c/479152
Change-Id: Ica8b57f5f5392e2bf47e368e9b10ef9fa5695c30
Depends-On: Idb9d198383ce93453707f1204806e4ae82c1e46a
A new snapshot api test [1] will be added to the function
test_update_snapshot_metadata_item, the test name will be
changed on Tempest side. This patch adds aliases for
following this Tempest change.
[1] https://review.openstack.org/#/c/479124
Change-Id: I672bbcb9983e7a3ace7769722d6ff97f7bc0ccc8
Depends-On: I3697406e5541bbdb191e4d6e63831be31b471e78
The recent version of Tempest (at least from v15) has renamed
all the previous VolumeV2* test case to Volume*. However the
current defcore guideline has not added such alias, which has
resulted in error when user wants to use new version of tempest
to test.
This patch is the part 1 of the fix, due to the large amount of
work. This patch has provided necessary aliases for all the
volume-v2-* capabilities (that means mission complete for required
capabilities) and some of the volume-v3-* ones.
We should expect another patch to provide the aliases for the
remaining volume-v3-* which are at the moment advisory capabilities
Co-Authored-By: Luz Cazares <luz.cazares@intel.com>
Signed-off-by: zhipengh <huangzhipeng@huawei.com>
Change-Id: I700b7009bfb3a93ade832198f4d58f487d641af8
In this flagging request two test cases are flagged:
"test_update_port_with_security_group_and_extra_attributes"
and "test_update_port_with_two_security_groups_and_extra
_attributes"
Reasoning: the concept of a network in OpenStack usually
refers to a l2 network, instead of concept like vpc in
aws. The flagged test cases require the cloud to support
subnets within a l2 network, which is a rather rare use
case for typical IPv4 public cloud implementation.
Specifically, in the first flagged test case update_port
action involves creating a new port in a new subnet and
update the previous port to the new one. The second test
case deals with a similar problem in a similar manner.
Proposal: flag these two test cases in defcore guideline
2016.08.json, 2017.01.json and next.json
Change-Id: I247d9247ba751f2d566ec2eb08905a264e784d7e
Signed-off-by: zhipengh <huangzhipeng@huawei.com>
test_list_servers_by_limits will be removed from Tempest
by https://review.openstack.org/463257, this is to remove
it from json file
Change-Id: I052e4305a08e2c63277903357ffe2696f2e85c95
The rationale for this patch has been stated in:
http://lists.openstack.org/pipermail/interop-wg/2017-April/000116.html
In short, the os-attach/detach in Cinder only changes the volume
state, it does not actually attach/detach the volumes, which is already
covered by "compute-volume-attach" capability. Therefore there is no
need for "volume-v2-attach-detach" capability of which test could break
defcore testing for OpenStack clouds, especially for public clouds.
Based upon the above reasoning, this patch accomplish two things:
(1) Flag all the test cases under volume-v2-attach-detach in
2016.08.json and 2017.01.json, and all the test cases under
volumes-v3-attach-detach in 2017.01.json.
(2) Move volume-v2/v3-attach-detach from "required" to "deprecated"
section in both 2017.01.json and next.json, and remove the detailed
test sections below.
Action in (1) is mainly due to the fact that defcore does not have
a mechanism to flag capability. Therefore the only way I could do
is to flag all the related tests with [D400] which indicates that
the capability associated with the tests has problems.
Change-Id: Iabb1d0820300442e407d8b92dfb575ac71471d06
Signed-off-by: zhipengh <huangzhipeng@huawei.com>
Since I6f2c2ebdce227705f073a43ff04c8bddc4ca5fd4 , the test name has
been changed on Tempest side. This patch adds an aliase for following
this Tempest change.
Change-Id: I8f8c0ceb291f0e666c323d6ad37b72bfbff9099b
Test tempest.api.object_storage.test_account_services.AccountTest.test_list_extensions
is included in the objectstore-account-list and the
objectstore-info-request capabilities. This patch flags or removes
this test from the objectstore-account-list capability.
Change-Id: I92e3a66b3a1beb8ceee6342a8a57f14c08490068
In this flagging requests two capabilities are flagged:
"test_create_port_with_no_securitygroups" and
"test_create_show_delete_port_user_defined_mac".
Reasoning: For a general public cloud setup, regarding
the first case, when user creates ports it is usually
required to have security group parameters for security
concerns. Regarding the second case, users are usually
not allowed to self-define mac addresses. The mac
addresses are usually pre-allocated.
Change-Id: Icead40f547e5d570250cf524bd6ae900c3fc82ea
Add aliases to reflect the change that these tests are now inherited
from ListUserImagesTest [1].
[1] https://review.openstack.org/#/c/424935/
Change-Id: I6acaf4b1c4c0325c089ecbefaad22e18f493d960
The test_upload_large_objects negative test was removed from
Tempest [1]. This patch flags this test in 2016.08 & 2017.01
guidelines and remove it from next.json.
[1] https://review.openstack.org/#/c/354873/
Change-Id: I28244022dbc0b72c5ae56f93d08a0ee464f65132
Commit I8d9296f958e17d20a39a05800ac1808347d952bd, removed
this test as it is being merged to CRUD tests.
This patch flag the update metadata tests and also remove
from next guidlines.
Change-Id: Id9a53c13eb501a131d4bab48414dd8deecc17d90
Depends-On: I8d9296f958e17d20a39a05800ac1808347d952bd
Commit I8d9296f958e17d20a39a05800ac1808347d952bd , changed the
name of the tests on Tempest side. So this patch addes aliases.
Change-Id: I4707b4956c2b92dc76cf4720016e737edd21b8b3
Depends-On: I8d9296f958e17d20a39a05800ac1808347d952bd
Commit I8d9296f958e17d20a39a05800ac1808347d952bd , changed the
name of the tests on Tempest side. So this patch addes aliases.
Change-Id: I4d4432bc1d2fd8b1c68cd6d6183bc456ce3b4ff4
Depends-On: I8d9296f958e17d20a39a05800ac1808347d952bd
Since Ic19fd7bd4f0afd6a551133d7db96737487b52663 , the name has been
renamed on Tempest side. So this patch addes aliases.
Change-Id: Ie929b481d8989433922ab960d11590aba31e8374
Depends-On: Ic19fd7bd4f0afd6a551133d7db96737487b52663
Since I7c99f61dc54ef7c437c7e4574eba935d76ef9318, QA team has removed
test_get_invalid_volume_id from Tempest because the test is duplicated
with test_volume_get_nonexistent_volume_id.
Then this patch changes the compute-volume-get test.
Change-Id: I54f9924c1c007ea2d34b7ef502df8edf8032549e
Since Ieab05d793039cea1d4bb14e91ea0f4cbea3df02b , the name has been
renamed on Tempest side.
So this patch addes aliases.
Change-Id: Ibd8b3f2494046b194d77e9d563ebecef3a883b8f
Tempest patch [1] will move these tests to a new file. This will
change the fully qualified test names.
[1] https://review.openstack.org/#/c/332066/
Change-Id: I3262f7414629d460b3660191e7f0c04198e22dd2
This commit changes the 2015.07 Guideline from "approved"
to "superseded" and changes the 2016.08 Guideline from "draft"
to "approved" status. This patch should not be merged until
the Board of Directors has approved the 2016.08 Guideline. Voting
is planned for the August 23 Board meeting.
Note: this change also regenerates documentation for all other
superceded Guidelines.
Change-Id: I630978bdff9c166a4a3340f8c26bcdcbf7013cbf
This change creates a 2016.08 doc. We'll iterate on this and then
present it to the Board of Directors on approximate August 8th
for approval.
Change-Id: I27e543fb522e77f697ead13d50da15f05367e581
ArkadyKanevsky