Open Container Initiative (@OCI_org) Certification Program https://opencontainers.org Rob Dolin (@RobDolin) Jeff Borek (@JeffBorek) Jeff

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

What is the OCI? Jeff

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

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

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

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

OCI Projects: (https://GitHub.com/OpenContainers/…) What is the OCI doing? OCI Projects: (https://GitHub.com/OpenContainers/…) 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

OCI Projects Rob

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 https://github.com/opencontainers/runtime-spec image-spec a software shipping container image format spec with security and naming as components 240 commits from 16 contributors https://github.com/opencontainers/image-spec Rob

What is the current state of the OCI specifications? Runtime spec: https://github.com/opencontainers/runtime-spec/releases 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: https://github.com/opencontainers/image-spec/releases 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

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

What is the current state of other OCI OSS projects? runc: https://github.com/opencontainers/runc/releases v1.0-rc (Jun 3 2016) v0.1.1 (Apr 25 2016) v0.1.0 (Apr 12 2016) v0.0.9 (Mar 10 2016) v0.0.8 (Feb 10 2016) v0.0.7 (Jan 26 2016) v0.0.6 (Dec 11 2015) v0.0.5 (Nov 20 2015) v0.0.4 (Sep 11 2015) v0.0.2.1 (Aug 25 2015) OCI Tools: https://github.com/opencontainers/ocitools Rob

What open source code is available? OCI Runtime reference implementation: runc: https://github.com/opencontainers/runc OCI Tools: https://github.com/opencontainers/ocitools Rob

Certification Program Background Jeff

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

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

Demos Rob

Demo: OCI Tools / Runtime Rob

Demo: OCI Tools / Runtime Rob

Demo: OCI Image Validator Rob

Demo: OCI Image Validator Rob

Certification Program Next Steps Jeff

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...

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

· 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

How can you participate? Jeff

Get involved with the OCI community! Join the technical community and projects! Weekly technical meetings open to all https://github.com/opencontainers/specs#weekly-call IRC: #opencontainers at irc.freenode.net GitHub https://github.com/opencontainers/runtime-spec https://github.com/opencontainers/image-spec https://github.com/opencontainers/ocitools Mailing list: dev@opencontainers.org Roadmap (milestones) https://github.com/opencontainers/runtime-spec/milestones https://github.com/opencontainers/image-spec/milestones Consider joining and what role you would like to play in the initiative https://opencontainers.org/join Jeff

Open Q&A https://opencontainers.org Both