1 of 28

CNCF TOC Meeting

Apr 19 2017

2 of 28

LF Antitrust Policy Notice

CNCF meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws.

Examples of types of actions that are prohibited at CNCF meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy. If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.

2

3 of 28

Meeting Logistics

Time: Apr 19 800AM-900AM (Pacific)

http://uberconference.com/cloudnative

Conference Number: +1-415-579-0198 No Pin Needed

3

4 of 28

TOC - Members Present Today

4

Company

Two Sigma

Cisco

CoreOS

Docker

Google

Joyent

Mesosphere

Weaveworks

Note: TOC meetings shall require a quorum of two-thirds of the TOC total members to take a vote or make any decision. If a TOC meeting fails to meet the quorum requirement, discussions may proceed, however there shall be no voting or decisions.

Name

Camille Fournier

Ken Owens

Jonathan Boulle

Solomon Hykes

Elissa Murphy

Brian Grant

Bryan Cantrill [conflict]

Benjamin Hindman

Alexis Richardson

Email

skamille@gmail.com

kenowens@cisco.com

jonathan.boulle@coreos.com

solomon.hykes@docker.com

elissam@godaddy.com

briangrant@google.com

bryan@joyent.com

benh@mesosphere.io

alexis@weave.works

5 of 28

Agenda

Standard Agenda

Networking WG Readout
Community Presentation: Vitess
WG Overview

AOB

Marketing
Events
Reminders
Next Time

5

6 of 28

New CNCF Projects: containerd + rkt

http://containerd.io/ (see github for proposal)
http://rkt.io (see github for proposal)

6

7 of 28

CNCF WG Updates

CI (lead: Camille Fournier)

Storage (lead: Ben Hindman)

https://github.com/cncf/wg-storage (see this doc too)

Networking (lead: Ken Owens)

https://github.com/cncf/wg-networking

Cluster (lead: Bryan Cantrill)

7

8 of 28

Networking WG Update

Scope of WG: https://github.com/cncf/wg-networking

Explore cloud native networking technology and concepts around a container networking interface specification
Initial focus on network connectivity of containers and removing allocated resources when the container is deleted.
Initial specification defined by CNI should be adopted as it is simple to implement, has multiple plugins, and is widely adopted.
Address network model definition, policy, and services frameworks

8

9 of 28

Networking WG Update: Goals

Define guidelines for a network interface specification focused on connectivity and portability.
Support dynamic (automated/API) provisioning and deprovisioning network resources through this interface.
Support group of entities that are uniquely addressable that can communicate amongst each other. This could be either an individual container, a machine, or some other network service (e.g. load balancing, firewall, VPN, QoS, Service Discovery). Containers can be conceptually added to or removed from one or more networks.
Focused on cloud native application patterns (not existing enterprise architecture patterns) initially.
Define policy framework for network isolation

10 of 28

Networking WG Update: Non Goals

Provide or dictate an implementation

This includes dictating plugin lifecycle management
Plugin distribution
Protocol-level authn/authz
Plugin discovery

Not going to make a one network standard for all
Not going to focus on individual projects per service but rather projects that model network services and patterns
Not going to be prescriptive but more reference guidelines and patterns

11 of 28

Networking WG Update: Initial Scope

Recommend CNI Spec and Plugins be adopted as initial network interface specification and plugins focused on connectivity and portability
Adopt implementations of CNI that have traction in the cloud native ecosystem
Define cloud native networking patterns and create related model definitions
Define the Policy framework and network services model

CNI to version 1.0. Specification only

Recommend : Incubating stage

Add value to cloud native computing (i.e., containerization, orchestration, microservices, or some combination) and be aligned with the CNCF charter.
Have all code under an ASL 2.0 license, or another license explicitly approved by the Governing Board.
Agree to transfer any relevant trademarks to CNCF and to assist in filing for any relevant unregistered ones.
Document that it is being used successfully in production by at least three independent end users which, in the TOC’s judgement, are of adequate quality and scope.
Have a healthy number of committers. A committer is defined as someone with the commit bit; i.e., someone who can accept contributions to some or all of the project.
Demonstrate a substantial ongoing flow of commits and merged contributions.
Since these metrics can vary significantly depending on the type, scope and size of a project, the TOC has final judgement over the level of activity that is adequate to meet these criteria

Plugins?

CNI incubating we help tighten, close gaps (test hosts), and clean documentation or we ask CNI to get to Version 1 first?

Make it clear what projects get from CNCF - what's the goal drive adoptions, build community, provide best practices

12 of 28

Networking WG Update: Get Involved

Join us!

GitHub: https://github.com/cncf/wg-networking
Send a PR to the README to add yourself to the team
Next meeting is April 26th:

https://github.com/cncf/wg-networking#meeting-times

13 of 28

Designed to be the best performing, scalable and most available NewSQL storage solution in the Cloud

https://github.com/youtube/vitess

Vitess

14 of 28

Database Landscape

NoSQL

RDBMS

NewSQL

Scalability

Features

The current storage market is divided into two segments: RDBMS and NoSQL.

On the RDBMS side, we have MySQL, Postgres and other commercial software including those running on mainframes. They offer strong data features. However, they can’t scale out.

On the other end of the spectrum, we have NoSQL solutions like Mongo and Cassandra. They scale out of the box, but lack features like transactions, indexes, etc.

NewSQL is an emerging category that offers the best of both worlds. This is a new market segment, and multiple players are needed. Users are coming from both ends of the spectrum and they’ll want to see multiple options to choose from. Today, we have Cockroach, TiDB, Cloud Spanner and Vitess.

More than Vitess vs. another NewSQL, it’s NewSQL vs. NoSQL or NewSQL vs. RDBMS.

15 of 28

Vitess Strengths

Battle tested for 6 years at YouTube
Site availability of 99.999 or greater
Lowest latency durable NewSQL storage �powered by MySQL
Simple and intuitive SQL based API
Seamless scalability and manageability �from small to arbitrarily large installations

16 of 28

Rich Feature Set

Cluster management
Resharding automation
Query services / SQL support
Production optimized

17 of 28

Architecture

shard

vtgate

app server

mysqld

vttablet

master

vtgate

big data

Vitess

etcd

mysqld

vttablet

mysqld

vttablet

replicas

mysqld

vttablet

big data replicas

mysqld

vttablet

vtctld

App

18 of 28

Vitess Community

Production & Testing

Contributions

Flipkart . JDBC & bulk DML features

Hubspot . MySQL compatibility

StitchLabs . Static map index

PixelFederation . PHP PDO

Slack . DBA statements

19 of 28

Vitess by the Numbers

Started 2010

4,000+ stars

500+ forks

11,000+ commits

79 contributors

92+ Slack members

vitess.io

github.com/youtube/vitess

20 of 28

Vitess Fit for CNCF

Cloud native DNA: built to run on Borg�
Early adopter of k8s and gRPC

Strong advocates of StatefulSet�

Brings scalable MySQL to the cloud

Why move to a foundation:

Vitess has grown beyond YouTube. There are now multiple stakeholders that depend on it. Featuring it as a standalone project will more accurately represent its use and adoption.

Why CNCF:

Vitess was one of the few open source projects that was built to run on Borg, before kubernetes was born.

We started collaborating with k8s very early on (early 2015). Apart from integrating with its features, we’ve also been driving some of them.

Same with gRPC, where we pushed for making Python more stable.

We’ve always been eager to integrate with other cloud features or products that are not yet in CNCF. For example, etcd & Consul.

There’s still skepticism in the community over running DBs like MySQL in containers. Vitess encourages and proves that it’s practical. StitchLabs is a shining example; They run Vitess at high QPS on GKE.

21 of 28

AOB / Reminders

22 of 28

Marketing

CTA to help with messaging / positioning - talk to Mark Coleman <mark@implicit-explicit.com>

Please also keep up discussions on TOC list, see eg multiple threads from Feb 2017 here

22

23 of 28

CloudNativeCon/KubeCon North America

Main CNCF Events for 2017:

Dec 6th - 8th: CloudNativeCon/KubeCon NA (Austin)

http://events.linuxfoundation.org/events/cloudnativecon-and-kubecon-north-america
CFP is open: submit talks now! (closes August 21st 2017)

Sponsorships open: sponsor@cncf.io

23

24 of 28

Upcoming CNCF Sponsored Events

CNCF is sponsoring and helping program content at the following events. We have travel funding available for TOC members (and possibly others) who would be willing to travel:

OpenStack Kubernetes Day, Boston, 5/2
Open Source Summit, Tokyo, 5/31-6/2

And co-located Automotive Linux Summit

LinuxCon ContainerCon CloudOpen, Beijing, 6/19-20

Please email dan@linuxfoundation.org and kschultz@linuxfoundation.org

24

25 of 28

AOB/Cadence

Last meeting slides on 4/5/2017
Meeting Cadence Reminder

First and third Wednesday of every month
Calls without TOC quorum will still be used to review issues

Next Meeting: 5/3/2017

25

26 of 28

Reminder: Reference Architecture

End User Reference Architecture voted* through (big thank you to Ken & co.)

CNCF End user reference architecture

Please go ahead and USE the material!

Contribute: https://github.com/cncf/landscape

�Example: Redpoint/CNCF Landscape https://raw.githubusercontent.com/cncf/landscape/master/landscape/CloudNativeLandscape_v0.9.4.jpg

26

27 of 28

Thank You

27

28 of 28

Projects: Pipeline

libStorage (storage API) → Storage WG
NATS (pubsub)

TOC sponsor: Alexis Richardson (working on project proposal and legal issues moving to ASLv2)

Minio (storage / more maturity in terms of adoption needed; will be discussed later)
OpenZipkin (need to reach out and needs more discussion)
CockroachDB (distributed SQL DB)
GitLab

28