1. Open Container Initiative (@OCI_org) Certification Program
Rob Dolin
Jeff Borek
Jeff

2. Jeff Borek (@jeffborek)
Brief Introductions
Jeff Borek
OCI TB Certification WG Co-Chair
WW Program Director, Open Technologies, IBM
Rob Dolin
Senior Program Manager, Cross-Platform Interoperability team, Microsoft
Jeff

3. What is the OCI?
Jeff

4. What is the Open Container Initiative (OCI) ?
The Open Container Initiative provides an open source technical community within which industry participants may easily contribute to building a vendor-neutral, portable and open specification and runtime that deliver on the promise of containers as a source of application portability backed by a certification program.
Jeff

5. Who is the OCI ? OCI Membership (46 organizations as of May 2016)
Jeff

6. New OCI Members (announced Monday, 8/22)
Anchore
ContainerShip
EasyStack
Replicated
About 50 members as of August 2016:
Jeff

7. How is the OCI organized? OCI Governance Structure
OCI Members - see slides #5 and #6
Technical Development Community (TDC)
Open to any individual or any open source contributor
Each project has a set of maintainers
Trademark Board (TB)
One representative appointed by each OCI Member
Responsible for trademarks, certification, budget
Includes Certification Program WG and Public Relations Committee
Technical Oversight Board (TOB)
Responsible for managing conflicts including cross-project or high-level issues that cannot be resolved in the TDC
Also responsible for adding, removing, or re-organizing OCI Projects
Jeff

8. OCI Projects: (https://GitHub.com/OpenContainers/…)
What is the OCI doing?
OCI Projects: (
Runtime-Spec - OCI Runtime specification
Image-Spec - OCI Image Format specification
runc - open source reference implementation of runtime
Also:
ocitools - includes tools and tests; demo later
artwork, project-template, web
tob - for Technical Oversight Board (TOB) collaboration
Rob
Ask: Heard of; Viewed code; Submitted issue or PR

9. OCI Projects
Rob

10. What is the current state of the OCI specifications?
runtime-spec
a specification for the creation and lifecycle of a container
686 commits from 45 contributors
image-spec
a software shipping container image format spec with security and naming as components
240 commits from 16 contributors
Rob

11. What is the current state of the OCI specifications?
Runtime spec:
v1.0.0-rc1 (Jun 5th 2016)
v0.5.0 (Apr 12th 2016)
v0.4.0 (Mar 10th 2016)
v0.3.0 (Feb 5th 2016)
v0.2.0 (Jan 12th 2016)
v0.1.0 (Sep 11th 2015)
Image spec:
v0.4.0 (Aug 17th 2016)
v0.3.0 (Jul 18th 2016)
v0.2.0 (May 31st 2016)
v0.1.0 (May 6th 2016)
Rob

12. What is the current state of other OCI OSS projects?
runc
A reference implementation container runtime
2,682 commits from 176 contributors
OCI Tools
A collection of tools for working with the OCI runtime spec
354 commits from 14 contributors
Rob; NOTE: As of mid-August 2016, the OCI Tools repo has not been formally approved by the

13. What is the current state of other OCI OSS projects?
runc:
v1.0-rc (Jun )
v0.1.1 (Apr )
v0.1.0 (Apr )
v0.0.9 (Mar )
v0.0.8 (Feb )
v0.0.7 (Jan )
v0.0.6 (Dec )
v0.0.5 (Nov )
v0.0.4 (Sep )
v (Aug )
OCI Tools:
Rob

14. What open source code is available?
OCI Runtime reference implementation: runc:
OCI Tools:
Rob

15. Certification Program Background
Jeff

16. What does the certification working group do and what value can a certification program bring?
The Certification Program WG is a committee of the OCI Trademark Board working to propose a set of criteria for implementations to meet if they want to use OCI trademarks (Open Container Initiative, OCI Certified, etc.)
Implementers whose implementations meet the bar of OCI certification can use OCI trademarks in marketing their solution
Users/customers can look for OCI Certified implementations to know that they are getting interoperable solutions
Implementers who want to build solutions can leverage/target OCI interoperability surfaces rather than having to build for multiple, inconsistent interoperability surfaces
Jeff

17. Questions being considered by the OCI Cert WG:
What are key factors for establishing a certification program for container technology?
Questions being considered by the OCI Cert WG:
Implementations:
Runtime spec
Image format spec
Both
Levels of compliance:
MUST/REQUIRED == Compliant
MUST/REQUIRED + SHOULD/RECOMMENDED == Unconditionally compliant
Testing:
Automation vs. manual: Can we fully automate?
Lab vs. peer vs. self: What optimizes cost and compliance
Jeff

18. Demos
Rob

19. Demo: OCI Tools / Runtime
Rob

20. Demo: OCI Tools / Runtime
Rob

21. Demo: OCI Image Validator
Rob

22. Demo: OCI Image Validator
Rob

23. Certification Program Next Steps
Jeff

24. What other programs is OCI Cert WG looking at?
RSS 2.0 and Atom 1.0
Java/OpenJDK TCK
HTML
IoT - AllSeen / OCF
Networking
Jeff
and several others...

25. What questions have we considered?
Self-certification vs. Lab certification
Member-only vs. open to all
Tiers / Levels– different levels of certification
Products – different “products” that could get certified
Versioning – validation tied to versioning (ex: OF 1.0.x and OF 1.3.x) or not (ex: OpenStack Compatible)
Rob

26. · More discussion of certification program exception processes
What work is remaining?
· More discussion of certification program exception processes
· Runtime certification members-only or open to all?
· Membership requirement for using OCI trademarks?
Rob

27. How can you participate?
Jeff

28. Get involved with the OCI community!
Join the technical community and projects!
Weekly technical meetings open to all
IRC: #opencontainers at irc.freenode.net
GitHub
Mailing list:
Roadmap (milestones)
Consider joining and what role you would like to play in the initiative
Jeff

29. Open Q&A
Both