DefCore’s Tempest in a Docker Container (“tcup”)
Core via Crowd Sourcing
DefCore Co-Chairs
Rob Hirschfeld
Joshua McKenty
What is DefCore?
DefCore sets base requirements for all OpenStack
products by defining:
1) designated sections of code, an...
DefCore = Commercial Use
Uses of the OpenStack mark:
1. Community (non-commercial use)
2. Code (integrated release)
3. Com...
Overview: How do we do this?
One Committee, with
- 10 Principles
- 12 Criteria
- 75 Capabilities (and growing)
- 1 Scoring...
Not whole projects!
Core defined by tests
describing capabilities
So...
Projects must have tests
Core = parts of projects
...
DefCore Principles
Core = Tests+Designated Code
12 Criteria
Capabilities
Capabilities = Groups of API Tests, e.g.:
"block-snapshots" :
test_snapshot_create_get_list_update_delete,
te...
Capabilities Scoring Matrix
Capabilities << Tests
Score max 100
Non-Admin API
Scored per Release
Preliminary Havana
Enforc...
Community Feedback
DefCore Depends on Usage Data!
1. Users
2. Tools
3. Clients
Some Examples
Case 1: BananaCloud
Example Public Cloud
“mostly” using OpenStack
Active in community
“OpenStack Powered”
Case 2: SpRocket
Example Private Cloud
“heavily” using OpenStack
add missing core feature
Specialized code base, ok
“OpenS...
Case 3: “Mist” API Client
“OpenStack Compatible”
No Impact from DefCore, but…
1. should share their API use
2. add tests f...
Tools: RefStack and TCUP
Refstack, the Site
Community Interop Portal
Collects Test Results
Shows Compliance
Allows Comparison
Refstack, the Project
Primary Use: Runs the Public Site
Secondarily: Can be setup as private test
collector for QA team
no...
Why TCUP?
Goal: Make Tempest accessible
TCUP is for people who DON’T code
To run from desktops inside firewalls
With minim...
How TCUP Works
1. download
2. set creds
3. run
then TCUP does
the rest
TCUP Demo
ssh me@linuxbox
$ wget tcup.py
$ source openrc.sh
$ python tcup.py
sip & enjoy http://www.startrek.com/article/o...
Call to Action!
We need YOUR HELP
Review the Havana Core
Help designate sections
Participate in Refstack
Run TCUP on your ...
References
RefStack Wiki: https://wiki.openstack.org/wiki/RefStack
DefCore Wiki: https://wiki.openstack.org/wiki/Governanc...
Upcoming SlideShare
Loading in …5
×

What is OpenStack DefCore, Altanta Conference

1,329 views

Published on

Board Members, Rob Hirschfeld & Joshua McKenty, present about how OpenStack is defining the core capabilities of the project.

Published in: Software, Technology
1 Comment
2 Likes
Statistics
Notes
No Downloads
Views
Total views
1,329
On SlideShare
0
From Embeds
0
Number of Embeds
48
Actions
Shares
0
Downloads
55
Comments
1
Likes
2
Embeds 0
No embeds

No notes for slide

What is OpenStack DefCore, Altanta Conference

  1. 1. DefCore’s Tempest in a Docker Container (“tcup”) Core via Crowd Sourcing DefCore Co-Chairs Rob Hirschfeld Joshua McKenty
  2. 2. What is DefCore? DefCore sets base requirements for all OpenStack products by defining: 1) designated sections of code, and 2) must-pass tests of capabilities. These definitions use community resources and involvement to drive interoperability by creating the minimum standards for products labeled “OpenStack”.
  3. 3. DefCore = Commercial Use Uses of the OpenStack mark: 1. Community (non-commercial use) 2. Code (integrated release) 3. Commerce (products and services) DefCore covers #3 only!
  4. 4. Overview: How do we do this? One Committee, with - 10 Principles - 12 Criteria - 75 Capabilities (and growing) - 1 Scoring Matrix (per release)
  5. 5. Not whole projects! Core defined by tests describing capabilities So... Projects must have tests Core = parts of projects Not your mother’s core
  6. 6. DefCore Principles
  7. 7. Core = Tests+Designated Code
  8. 8. 12 Criteria
  9. 9. Capabilities Capabilities = Groups of API Tests, e.g.: "block-snapshots" : test_snapshot_create_get_list_update_delete, test_volume_from_snapshot
  10. 10. Capabilities Scoring Matrix Capabilities << Tests Score max 100 Non-Admin API Scored per Release Preliminary Havana Enforced for Juno
  11. 11. Community Feedback DefCore Depends on Usage Data! 1. Users 2. Tools 3. Clients
  12. 12. Some Examples
  13. 13. Case 1: BananaCloud Example Public Cloud “mostly” using OpenStack Active in community “OpenStack Powered”
  14. 14. Case 2: SpRocket Example Private Cloud “heavily” using OpenStack add missing core feature Specialized code base, ok “OpenStack Powered”
  15. 15. Case 3: “Mist” API Client “OpenStack Compatible” No Impact from DefCore, but… 1. should share their API use 2. add tests for untested APIs 3. reconsider non-must-pass
  16. 16. Tools: RefStack and TCUP
  17. 17. Refstack, the Site Community Interop Portal Collects Test Results Shows Compliance Allows Comparison
  18. 18. Refstack, the Project Primary Use: Runs the Public Site Secondarily: Can be setup as private test collector for QA team note: Does not use or require Docker!
  19. 19. Why TCUP? Goal: Make Tempest accessible TCUP is for people who DON’T code To run from desktops inside firewalls With minimal setup and configuration This minimizes community support required
  20. 20. How TCUP Works 1. download 2. set creds 3. run then TCUP does the rest
  21. 21. TCUP Demo ssh me@linuxbox $ wget tcup.py $ source openrc.sh $ python tcup.py sip & enjoy http://www.startrek.com/article/one- trek-mind-8-drink-for-thought
  22. 22. Call to Action! We need YOUR HELP Review the Havana Core Help designate sections Participate in Refstack Run TCUP on your cloud Rock us some +1s!
  23. 23. References RefStack Wiki: https://wiki.openstack.org/wiki/RefStack DefCore Wiki: https://wiki.openstack.org/wiki/Governance/DefCoreCommittee RefStack: https://github.com/stackforge/refstack

×