docs.opendev.org will provide easier access to the doc pages
in comparison to the Gitea (opening the doc files in the repo).
Change-Id: Iecc6d745f1a35e701ff86060169c489556cac9c3
Let's bump minimal tox version so that we can rename
whitelist_externals option to allowlist_externals one.
Change-Id: Id105174f05b4d98e8b2e5320fcf789abb89e8ec3
Hacking provides valuable standard checks such as imports in
alphabetical order. Having this included in our pep8 check/job
the quality and readability of the code will be improved.
Change-Id: Ieedfcd340e9b700bdead0073bac39a505c8628b5
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
Adds a job which runs all next tests on a devstack master and
experimental jobs which run the same on supported stable releases.
Fix names of a few manila_tempest_tests and designate_tempest_plugin
tests so that they match the names from the plugins.
Change-Id: Iedbaa09e425a29156304eea63b66a1ce69dd77bd
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
Having named the file differntly than the component name defined
within was causing unnecessary troubles in the refstack server
which parses it. Having the names consistent is a better practice
than implementing various ifs in the server's backend and fronted
and may definitely lead to less issues in the future.
Change-Id: Ie491daa752320377d7fb3d3198c329955f65d569
interop-tempest-consistency job still use the python2.7
env to run as default basepython in testenv is py2.7.
Requirement has dropped the py2.7 caps now
- I2d58d1b524764ea1d46d6ab3a382783f6a002b34
and interop-tempest-consistency job started failing on interop
and Tempest gate. To unblock gate on both project we need to move
the default tox env of interop to python3.
Change-Id: I40770cf254369808c2e420dae6c2ec52bf47b777
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.
Change-Id: Ie4fd0a69ea0c2ffeff59a2ead1012a730e47084c
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This patch updates some of the consistency checking tools
to make them more generally usable by allowing both
automatic checkout of tempest and manual checkout. It builds
on this to add a Zuul job that gates against the consistency
check.
Change-Id: Id0d9148af39c2d2ccf8f11502cc9aff6699f0ead
This is a mechanically generated patch to switch the documentation
jobs to use the new PTI versions of the jobs as part of the
python3-first goal.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: Ia08c31871528b6d0334a01ce5719ea96f3741d90
Story: #2002586
Task: #24759
This tool checks a guideline against a Tempest test suite
to make sure that:
* all idempotent IDs in the guideline exist in the tests
* test names in the test suite match names in the guideline
By gating against this tool in both the Interop project and in
Tempest, we can help prevent typos and catch renaming of tests.
Change-Id: I8b6778c2063eeac8b0d7c0d64127eefe420c617f
The 2018.02 Guideline was the first to be published in the new
schema 2.0 format. [1] The change to 2.0 was done with the agreement
that it would probably be easiest to write 2018.02 in the new format
and then create a new next.json from it (rather than the other way
around) due to the timing. This patch transforms next.json to
schema 2.0 by using the existing 2018.02 document as the base. Once
this lands, we'll be able to begin work on the next round of scoring
using the new 2.0 format, as well as do the usual round of housekeeping
like removing old capabilities and moving advisory ones to required.
For simplicity, we'll do those in future patches.
This patch also removes one test from the listing as it has been
combined with another test under the other test's idempotent ID.
See discussion in [2] for more background. Leaving the test here
but also swapping the name and alias as we normally do in next.json
would cause a duplicate key issue with the docs jobs.
[1] https://git.openstack.org/cgit/openstack/interop/schema/2.0.json
[2] https://review.openstack.org/#/c/548990/3/2018.02.json@2924
Change-Id: I12457d66e804f6f6673c604542848d41ac1396a2
Merge in tox.ini the existing separate lint jobs into a single one and
use the environment pep8 for this as pep8 is the generic linting target
in OpenStack.
This allows us also to remove several test jobs from this repository.
Change-Id: Iba797d082b5793352b75c456c5a06791a34bc40d
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
Version 2.0 of the Guideline Schema used by the Inteop WG.
Includes the 2.0 schema, documentation, and an update of the
current next.json schema to the proposed 2.0 standard.
Open questions:
* make required_since optional?
* make idempotent_id optional?
* change date of approval to match more generic dates?
* components structured correctly? redundancy with designated sections?
* splitting platforms and extensions up into different fields for better
granularity?
Change-Id: I552408d1426ee9f7f5f350f2f7333f8e33884db4
Create the 2017.08 Guideline candidate, to be moved from review to
approved status if and when approved by the OpenStack Foundation
Board of Directors. A vote is expected at the August 22, 2017
Board meeting.
Note: this patch also adds back test information for two Capabilities
that were deprecated (and keeps them marked as not required). The
tests associated with these were inadvertently removed in
Iabb1d0820300442e407d8b92dfb575ac71471d06 but should instead have
simply had their "required-since" status nullified, as removing
them entirely breaks the jsonToRst.py script and leaves users
unable to easily find the tests that are no longer required due to
the deprecation.
Change-Id: Ifce3fe1e3401e7f887ddeae2a41078dca7e16625
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
Following the July 2016 board meeting, add minor update to guidelines
to move them to version 1.5 of the DefCore schema and add json
schema validation to gate job.
Change-Id: Iac667f8a87b50a15f4dfe13c1ef69efa61c10059
Added formal 1.5 json schema to gate current guidelines against.
Updated next json files to validate against schema,
and updated next guideline schema version reference to 1.5,
with syntax changes that fixed ambiguous empty content and
duplication of data. Added tox jobs to lint and validate next
json files.
Change-Id: I13ee6b16115588527fde070e34874edf919aa864
We're starting to accumulate a number of python scripts in
various parts of the tree, and probably will continue to do so.
To make maintenance easier over time, we should have basic
pep8/flake8 checks in place for python code, as is best practice
elsewhere in the OpenStack project. This patch adds basic checks
and corrects existing errors in our python scripts so that going
forward we can opt to gate on clean python code.
Change-Id: Ie32ee7a14ee608e12f42288e137a0849555b5ed8
Over the past week or so we've seen docs jobs failing on the DefCore
repo. The trouble started at around the same time the gate was having
other issues, so we mostly let it slide. However upon further review,
it appears a change in the run-docs.sh script in infra [1] is actually the
root of the issue. The problem is that our tox.ini doesn't have
a testenv configuration that most other projects do, and the change
to run-docs.sh exposed that. This patch should be sufficient to get
our docs builds working again by fixing our tox.ini file.
[1] https://review.openstack.org/#/c/211239/
Change-Id: I771df06d07080daba8ae0d7beb81d7e2a601aa68
* Creating doc/source directory
* First pass at index.rst
* Moving process directory into doc/source
* Moving schema directory into doc/source
* Added tox job for doc building
* Updated tox.ini doc8 job to scan doc/source only
Change-Id: Iec39fa40c3d0e0ee317e625e39f789114da40fea
Updated tox.ini to check current rst documents. Fixed tox errors
in checked documents. Semantics of docments remained unchanged
Change-Id: Ic4b628b551e0c438ca71d5728afa7172bc3cf128
Added tox.ini and test-requirements.txt to allow for .rst
document validation, and other tests to check updates and
changes. The goal will be to add a verify and gate process
to the Defcore project repository.
Change-Id: I9fceae7569d7e3df53c3c3d2567a691dbd406a55