This repository is hosted on opendev.org's
gitea server, and doesn't get mirrored to
github currently (we may add mirroring in
the future). We can swap a bunch of URLs
that assume the content is on github and
older infra cgit servers with correct URLs.

Meetings have moved from IRC to MeetPad,
fix the corresponding details in the README.

Also use this commit to strip trailing
whitespaces across the repository.

Change-Id: Ica0a7ba08d9c437f94fbc9ab282bd929f01df8ff

There are many references to review.openstack.org, and while the
redirect should work, we can also go ahead and fix them.

Change-Id: I70c590322ca5c20636ac8f4e0a5233dae4cb832e

This spec outlines the additions and modifications that will need
to be made to to the existing RefStack API in order to facilitate
and manage subunit data usage and upload

Change-Id: Ia2a171165963decd13a26a0226e6a448bc5b6432

Fix the typos found in refstack.

Change-Id: I66724acaf6472df2a2d957b1c795d4dbcc06a68b

While writing up the subunit upload spec, I went to grab the link
of the original spec off of github and realized that the data model
visualizations were nigh unreadable due to a lack of block literal
usage. This patch adds a block literal to restore readability.

Change-Id: Ie17d7b096300d5db706b948e8532b0380f42aaaf

Re: primary assignee: I know Chris had mentioned he wanted me
working on this; primary assignee can be changed if somebody
else is going to be the main actor in this change.

This is very much a work in progress. Some topics currently
being researched/up for debate:
* Is subunit2sql's input sanitization adequate for our needs,
  where protection against malicious file upload is concerned?
* Is there a way to store the data in subunit2sql's db schema
  in the RefStack db or vice versa?

Sections that I will be adding more detail to shortly:
* REST API impact
* Other deployer impact

Change-Id: I03e212694d7d7a586f1caabedbebd7da6a0f38b9

Change-Id: Id409c9bb45955ced41c7d85d8766247f50439b67

defintion should be definition

Change-Id: I78916bb0c299b20216d8a2e10f765156e3843941

Added sphnix build folder location. Added Ocata implemented specs.
Fix registered sign character.

Change-Id: I27a8db968dbb029f370f46b77f3d2be1d85a45ca

Change-Id: Ibf5b3ca13203cb3c84e2108c87d7fd16b1baa1c9

This spec defines the mechanism to mark a test as "used for
verification". APIs used to mark and un-mark a test are also
defined.

Change-Id: I1830414e62353974b45555fd8f22aac7acf06ff2

This spec defines the processes and mechanisms to associate
test results to vendor products.

Change-Id: I3257dbcad3781d1d168c45ad0db9570e5c851086
Depends-On: https://review.openstack.org/#/c/343954/

This spec defines the database and API update needed to match
the product model used by the OpenStack Marketplace.

Change-Id: I291998dd7aa174b4e2f50ef6d8011254d368e358

Several existing Refstack specs doesn't have the spec
name header resulting in a bad documentation formatting.
Added or fixed spec name headers under existing spec
folder so that documentation is rendered and displayed
correctly.

Change-Id: I20d0c140ddc132fad90e2b7152c71599a22a1dd8

Update the specs to match implementation details.

Change-Id: Iac1cfec9174350d081ff221f82cf314e4a5ca4d7

This spec defines the REST APIs needed to support product registration
and management.

Change-Id: Idd45407c356d18fad748717874e8844542a2b266

This spec defines the REST APIs needed to support the retrieval of
DefCore Guideline files and the test lists included in these files.

Change-Id: I8c0404972139e6516c8f45898c27c39df4744a8e

This spec defines the REST APIs needed to support vendor management.

Change-Id: I0b7c834227e47a80c42fb575ca4d8097bc333660
Depends-On: #268922

Change-Id: I14feb04299bfdf628cd4c53b043fea7e62ccfa39

Add 'properties' column to the organization table.
Add 'product_type' column to the product table.

Change-Id: Ibdbff019bc627e3c65e7c37b334fb674f8c85529

This specification is the first of a series of specifications that
will be defined for RefStack to implement the vendor/product
registration process.  This spec focus on the data model aspect
of this process.

Change-Id: I59c74367aed3610d71d4221019099a66e8b80178

As RefStack implements the vendor/product entities, RefStack needs
to allow management and visibility of these entities to a group of
users not just the user who created the entities.

Change-Id: Ib1ef631c6b02746a30970adf0289549642348cf1

This spec proposes RefStack to add a method to use the cloud access URL
as the base to generate the CPID.

Change-Id: I118a77f4cb328908a528376a038a43684427dbfa

Change-Id: I02da57c2b7d888ae49bd4f96ba8fb46016d16e7d

RefStack recently added features to enable the uploading of data with key.
Currently, RefStack accepts the uploaded data regardless of whether
the keys exist in RefStack or not. This spec describes the validation
process update needed to ensure that RefStack only accepts data with
those keys that are previously imported into RefStack.

Change-Id: I5bb7de969fe92258d54a64feec01310afcf91038

This spec proposes to add a new REST API that returns the number of test
records that have been uploaded to the Refstack server.  Currently, there
is no API provided by Refstack to fecth test records.

Change-Id: I223e1286634b4fc31eaef02fb9ada91a7b5a09e0

Test results are validated using jsonschema.
Actual schema can be retrieved from /v1/results/schema endpoint.

https://github.com/stackforge/refstack/blob/master/specs/proposed/refstack-org-test-result-json-schema.rst

Change-Id: I05e5fa3b84c60925f162985cd7d51b14d69b19d8

This schema proposes the development of a json schema for test results
to aid in client development and server side data validation.

Blueprint:
https://blueprints.launchpad.net/refstack/+spec/test-result-json-schema

Change-Id: Ic8ba94e9646285f827be5a07c309baf8aa197267

A GET handler was added for retrieving test results with URL of the
form: /v1/results/{test_id}.
The report page can now be used to view results. It should be accessed
with URL of the form: /output.html?test_id={test_id}. This is just to
keep it simple for now.

Change-Id: I28e9ebf74cc7a6dad360232840b49c6aae27dab0

If test has a uid we should add a possibility to transmit them
to Refstack from refstack-client.

Change-Id: I6fc70dd7ffda13c51bcbb99a78cd096a48dc5cf5

Change-Id: Ie226c9129d88abecaa52719f869794ea3c914f2d

Replace URLs for workflow documentation to appropriate parts of the
OpenStack Project Infrastructure Manual.

Change-Id: Ic46bcacbbff0f7b11bbb879e5830c6be1ee1be61

storyboard: https://storyboard.openstack.org/#!/story/110

At the Juno summit, we have learned of many other groups working
on things that overlap with Refstack.  This spec identifies code
that should either be deprecated or moved into other projects.

Change-Id: I040f3ac690344265e029815757322aff6e28d2cf
Co-Authored-By: David Lenwell <dlenwell@gmail.com>

from now on all testing will happen from tcup. no local test path needs to exist.

Change-Id: Ibfebcb67b5eb307b670794af07e31fe3f9f0dd0f

Change-Id: Ib12acc7536f4541591365d31250b703c8493ec16

To allow the tester to be installed and run outside of the refstack project
we have decided to move it into its own project.

moved to approved and added work items to storyboard:
https://storyboard.openstack.org/#!/story/133

Change-Id: If789122e76927641fb4ce53485d0bebc3c3b21b0
blueprint: seperate-refstack-tester-from-refstack

ref: https://storyboard.openstack.org/#!/story/135

Use Endpoint ID as a unique identifier for clouds
in refstack test uploads.

Change-Id: I363531ccfbffc5ba76a7d95de6648ff2dd75a95d

The coretests.json file includes a list of tests that are defined as "core" by
the DefCore committee.  Currently, the coretests.json file (in the
defcore/havana directory) uses the method names defined in the Tempest Python
test classes as the test names.  While these method names are unique in Havana,
it is not the case in Icehouse where some of the method names are being used by
multiple test classes of different OpenStack components.

Change-Id: Idcc62c43984356fca00464dd192ae1292569e0b8

Change-Id: I5ce4858c4e7f6fac5d85d4eb6b0962b2b6d3dd78
blueprint: ability-to-upload-a-complete-tempest-config
storyboard: https://storyboard.openstack.org/#!/story/105

rewrite of the spec in .MD format to better support clean code blocks.

moved into approved folder

Change-Id: Ida36a618cfeb5a5097cd88bbb09e6b15c8f8f9a1
storyboard: https://storyboard.openstack.org/#!/story/132

Change-Id: Ie12b4eee515046135b32622d93c2d7c94cda99d8

For https://storyboard.openstack.org/#!/story/111

This spec should be considered complete for final review.

This is a pair of read only screens for helping
community compare tests results starting from the
DefCore capabilities and allowing them to inspect
specific items on drill down.

The focus is on comparison against core and
other clouds not on quantative analysis.

Change-Id: I85fa223a4fd67b16d9103593f727a6811c741452

For story https://storyboard.openstack.org/#!/story/109

This spec should be considered complete for final review.

It is a basic read only screen for rendering test results
in a way that helps the DefCore committee (and other
community members) find tests & capabilities that should
be added to core or should be removed from core.

Change-Id: I879b73cba32d8ae65aa50ad5cb42cc7c9baa5647

Change-Id: I47d3ca0f259edba8f6fc923b66c4c2fd9b88658d

Change-Id: Iffa95584bd3417391704707811cc9ef21527dc60
storyboard: https://storyboard.openstack.org/#!/story/108

Change-Id: I99cc5a8017789fe817029922272e82a402645e9a

finalized api spec

Change-Id: Ibb015c4dab9e4f36290dec02fb6b9097dc070f11

Those files are not supposed to be marked as executable.

This initial TCUP spec addresses build the base community
capability to run tests manually against internal private clouds.

Change-Id: Ic8315f56a7c2166192d2340824a471fc69db526b

Change-Id: Ibd6aa216a759d8146fa240e79622827ed46a2369

Change-Id: Ib2e5266e88a1d72c6fb9f8b4ff456778b8828641