OpenStack Summit Boston, May 2017

Catherine Diep (IBM, RefStack)

Chris Hoge (OpenStack Foundation)

Kurt Garloff (T-Systems)

Does My App or Tool Work on OpenStack Cloud X? Use RefStack to Find Out ...

A simple
Universe

Public

Public

Public

Private

Integrated Hybrid

?

The OpenStack Universe

Freedom

Four Opens

Thousands of possibilities to configure the services

Selections of Services (Core / BigTent)

Private / Hybrid / Public

Public vs. Managed Private vs. Distro vs. DIY

... allow you to fulfill even exotic needs.

Fragmentation

Chaos

Well understood choices

User viewpoints

Cloud transformation is a significant investment -- is it future proof?

Will my cloud-native app work on (OpenStack based) cloud X?

OpenStack seems so chaotic ... Is it really enterprise-ready?

Can I do cloud-bursting for my app from my private cloud to public?

Can I use tool Y on both my private cloud X and public cloud Z?

Make Interoperability Transparent

Define measurable standards

Test against standards

Collect and publish results

InterOp Guidelines

RefStack Client

RefStack Server

Interop Working Group

  • OpenStack Foundation Board commissioned working group to formalize an interoperability guideline consisting of:
    • Capabilities that must be present as part of the product API.  These capabilities are measured by set of must-pass tests.
    • Designated Sections that are the upstream OpenStack code that must be present in the product.
  • Complying with this guideline is required to qualify for the OpenStack Powered trademark for public & private clouds, and distributions.

Interop Working Group was formerly known as DefCore

     RefStack  

 There are two parts in the RefStack project:

  • RefStack Client
    • RefStack Client is a command line tool that runs test tools (Tempest), summarizes results, and communicates with the refstack api.  Vendors can use refstack client to run the tests themselves in a controlled and repeatable way.
  • RefStack Server 
    • RefStack API is a central repository for the collection of results and is currently hosted at https://refstack.openstack.org/ . It can also be hosted locally within any organization's infrastructure.
    • RefStack UI is a web interface for interacting with data collected with the api and client ( https://refstack.openstack.org/ ).

RefStack Client

  • RefStack provides a one-step setup command (setup_env) which takes care of installation of all dependencies including Tempest. https://github.com/openstack/refstack-client/blob/master/README.rst
  • Testing
    • Currently based on Tempest Test Suite.
    • By default, RefStack will install a specific Tempest SHA which was used by the DefCore committee to define the must-pass tests.  RefStack also provides options allowing users to override the default Tempest version.
    • Once refstack-client is installed, Tempest is located at <refstack-client home directory>/.tempest.
  • Uploading results
    • JSON format result that complying with the RefStack result schema
    • Data can be uploaded anonymously or with signature

RefStack Website

  • Users can view and manage test results.

     
  • Allows users to compare their results to guidelines.

Viewing Guidelines

Click here to get test list matching selected guideline and target program

selected guideline

Interpreting Test Results

On the results report page for each test run, a user can check result against multiple guideline versions and target programs.

Can view all passed tests by clicking on the count.

Compliance with the selected guideline and target program is denoted by the percentage and the colored YES/NO.

  • OpenStack Powered Storage
  • OpenStack Powered Compute
  • OpenStack Powered Platform

Three Powered Trademarks

  • New major programs?
  • Additions to existing programs?

New Powered Trademarks?

  • Allowing new major programs
  • Adding program extensions
    • Can specify dependencies
  • Mostly stays the same
    • Capabilities with tests
    • Designated sections with code

Interop Guidelines v2.0

  • Encouraging stakeholders to build their own guidelines.
  • Interop Working Group will maintain control of official trademark eligible guidelines.
  • Goal is project owners should define minimums for interop.

Community Driven Guidelines

  • NFV

Proposed Platforms for 2018

  • DNS (Designate)
  • Orchestration (Heat)
  • Secrets (Barbican)
  • Container Orchestration (Magnum)
  • Database (Trove)
  • Big Data (Sahara)

Proposed Extensions for 2018

RefStack Future plans

  • Accept any test result (using Tempest Test Suite or not) that adheres to RefStack result schema. 
  • Facilitate checking result against customized guidelines

Community defined guidelines

Outlook

Better Transparency & More Interoperability

Service Coverage

Services Covered

OpenStack powered Compute

OpenStack powered Object Storage

OpenStack powered Orchestration ?

OpenStack powered XYZ ...

Network
Standard X

Image
Standard Y

New Vertical Programs

Service Coverage

Services Covered

OpenStack powered Compute

OpenStack powered Object Storage

OpenStack powered Orchestration ?

OpenStack powered XYZ ...

Network
Standard X

Image
Standard Y

NFV

Custom Profiles

Tool B requirements

Service Coverage

Services Covered

OpenStack powered Compute

OpenStack powered Object Storage

OpenStack powered Orchestration ?

OpenStack powered XYZ ...

Network
Standard X

Image
Standard Y

Application A requirements

Allows to finally get an answer to the initial question: Does app A or tool B work on OpenStack Cloud X?

Custom Profiles

1. Understand your application/tool

 - API calls

 - Expected behavior

2. Create tests

 - reuse existing tempest tests

 - fill gaps (tempest and beyond)

3. Create test list (custom profile)

 - schema v2 will help ...

4. Upload to refstack server

 

 

Taxanomy of custom profiles

1. Private custom profiles:
Answering question privately
 

2. Sharing of custom profiles:

E.g. User to service provider ...
 

3. "Official" special profiles (?):
Public testability
Curation process?

 

4. Trademark guidelines

Board approval

Help us!

Feedback

Questions

Contributions

 

Interop Working Group

RefStack Project

Tempest Project

 

Talk to us (Chris, Catherine, Kurt, Egle, Mark, Luz, ....)

Using RefStack

By Kurt Garloff

Using RefStack

Catherine Diep, Chris Hoge, Kurt Garloff: Does My App or Tool Work on OpenStack Cloud X? Use RefStack to Find Out ... Presentation for the Boston OpenStack Summit (May 2017),

  • 825
Loading comments...

More from Kurt Garloff