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
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
The .rst Guideline files currently say that they're generated from
"the master JSON verison" but don't actually contain a link to their
JSON counterparts. This patch makes that reference a hyperlink so
folks can more easily locate the JSON files that are the authoritative
documents. This is especially useful when viewing rendered versions
of the RST docs.
The patch also adjusts the script we use to generate the RST docs
from their JSON sources so future Guidelines include similar
linkage.
While we're at it, we've also removed a chunk of code in the
RST generator script so that it doesn't rely on the "name" field
since we never really added those fields universally, which could
cause the script to fail. Instead we just use the "project" field.
Further, a few capabilities that are marked as removed are lacking
the aforementioned "project" field, so those have been added where
they were missing.
Following the changes to the RST generating script, it has been
re-run so that the existing 2015 Guideline RST documents have
the same formatting. While the formatting has changed (added links
and modified capitalization), the content has not (no capabilities
or tests added/removed).
Co-Authored-By: Mark T. Voelker <mvoelker@vmware.com>
Co-Authored-By: Rob Hirschfeld <rob@zehicle.com>
Change-Id: Idbdd7d6825aa8af2404b9e2791fa67240cdef239
An earlier change added a flag to the compute-volume tests [1].
However that change also introduced a trailing comma at the end of
the flag list for that capability, which results in invalid
JSON. This patch removes it so that scripts will parse properly
again.
[1] https://review.openstack.org/#/c/196157/
Change-Id: I0b56721ffec66c0f3e0313cd36c78de6c3079a2b
Original commit message:
"Currently tests that require SSH are not gated against in Tempest
due to the variety of conflicting network models available to
OpenStack clusters. Tests that require SSH need to be rationalized
and refactored, and is a current work item for the openstack-qa
team.
Until this test infrastructure is refactored, the tests should be
flagged but kept for future capability testing."
This situation hasn't changed in the releases covered by 2015.05
and therefore warrants flagging in that Guideline as well. These
tests are also under consideration for flagging in 2015.json.next [1].
[1] https://review.openstack.org/#/c/189927/1
Change-Id: If536e1afe679f5be400459145ea2be75771fac96
From previous commit message:
"In the compute-servers sections of tests, there are four resize tests.
When using Nova's libvirt driver, and no shared-storage, resize relies
on transferring storage via ssh.
This requires password-less ssh to be setup between all compute nodes
in the cloud. This kind of setup may raise security concerns.
For example, resize is disabled by default in the HP Helion OpenStack
distribution because of this security concerns, as well as in the HP
Helion OpenStack public cloud.
This would cause any cloud/product sharing the same security concern to
fail or skip these tests, so I'm proposing they should be temporarily
flagged.
The blueprint [0], when implemented, would address the security
concerns, so it would be the first step to remove the flag from resize
tests.
[0] https://blueprints.launchpad.net/nova/+spec/migrate-libvirt-volumes"
These concerns are still present in the OpenStack versions covered by
2015.05, and these tests have already been flagged in 2015.json.next
as well [1]. They therefore warrant flagging here too.
[1] https://review.openstack.org/#/c/189975/
Change-Id: I5aade6f2296d861555fa38eba0d82fd777d9df3c
Original commit message [1]:
"Concerns have been raised (by both community members and John
Dickinson, the Swift PTL) about a subset of the Swift tests that
are currently included that test ACL policy and authentication to
objects in Swift. John's reccomendation was to flag these tests
as they are not testing the Swift API and to remove them in the
future."
Note that these tests have also been proposed for removal
in 2015.next.json. [2]
[1] https://review.openstack.org/#/c/181659/
[2] https://review.openstack.org/#/c/189979/
Change-Id: I445e9b3d8001e286b7147b6ac45beb953c23549e
...in 2015.05. Original commit message [1]:
"The Images v2 API ListImages test creates images to appear in the image
list, using the Glance image-create call to do this. There is, however,
an alternative route to image creation in the Images v2 API, namely, to
use an import task. A cloud provider may wish to restrict the standard
image-create to admin use only, for example, and restrict regular end
users to use of the import task (which allows an opportunity to perform
validation or security scanning on the image data before creating an
image in Glance). It is also reasonable for a provider not to allow
any upload of external images into a cloud and instead only allow image
creation via the Nova image-create server action. The key point is
that given that the ListImages test is supposed to test that the image
list functionality is present and working correctly, the test should be
agnostic as to how the images got into Glance in the first place. The
test should be flagged until it can be modified to take into account the
various legitimate restrictions that providers may wish to place on how
images are introduced into their OpenStack clouds.
This is also reported as tempest bug:
https://bugs.launchpad.net/tempest/+bug/1453265 "
The Tempest folks have rejected the bug, but a larger discussion on
the defcore-committee ML [2] has ultimately indicated that there's simply
not an interoperable solution today. The discussion will hopefully
lead to a more interoperable future, but we're not there yet. Thus,
we should carry this flag forward to 2015.05.
[1] https://review.openstack.org/#/c/181280/
[2]
http://lists.openstack.org/pipermail/defcore-committee/2015-June/000823.html
Change-Id: If2c6528af24f19881dd30106437bd4253dcc1a1a
Original flag commit message:
"In the Compute tests, there are tests that need to generate
images as a prerequisite before the main tests can begin.
Since these are Compute tests, I would expect that these
prerequisites would be via the Compute API, but they use
the Glance v1 API instead. Since the capability being tested
should be Compute in isolation, I would say this test should
be flagged until the depdency on Glance v1 is removed."
Glance implements two APIs, v1 and v2. The v1 API
is currently SUPPORTED, while the v2 API is CURRENT [1][2].
The original plan was to deprecate and remove the v1 API
by Kilo, but it appears it was superceded [3]. Neither Nova
nor Horizon currently supports proxying the v2 API,
but this functionality is on the roadmap for both
projects [4][5].
These tests should be flagged with the intention to
reintroduce them after upstream support for Glance v2 has
been added to Nova and Horizon and after the implicit
dependency on the v1 API has been removed from the Tempest
tests [6].
[1] http://developer.openstack.org/api-ref-image-v1.html
[2] http://developer.openstack.org/api-ref-image-v2.html
[3]
http://lists.openstack.org/pipermail/openstack-dev/2013-November/019431.html
[4] https://blueprints.launchpad.net/nova/+spec/use-glance-v2-api
[5] https://blueprints.launchpad.net/horizon/+spec/horizon-glance-v2
[6] https://bugs.launchpad.net/tempest/+bug/1463534
"
This situation hasn't changed in the releases covered by 2015.05 and
therefore these flags should be carried forward to that Guideline.
Change-Id: I2d8168d1f0478499be574e695bb00ac8e7965c37
Keystone token tests were refactored. This patch corrects the
name reference in 2015.05.json.
Keystone was listed twice as both required and advisory in
the designated sections. Removes the erronious advisory
designation in favor of the required designation.
Change-Id: I6fbe17c9f4d2e3651b956bfb133e919724b45096
The main change for this Guideline is the addition
of the Keystone identity tests.
There is a schema update pending but will not have
sufficient review time before Board approval in May.
Based on community discussion, FLAGGED TESTS were removed
from this guideline to be added back by DefCore in the
next cycle following discussion.
This patch includes updates to the 2015.next file
to reflect approval of 2015.05.
Change-Id: Ia1523cb0ee4ecd6ae951303663e8afbbfbc9a4e2
ArkadyKanevsky