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 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
Test [1] is a typo. The correct name is [2]. The test_volume_bootable test belongs to
the test_volumes_actions.py not test_volumes_get.py file. Thus, no Tempest version will
be able to run this test because its name won't be able to match any name from the test
list produced by Tempest. Following the practice in [3], fix 2017.01.json by adding the
correct name as alias since this is an approved guideline. For 2017.08 and next.json,
replace the incorrect name with the correct one.
[1] tempest.api.volume.test_volumes_get.VolumesActionsTest.test_volume_bootable
[2] tempest.api.volume.test_volumes_actions.VolumesActionsTest.test_volume_bootable
[3] https://review.openstack.org/#/c/450346/
Change-Id: I9d17b6f9366740878f1b2918d38da775f4b7e620
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
This is the second patch for I700b7009bfb3a93ade832198f4d58f487d641af8
It provide all the aliases for volume-v3-* which are
advisory capabilities.
The change is due to tempest renaming of its VolumeV2 classes.
Tempest change is to reuse the same test case for both V2 and V3.
Avoiding confusion about the version being tested by removing "V2"
from the name. Notice that Cinder version should be setup at
tempest.conf file and defaults to V2.
Change-Id: I5d709698297d043b5cb4a40c263f30cc00908238
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
Since Iaa8f2863f19ed04878a8a70dad13f7b765887d3c the test has been
implemented and the module path is always test_subnetpools_extensions
not test_subnetpools_extension. So this patch fixes it.
Change-Id: I0630c76e050055db9909b90230ab021939e71ea1
Test [1] does not included class name in its FQN. Thus, no Tempest
version will be able to run this test because its name won't be able
to match any name from the test list produced by Tempest. Fix
2017.01.json by adding the correct name as alias since this is an
approved guideline. For next.json, the incorrect name is replaced
with the correct one because it does not make sense to add a
non-existing test name as alias.
[1] tempest.api.identity.v3.test_list_projects_returns_only_authorized_projects
Change-Id: Ice75be2402d65ff473f68aa77db66167ae452363
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
This patch should be approved only if and when the OpenStack
Foundation Board of Directors votes to approve the proposed 2017.01
Guideline. It does the following:
1.) Marks 2017.01 as "approved."
2.) Marks 2016.01 as "superceded."
3.) Adjusts the "replaces" target of next.json and it's target
approval date to reflect work begining on the next Guideline.
Note that the Board of Directors meeting list for 2017[1]
hasn't yet been set, so the date listed here is approximate.
[1]
https://wiki.openstack.org/wiki/Governance/Foundation#OpenStack_Board_of_Director_Meetings
Change-Id: I566e52fdc82af57a5bf24bfd3db5d10a26887127
Create the 2017.01 Guideline candidate, to be merged if and when
approved by the OpenStack Foundation Board of Directors. A vote
is expected at the January 24, 2017 Board meeting.
Change-Id: I8bd75de0967395cc1cfb9b247c3f442f9e08bab2
ArkadyKanevsky