OCP Contribution Process

January 2019

Consume. Collaborate. Contribute.

Projects

Success through Communication and Participation

Consume. Collaborate. Contribute.

OCP Structure

OCP Board of Directors

OCP Foundation Staff

Incubation Committee

Project Leads

OCP Project Communities

OCP is made up 5 major functions. The Board sets the charter of the Foundation. Together with the Incubation Committee and Project Leads, the Foundation provides the OCP Project Communities a cohesive platform for collaboration.

The OCP Project Community is at the heart of any contribution. When member companies collaborate on a concept or when member companies share their expertise openly, this is done as a “Contribution.” There is NO IP assigned to the Foundation at any point.

Consume. Collaborate. Contribute.

OCP COMMUNITY: PROJECTS & SUB-PROJECTS

DC Facility

TELCO

HW MGMT

HPC

SECURITY

Open Sys FW

NETWORKING

ONL, ONIE, SAI, SONiC, CAMPUS BRANCH WIRELESS

STORAGE

JDA PROJECT ARCHIVAL

RACK & POWER

ADV COOLING SOLUTIONS POWER SHELF INTEROPERABILITY

SERVER

PCI 3.0 MEZZ

Accelerator Module

ODSA

MODULAR DC

OPENEDGE

OPENRMC

Consume. Collaborate. Contribute.

Do we want these listed in alphabetical order?

Project Info

Each of these Projects can be reached via their respective parent project:

Consume. Collaborate. Contribute.

SuProject to SubProject

Contribution Process:

Consume. Collaborate. Contribute.

How to Get Started?

There are many ways to publicly participate in the OCP Project Community.

  • Mailings

Join

  • Project Mailing Lists
  • Project Calls
  • Mailings

Drive

  • Project Focus
  • Thought Leadership
  • Mailings

Contribute

  • Specifications
  • Products
  • Mailings

Run

  • Project Leaders
  • IC Committee
  • Mailings

Attend

  • OCP Summit
  • OCP Meetings
  • OCP Panels
  • OCP Engineering Workshops
  • OCP Days
  • OCP Events

Consume. Collaborate. Contribute.

Ways to Contribute to OCP

Specs

Design
Files

Reference

Architecture

Tested Configs

White Papers

Case
Studies

Seminars

Testimonials

Videos

Embedded SW

Product
Recognition

Facility
Recognition

Consume. Collaborate. Contribute.

Member Contribution Requirements

Community Members

    • No Contribution Required
    • If they choose, they may make contributions
    • May seek OCP Accepted™ product recognition for their product contributions (based on an existing accepted Specification).

Silver

    • No Contribution Required
    • If they choose, they may make contributions
    • May seek  OCP Accepted™ or OCP Inspired™ product recognition for their product (based on an existing accepted specification).

Gold

    • Must make 1 contribution per year of membership*
    • May seek  OCP Accepted™ or OCP Inspired™ product recognition for their product (based on an existing accepted specification).

Platinum

    • Must make 2 contributions per year of membership*
    • May seek  OCP Accepted™ or OCP Inspired™ product recognition for their product (based on an existing accepted specification)..

*Opt-Out option available for Contributions.

Consume. Collaborate. Contribute.

Do we want to say “based on an existing accepted Specification & Design).” for Community?

Type

Pre-Requisites

Credit

Specification or

Design Package

1 Specification or 1 Design Package

  • Each Spec and/or Design Package must meet 3 out of 4 OCP Tenets
  • Each Spec must have one 1 identified supplier with readily available product within a reasonable amount of time (120 days).
  • Each Design package must have one 1 identified supplier with readily available product within a reasonable amount of time (120 days) and the Supplier must apply for the OCP Product Recognition Program (OCP Accepted™or OCP Inspired™ status and logo).

1 Credit

OCP Inspired™

Product

5 OCP Inspired™ Product SKUs on the Marketplace.

  • Must be based on an approved OCP Spec.
  • Must meet 3 out of 4 OCP Tenets
  • Each SKU must carry the OCP Inspired™ logo.
  • Each SKU must be readily available within 120 days and be visible on Supplier’s website for purchase.

5 SKUs

= 1 Credit

OCP Accepted™

Product

5 OCP Accepted ™ Product SKUs on the Marketplace.

  • Must be based on an approved OCP Spec.
  • Must meet 3 out of 4 OCP Tenets
  • Each SKU must carry the OCP Accepted™ logo.
  • Each SKU must be readily available within 120 days and be visible on Supplier’s website for purchase.

5 SKUs

= 1 Credit

OCP Contribution Credit Structure

Consume. Collaborate. Contribute.

Type

Description

Credit

Embedded SW

  • Initial Committers to a repository in either the OCP GitHub directory or an affiliate OCP Github directory (SONiC/ONIE/ONL etc)

- Member Companies that have contributed over 25% to a given repository within their current term.

  • Between 15-24% will receive 0.5 credit.
  • Anything less than 15% will be considered participation.

1 credit

Reference Architecture

A documented and tested solution comprising:

  • Two or more unique tested configurations (see above)
  • Two or more unique OCP Accepted™ Product SKUs.
  • > 50% content use of Orderable SKUs.

- The contributor must provide product test documentation, certification info, and configuration details about the reference architecture and warrants that the reference architecture works as documented.

- OCP shall be allowed to promote the contribution of reference architecture via the OCP Marketplace.

Case Dependent

(0.5-1 Credit per item)

OCP Ready™

Facility

1 OCP Ready Facility

  • Facility must meet all the requirements in the OCP Ready™ Checklist and Colo Site Assessment in current term
  • Assessment must be made annually to retain certification.
  • Renewals for the same facility will be 0.5 credit
  • Member must be a Colo SP.

1 credit

OCP Contribution Credit Structure Cont’d

Consume. Collaborate. Contribute.

Type

Description

Credit

Tested
Configuration

A documented and tested configuration using an OCP Inspired™ or OCP Accepted™ Product and configured with additional hardware and operating system software and application software (specific use)

- Testing plan/results, configuration details must be provided.

- Contributor warrants tested configuration will work in defined use case and can provide support service

- Contributor responsible for accuracy of info

- OCP may promote the contribution of tested configurations via the OCP Marketplace.

10 tested configurations = 1 Credit

White Papers &

Case Studies

A white paper or case study explaining details of your use of OCP Accepted™ or OCP Inspired™ Products within your infrastructure.

  • The white paper or case study must demonstrate 2 or more OCP tenets and be accepted by the Foundation and IC committee along with the appropriate agreements.
  • OCP shall be allowed to promote this on the OCP website or promotional materials.

Case Dependent

(0.25-1 Credit per item)

Educational Videos or

Quotable References or

OCP-centric Technology Seminars


Organized Plug-fests


Engineering Workshops

The Foundation may approve the following items with proper authorization and technical validation.

The below items must utilize of at least 2 OCP Tenets.

- Educational Videos for use of OCP Products or Reference Architectures

- Testimonials and quotable customer references for relevant OCP Products, Test Configurations and Reference Architecture

- Technology Seminars, when promoting the use of OCP Products, Test Configurations and Reference Architecture

- OCP shall be allowed to promote this on the OCP website or promotional materials.

Case Dependent

(0.5-1 Credit per item)

OCP Contribution Credit Structure Cont’d

Consume. Collaborate. Contribute.

Contribution Types and Associated Docs

Contribution Type

OCP Legal Requirements

OCP Foundation Submission Requirements

OCP Accepted™

OCP Inspired™

OCP Ready™

Comments

Specification

  • OCP Membership
  • OCP CRLA
  • CLA (OWF or OCP)
  • Certification Mark Agreement
  • Specification Doc.
  • Meets ¾ OCP Tenets
  • Completed Checklist
  • Must have identified 1 supplier that can build product.

NA

NA

Specs need to be open and intended for public consumption. Must have at least 1 identified supplier that will have sellable product in a reasonable amount of time (120 days).

Design

  • OCP Membership
  • OCP CRLA
  • CLA (OWF or OCP)
  • Certification Mark Agreement
  • Must be based on an existing approved spec.
  • Complete Design Files
  • Completed Checklist
  • Orderable SKUs

NA

N/A

Must be based on an approved OCP Spec.

If contributed to OCP, designs need to be open and intended for public consumption.

Embedded SW

  • Any OSI Approved License
  • Must be an OCP Software platform
  • Must be in the OCP GitHub directory or an OCP Github affiliate directory

Must be on an OCP Software platform.

Product

  • OCP Membership
  • OCP CRLA
  • Certification Mark Agreement
  • SP Agreement if needed
  • Must be based on an existing approved Spec.
  • Orderable SKUs
  • Completed Checklist
  • Provide Serviceability

X

X

Products must be submitted to the OCP Recognition Program (OCP Inspired™ or OCP Accepted™). Products must carry appropriate OCP Product logo to receive contribution credit and be visible on the Supplier’s website for purchase.

Facility

  • OCP Membership
  • OCP CRLA
  • Certification Mark Agreement
  • Colo SP Agreement
  • Must be based on OCP Colo Facility Guidelines
  • Completed Colo Site Assessment
  • Maintain Assessment thru term

X

Facility must be submitted to the OCP Facility Recognition Program and must carry OCP Ready™ logo to receive contribution credit and must be visible on Colo’s website.

R/As, White Papers, Case Studies, Metrics

  • OCP Membership
  • OCP CRLA
  • Certification Mark Agreement
  • Must be based on an existing approved Spec or Design
  • Must be based on OCP Products
  • Completed Checklist

NA

NA

R/As, white papers, case studies, metrics are very beneficial to our community. OCP Products must be part of the Product Recognition Program.

Consume. Collaborate. Contribute.

How to start a Spec/Design File/Reference Architecture Contribution?

  • All the above Contributions start with a legal document - Contribution License Agreement (CLA)
    • There are 2 types of CLAs accepted by OCP:
      • OWF-CLA - to sign the agreement click here
      • OCP-CLA - to sign the agreement click here
    • Have your Legal team review these and sign them.
  • If the CLA is complete, use the following OCP Specification Template and Design Package Guidelines to create your submission package.
  • If you want guidance from the OCP Project Community, please contact the respective Project Leads or OCP Foundation Staff. We will assist you in presenting your contribution to the community and collecting feedback.
  • Start the Consolidated Checklist as a way to track your progress. Requirements are stated on Slide 10-11..
  • If the Spec is complete, please present it to the respective Project Community. This creates awareness.
  • Ensure you have a supplier who can build your product. An OCP Solution Provider is prefered.
  • Complete the Checklist and present your final Spec to the Incubation Committee.
  • Upon approval from the Incubation Committee, it will be published on the OCP Contribution Database

Specs

Design
Files

Reference

Architecture

Consume. Collaborate. Contribute.

How to recognize your Products as OCP?

  • If your product is based on an existing approved OCP Spec, you can get contribution credit
    • Fill out the Consolidated Checklist
    • Refer to an existing Spec
    • Provide us the Design Collateral and you can recognize the product as OCP Accepted™.
    • If you don’t want to provide the design collateral and you are a tiered member, you can recognize your product as OCP Inspired™.
    • Sign a Certification Mark Agreement for the respective logo and sell your OCP Solution!
  • If you want to contribute your own spec, follow the steps on Slide 14 and get started. You can get up to 3 contribution credits instantly (1 for spec, 1 for design collateral, 1 for product recognition).
  • If you want to use the OCP Marketplace to showcase your OCP recognized products, become an OCP Solution Provider!

Product
Recognition

Consume. Collaborate. Contribute.

Do we want to note that you can still get OCP Accepted™ if someone else has given the design files already?

Specification

OCP Inspired™ Product Recognition

  • Available to Silver/Gold/Platinum members
  • Design Package not required
  • Supported SKUs
  • Orderable by anyone

OCP Accepted™ Product Recognition:

  • Available to all members
  • Requires Design Package Contribution
  • Supported SKUs
  • Orderable by anyone

Product Recognition Process

* Specs, Design Package, and Products can come from same or different companies

Use an existing Spec to build your product or contribute your own Spec

NO IP Assignment

Consume. Collaborate. Contribute.

Where to find current and future specs and design files on our website?

Approved Contributions: https://www.opencompute.org/contributions

Marketplace: OCP Accepted™, OCP Inspired™, and OCP Ready™ Solutions

https://www.opencompute.org/products

Check Project Wiki Pages for Work in Progress

Consume. Collaborate. Contribute.

Products that comply 100% with an OCP accepted specification and the design files are open sourced and available.

Products that comply 100% with an OCP accepted specification and are available from a Gold, Silver or Platinum member of OCP

Worldwide Delivery, Service, Support Network

OCP Product Recognition Program

Consume. Collaborate. Contribute.

How to recognize your facility as OCP?

  • If your facility is ready to accept OCP Solutions, you can get contribution credit
    • Check to see if your facility meets the OCP Colo Facility Guidelines for OCP Racks.
    • Complete the OCP Ready Colo Site Assessment.
    • Provide us your Assessment and get IC Approval.
    • Sign a Certification Mark Agreement for the respective logo and market the site with the logo
    • All OCP Ready™ Facilities will be listed on the OCP Marketplace.
  • Each site is 1 Contribution credit and each renewal is 0.5 credit.

Facility
Recognition

Consume. Collaborate. Contribute.

Reference Architecture Contribution Process

  • Leverage ORDERABLE SKU information collected at time of contribution and distributed by Foundation.
  • Leverage TESTED CONFIG. information provided by and maintained by contributor.
  • Solution Providers or ODM’s validation any new TESTED CONFIGS.
      • Charges for validation is defined in support contract.
      • Solution Provider receives HOURS credit for contributing a new TESTED CONFIG.
  • Opportunity for additional contribution by SP (new TESTED Configs, new REFERENCE ARCHITECTURE)

OCP SKUs

STEP 2. Leverage TESTED CONFIGS

Applications

Orchestrators

Utilities

Compute Nodes

FPGA Nodes

NW Switchgear

NW Aggregators

NAS Storage

DAS Storage

REFERENCE

ARCHITECTURE

Step 3. Testing of Full HW & SW Stack

Leverage

TESTED CONFIGS

ADD new

TESTED CONFIGS

CONTRIBUTION

OPPORTUNITY

STEP 1: Start with

ORDERABLE SKUs

CONTRIBUTION

OPPORTUNITY

CPU

Storage

Memory

Mechanical

Power

OS

FW/BIOS

TESTED

CONFIGS

Reference

Architecture

Consume. Collaborate. Contribute.

Tested Configuration Contribution Process

If you are testing application software or system software on an OCP recognized product, you can earn up to 1 contribution credit.

  • Start the Consolidated Checklist as a way to track your progress.
  • Provide us with your test plan/results and configuration details.
  • Submit your Tested Configuration to the Project Leads in the respective Project and get approval from the IC.
  • If you are a OCP Solution Provider, OCP will publish your tested configurations on the OCP Marketplace.

Tested Configs

Consume. Collaborate. Contribute.

Embedded Software Contribution Process

  • If you are contributing to an OCP Github or OCP Affiliated Github Directories, you can get contribution credit
    • Fill out the Software Consolidated Checklist
    • Tell us what your Github ID is and what company you are working with.
    • OCP will give 1 contribution credit to your company if you are the initial committer on a repository or if you are contributing more than 25% to an existing repository.
    • If you are contributing between 15-25%, you will earn 0.5 credits.
    • Let us know what you are doing!

Embedded SW

Consume. Collaborate. Contribute.

White Paper and Case Study Contributions

If you are using an OCP Solution in your infrastructure or want to share an experience with an OCP recognized product, you can earn up to 1 contribution credit.

White Papers

Case
Studies

Consume. Collaborate. Contribute.

OCP Tenets

Efficiency

  • Platform Performance
  • Reduction of Infrastructure Cost
  • Power Conversion & Delivery
  • Cooling

Scalability

  • Fast, Simple, Tool-less Maintenance
  • OCP Compliant Management Tools
  • Documentation

Openness

  • Open Source
  • Open Interfaces
  • OCP Compatible

Impact

  • Efficiency Gains
  • New Technology
  • Leverage/Empower Prior Contributions
  • Supply Chain

New OCP contributions must create meaningful positive impact within the OCP ecosystem. This can be attained by introducing efficiency gains, introducing new technologies and products that are valuable for scale out computing, creating a multiplier effect by building on top of already existing OCP solutions, and enabling a more robust supply chain by contributing alternative compatible solutions.

A key OCP tenet is efficient design. Aspects that can be considered include (but aren’t limited to) power delivery and conversion, thermal efficiency, platform performance (per-W for example), reducing overall infrastructure costs, reducing code weight, reducing latencies and more.

OCP contributions must be scalable. This means that the technology is designed with the right supporting features to allow for its maintenance in large scale deployments. This includes physical maintenance, remote management, upgradability, error reporting and appropriate documentation. Management tools should strive to adhere to the guideline provided by the OCP Hardware Management Project. Documentation should enable adopters towards a successful deployment, providing guidance on equipment installation, turn on and configuration, as well as physical and remote service.

OCP encourages as much open source contribution as possible, but understands that in certain cases 100% open source contriution may not be possible. Whether fully open source or not, a contribution should strive to comply with a set of already existing open interfaces, at the very least provide one. Providing a solution compatible with already existing OCP contributions is one way to implement existing (open) interfaces.

Consume. Collaborate. Contribute.

Thank you.

For any questions, please do not hesitate to reach us at membership@opencompute.org

Consume. Collaborate. Contribute.

Consume. Collaborate. Contribute.

OCP Contribution Process 2019 - Google Slides