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
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
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
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
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
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>
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
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
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
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
This initial TCUP spec addresses build the base community
capability to run tests manually against internal private clouds.
Change-Id: Ic8315f56a7c2166192d2340824a471fc69db526b