Juniper's plans to reboot the OpenContrail community and transition from a Juniper-led project to a community led project. We need your help. Get involved.
2. Background
• The OpenContrail community isn’t where we want it
• The decision was made in 2016 to fix this and some plans
were set in motion:
• Bring in an expert on open source and strategy (Randy Bias)
• Hire a community manager (TBD)
• Rethinking Juniper’s community engagement model began
• ON THE TABLE: SDLC model, packaging, community code contribution
process, JNPR “in the open” development, and transition from single-
entity project to multi-entity project
2
4. Common Vision
• OpenContrail Vision: OpenContrail seeks to become a ubiquitous global
network fabric that is agnostic extending across all cloud infrastructure. It
will provide a single point of control, visibility, and management globally for
all networks and network security. It will become the most broadly adopted
and highest quality SDN overlay technology available.
• Community Vision: The OpenContrail community will be open and
inclusive, while also providing strong technical and architectural oversight
where competitive ideas are welcome, but rough consensus and running
code always win.
4
6. Dedicated Steward
• Dedicated Community Manager:
• Wears a single hat; no responsibility for commercial product delivery
• Acts as “product manager” for open source community
• Advocates for community as a whole
• Educates all stakeholders on community engagement
• Juniper: engineering, product mgmt, product marketing, and management
• Greater OpenContrail stakeholders
• Independent of commercial Contrail BU
• reports directly to Randy Bias
• Coordinates “reboot” of OpenContrail community
6
7. Shared Governance
• The community governs itself
• Considered and step-wise transition from Juniper-centric to community
driven
• Governance ≠ Foundation
• Governance models exist for open source without foundations attached
to them; we need rules of engagement, not high levels of overhead
• All options are on the table:
• Traditional Foundation: CNCF, Linux Foundation, Apache Software
Foundation, etc.
• New Foundation: OpenContrail Foundation
• No Foundation
7
8. Why?
• Vibrant community-run project, not driven by a single entity
• Enrich community and encourage greater participation
• Leverage the community to increase quality, velocity, and
adoption
• Drive 100-1000x more OpenContrail deployments
• Deliver on a global ubiquitous network fabric
8
9. Stakeholder Alignment
• Juniper has significant investments in OpenContrail and
needs paths to recognizing revenue
• Other stakeholders want more commercial options
• All stakeholders need to see a strong technical leadership
and architectural oversight for foreseeable future
• All stakeholders want to see broader adoption
• All stakeholders want to see highest quality possible
• It’s the network after all
• Production-grade, secure, and most broadly adopted
9
11. Draft Timeline
11
Call for
governance
summit
participants
(OpenStack
Summit
Boston 2017)
JNPR hires
community
manager
Governance
Summit
(JNPR HQ
and/or Conf
Call)
May June H2’2017 2018
All build/
release/
packages/
containers in
public
Finalize
governance
and/or
foundation
plans
Engage Linux
Foundation
Call for
feedback
from
community on
plans
Juniper 1:1
convos with
key
stakeholders
Engage
broader
ecosystem
Implement governance
and/or Foundation
+
New release of
OpenContrail connected
to changes in JNPR biz
model for commercial
ContrailDevelop
strawman of
community
values and
objectives
Randy PTO
12. Participating in the “Founding”
• Who? Anyone with an interest in OpenContrail being wildly
successful
• Special perks for being a “founding” member? Nope
• Sign up to the Google Group here:
• http://tinyurl.com/opencontrail-founding
• Thank you in advance!
12