Jump to: navigation, search

Difference between revisions of "RefStack"

(Resources)
m (refstack-client)
 
(46 intermediate revisions by 9 users not shown)
Line 1: Line 1:
Welcome to the home page of RefStack. Right now, it is mostly a collection of digital documents that inform the RefStack project, but this page will get cleaned up and ordered as the organizing process goes on.
+
This wiki '''might be outdated''' follow refstack's documentation for the current information:
 +
https://docs.opendev.org/openinfra/refstack/latest/index.html
 +
 
 +
'''More info''' about Interop Working Group can be found at:
 +
https://docs.opendev.org/openinfra/interop/latest/index.html
 +
 
 +
'''Toolset for testing interoperability between OpenStack clouds.'''<br />
 +
 
 +
== RefStack Design ==
 +
 
 +
RefStack provides the [[Governance/InteropWG|Interop Working Group]], the tools for vendors and other users to run API tests against their clouds to provide the Interop Working Group 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 be used to validate whether and how well actual OpenStack installations fit the OpenStack Foundation's requirements for OpenStack [http://www.openstack.org/brand/interop/ branding]. As determined through requirements analysis and specifications, it consists of a client that will gather OpenStack Tempest test results for the Stack under test, a User Interface for analyzing results, and a reporting structure that allows on-line and off-line options for submission for certification.
 +
 
 +
=== Requirements ===
 +
 
 +
[[RefStack/DefCore_Requirements|Interop Working Group Requirements]]<br />
 +
[[RefStack/UseCases|Use Cases]]<br />
 +
 
 +
=== Architecture ===
 +
'''For a quick overview, see the''' [https://docs.opendev.org/openinfra/refstack/latest/index.html RefStack Documentation]<br />
 +
 
 +
==== refstack-server ====
 +
The RefStack server is comprised of two components: the API and the UI. The API contains the REST endpoints needed for a user to upload and retrieve test result data sets which are stored in a MySQL database. The UI is an AngularJS based front-end for browsing uploaded data and viewing how test results stack up against Interop Working Group capabilities.
 +
 
 +
==== refstack-client ====
 +
The RefStack client is a Tempest wrapper that will run the Tempest API tests and will format the results in a way that the RefStack API expects. The client does the following things:
 +
* Extracts just the 'Passed' tests from the generated subunit file.
 +
* Retrieves the cloud provider ID (here, we use the Keystone service ID as the CPID), and associates it with the results.
 +
* Gives the ability to upload data to a RefStack server.
 +
 
 +
refstack-client's documentation is [https://docs.opendev.org/openinfra/refstack-client/latest/ available here]
  
 
== Resources ==
 
== Resources ==
Website:  http://refstack.org/<br />
+
'''Website:''' https://refstack.openstack.org/<br />
IRC:
+
More info here:
:Server:  irc.freenode.net
+
https://docs.opendev.org/openinfra/refstack/latest/contributing.html
:Channel:  #refstack
+
 
=== Etherpads ===
+
=== Repositories ===
==== DefCore ====
+
https://opendev.org/openinfra/refstack<br />
Much discussion, requirements definition and design for RefStack take place under the DefCore Umbrella.  So as not to lose this knowledge, it is incorporated within the RefStack pages.<br />
+
https://opendev.org/openinfra/refstack-client
https://etherpad.openstack.org/p/DefCoreElephant.4<br />
 
https://etherpad.openstack.org/p/DefCoreTestCriteria<br />
 
https://etherpad.openstack.org/p/DefCoreRefStackUseCases<br />
 
https://wiki.openstack.org/wiki/Meetings/DefCore
 
==== RefStack ====
 
http://eavesdrop.openstack.org/meetings/refstack/2014/<br />
 
  
=== Meetings ===
+
=== RefStack Meetings ===
Weekly IRC meeting:
+
For meeting info visit the following link:
:Thursdays 2200UTC in #meeting-alt
+
https://meetings.opendev.org/#Interop_Working_Group_Meeting
[[Meetings#DefCore_.2F_RefStack_Development_Meeting|DefCore/RefStack Development Meeting]]<br />
 
  
OpenStack-DefCore Bylaws Subcommittee Meeting
 
:Thu 3/13/2014  15:30 UTC
 
:+1-702-696-4520; or +1-866-409-2889; Participant Code: 261 942 3593
 
====Geolocated Meetings====
 
[[Meetings#DefCore_Progress_Update_Meeting|DefCore Progress Update Meeting]]<br />
 
: Agenda at https://etherpad.openstack.org/p/DefCoreElephant.4<br />
 
:More info to follow with distance access info, etc.
 
March working meeting:  3/?  Tentative location:  PistonCloud
 
:More info to follow
 
 
=== Blueprints ===
 
=== Blueprints ===
https://etherpad.openstack.org/p/RefStackBlueprint
+
(OLD)
 +
https://blueprints.launchpad.net/refstack<br />
 +
 
 +
=== Reviews ===
 +
https://review.opendev.org/q/project:openinfra/refstack<br />
 +
 
 
=== FAQs ===
 
=== FAQs ===
 +
 
=== Blogs, Articles, Etc. ===
 
=== Blogs, Articles, Etc. ===
 +
(OLD)
 
http://robhirschfeld.com/2014/01/07/defcore-critieria/
 
http://robhirschfeld.com/2014/01/07/defcore-critieria/
 +
 +
[[Category:InteropWG]]

Latest revision as of 15:01, 22 November 2021

This wiki might be outdated follow refstack's documentation for the current information: https://docs.opendev.org/openinfra/refstack/latest/index.html

More info about Interop Working Group can be found at: https://docs.opendev.org/openinfra/interop/latest/index.html

Toolset for testing interoperability between OpenStack clouds.

RefStack Design

RefStack provides the Interop Working Group, the tools for vendors and other users to run API tests against their clouds to provide the Interop Working Group 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 be used to validate whether and how well actual OpenStack installations fit the OpenStack Foundation's requirements for OpenStack branding. As determined through requirements analysis and specifications, it consists of a client that will gather OpenStack Tempest test results for the Stack under test, a User Interface for analyzing results, and a reporting structure that allows on-line and off-line options for submission for certification.

Requirements

Interop Working Group Requirements
Use Cases

Architecture

For a quick overview, see the RefStack Documentation

refstack-server

The RefStack server is comprised of two components: the API and the UI. The API contains the REST endpoints needed for a user to upload and retrieve test result data sets which are stored in a MySQL database. The UI is an AngularJS based front-end for browsing uploaded data and viewing how test results stack up against Interop Working Group capabilities.

refstack-client

The RefStack client is a Tempest wrapper that will run the Tempest API tests and will format the results in a way that the RefStack API expects. The client does the following things:

  • Extracts just the 'Passed' tests from the generated subunit file.
  • Retrieves the cloud provider ID (here, we use the Keystone service ID as the CPID), and associates it with the results.
  • Gives the ability to upload data to a RefStack server.

refstack-client's documentation is available here

Resources

Website: https://refstack.openstack.org/
More info here: https://docs.opendev.org/openinfra/refstack/latest/contributing.html

Repositories

https://opendev.org/openinfra/refstack
https://opendev.org/openinfra/refstack-client

RefStack Meetings

For meeting info visit the following link: https://meetings.opendev.org/#Interop_Working_Group_Meeting

Blueprints

(OLD) https://blueprints.launchpad.net/refstack

Reviews

https://review.opendev.org/q/project:openinfra/refstack

FAQs

Blogs, Articles, Etc.

(OLD) http://robhirschfeld.com/2014/01/07/defcore-critieria/