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
NOTE: This patch starts the process of creating a new
draft process for Board approval in Section C6.
As discussed in the board meeting, this change specifically
identifies that only the latest two guidelines are available
for vendor validation. Older guidelines are still approved
and must remain available because vendors have validated
against them (thus superseded not deprecated).
Change-Id: Id2c2a23c9a8e204480dcebde6fe436292120ba8a
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
In the compute-servers sections of tests, the
ServerActionsTestJSON.test_get_console_output test fails on some Nova
backends because it's not a universally supported feature. For example,
it isn't supported on VMware:
http://git.io/vJIAj
This would cause any cloud/product using such a backend to fail DefCore
tests, so the test should be flagged.
Change-Id: Ie3778cf8d1100fdb0a9065fabfb8254e0a7747b1
As per the process, we want to use generated RST
instead of hand created files.
In generating the files, I found a comma error in 2015.03
and removed spaces from 2015.04 so there are minor
changes to those files.
Because 2015.next is still in process, it does not make
sense to generate the RST file at this time. We do
NOT want to have to maintain multiple files for each
change. I've removed the 2015.next.rst file.
Also added check to make sure we're using the
correct JSON source using the hardcoded DefCore
repo path as an extra check.
Change-Id: I443f4c1cb84eb2c42ad9e6914cee0ce6d498a9bb
As per DefCore discussion, I've moved the DS JSON over
to the guidelines.
Unlike the original version, I've added the concept
of required, advisory, depricated, removed and
informational so that it matches the process flows.
To be complete, I've done it to all three Guidelines
since they were all the same.
Change-Id: Ia5a906df5228bf34bb24c96e730e2452743a17c8
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.
Change-Id: I9e79090f70648661ab236f67be7bbcd99bc0afc3
Also, correct JSON denormalization of the missed
guidelines addition for 2015.04 for 2015.04 and 2015.next
Change-Id: Ia9473b50d45d436c136ca58147229bd1fd130bbf
PS: we may want to drop the denormalization (patch?)
Initial draft of 2015.03 guideline as passed by the board.
We are condensing two steps into one here > format & content.
After we accept this, we will create a new prelim guideline for
the next review cycle (target at 2015.04!).
I've also moved from files out of the root directory for
cleanup.
The RST and JSON files should match in content.
Change-Id: I40623b38e80a7d4a65a66d7210f6dfad5835c371
ArkadyKanevsky