openinfra/refstack
Code Issues Proposed changes
refstack/doc/source
History
Clark Boylan 0af3a46e16 Force PEM filetype with ssh-keygen 
At some point ssh-keygen changed its default output format and now
python cryptography can't read the new default. Address this by forcing
the PEM output format which cryptography can read without problems.

Note this is a docs only change to help end users generate keys that
work with refstack after a user reported trouble with this.

Change-Id: I9d1f503817fee69fe22f19a98b506448bda1f888
2020-05-06 14:42:23 -07:00
..
conf.py
Update Refstack docs for documentation migration
2017-07-10 19:26:08 +00:00
index.rst
Re-organize RefStack document links
2017-04-24 15:36:24 -07:00
README.rst
Adding mechanism to build documentation via sphinx
2016-08-15 15:11:10 +00:00
refstack.rst
Invalid link of doc reference
2018-07-11 15:10:19 +07:00
run_in_docker.rst
Fix two typos
2016-08-23 19:38:39 +09:00
test_result_management.rst
Add document describing the newly added vendor and product features
2016-12-08 13:31:36 -08:00
uploading_private_results.rst
Force PEM filetype with ssh-keygen
2020-05-06 14:42:23 -07:00
vendor_product.rst
Add document describing the newly added vendor and product features
2016-12-08 13:31:36 -08:00

README.rst

RefStack

RefStack team and repository tags

image

What is RefStack?

  • Toolset for testing interoperability between OpenStack clouds.
  • Database backed website supporting collection and publication of Community Test results for OpenStack.
  • User interface to display individual test run results.

Overview

RefStack intends on being THE source of tools for interoperability testing of OpenStack clouds.

RefStack provides users in the OpenStack community with a Tempest wrapper, refstack-client, that helps to verify interoperability of their cloud with other OpenStack clouds. It does so by validating any cloud implementation against the OpenStack Tempest API tests.

RefStack and Interop Working Group - The prototypical use case for RefStack provides the Interop Working Group - formerly known as DefCore committee - the tools for vendors and other users to run API tests against their clouds to provide the WG with a reliable overview of what APIs and capabilities are being used in the marketplace. This will help to guide the Interop Working Group defined capabilities and help ensure interoperability across the entire OpenStack ecosystem. It can also be used to validate clouds against existing capability lists, giving you assurance that your cloud faithfully implements OpenStack standards.

Value add for vendors - Vendors can use RefStack to demonstrate that their distros, and/or their customers' installed clouds remain with OpenStack after their software has been incorporated into the distro or cloud.

RefStack consists of two parts:

Get involved!