Jump to: navigation, search

Difference between revisions of "RefStack"

m (Reviews)
m (Change doc references from DefCore to InteropWG)
(4 intermediate revisions by one other user not shown)
Line 3: Line 3:
 
== RefStack Design ==
 
== RefStack Design ==
  
RefStack provides the [[Governance/DefCoreCommittee|DefCore Committee]] the tools for vendors and other users to run API tests against their clouds to provide the DefCore committee with a reliable overview of what APIs and capabilities are being used in the marketplace. This will help to guide the DefCore-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.
+
RefStack provides the [[Governance/InteropWG|Interop Working Group]], a.k.a. DefCore committee, 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 ===
 
=== Requirements ===
  
[[RefStack/DefCore_Requirements|DefCore Requirements]]<br />
+
[[RefStack/DefCore_Requirements|Interop Working Group Requirements]]<br />
 
[[RefStack/UseCases|Use Cases]]<br />
 
[[RefStack/UseCases|Use Cases]]<br />
  
 
=== Architecture ===
 
=== Architecture ===
'''For a quick overview, see the''' [https://github.com/stackforge/refstack RefStack README]<br />
+
'''For a quick overview, see the''' [https://github.com/openstack/refstack RefStack README]<br />
  
 
==== refstack-server ====
 
==== 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 DefCore capabilities.
+
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 ====
 
==== refstack-client ====
Line 23: Line 23:
  
 
== Resources ==
 
== Resources ==
'''Website:'''  http://refstack.net/<br />
+
'''Website:'''  https://refstack.openstack.org/<br />
Mailing list: fits@lists.openstack.org<br />
+
Mailing list: openstack-dev@lists.openstack.org<br />
 
IRC:
 
IRC:
 
:Server:  irc.freenode.net
 
:Server:  irc.freenode.net
Line 44: Line 44:
 
=== Reviews ===
 
=== Reviews ===
 
[https://review.openstack.org/#/q/status:open+openstack/refstack,n,z Gerrit RefStack Reviews]<br />
 
[https://review.openstack.org/#/q/status:open+openstack/refstack,n,z Gerrit RefStack Reviews]<br />
[https://review.openstack.org/#/q/status:open+openstack/refstack-client,n,z Gerrit RefStack-client Reviews]
 
  
 
=== FAQs ===
 
=== FAQs ===
Line 51: Line 50:
 
http://robhirschfeld.com/2014/01/07/defcore-critieria/
 
http://robhirschfeld.com/2014/01/07/defcore-critieria/
  
[[Category:Defcore]]
+
[[Category:InteropWG]]

Revision as of 23:58, 9 December 2016

Toolset for testing interoperability between OpenStack clouds.

RefStack Design

RefStack provides the Interop Working Group, a.k.a. DefCore committee, 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 README

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.

Resources

Website: https://refstack.openstack.org/
Mailing list: openstack-dev@lists.openstack.org
IRC:

Server: irc.freenode.net
Channel: #refstack

Launchpad home page: https://launchpad.net/refstack

Contains links to blueprints, bugs and other project tracking information

Repositories

https://github.com/openstack/refstack
https://github.com/openstack/refstack-client

RefStack Meetings

Weekly IRC meeting: Meeting page

Blueprints

https://blueprints.launchpad.net/refstack

Reviews

Gerrit RefStack Reviews

FAQs

Blogs, Articles, Etc.

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