+1

On Fri, Jan 13, 2017 at 7:49 AM, Chris Aniszczyk via cncf-toc <cncf-toc@...> wrote:

Hey CNCF TOC community, it's time to vote on the linkerd (https://linkerd.io/) proposal as an inception level project, you can view the proposal below in this email or on GitHub: https://github.com/cncf/toc/pull/25

Please vote +1/0/-1

---

Name of project: linkerd

Description: Linkerd is an open source service mesh for cloud-native applications. It is a layer 5/7 proxy that provides fully decentralized request-level reliability and optimization to service communication, including latency-aware load balancing, retries, failure handling, circuit breaking, and deadlines. It provides granular metrics (both of itself and of downstream services), distributed tracing, TLS, a powerful logical routing layer, and integration with most common service discovery mechanisms.

Applications use linkerd by proxying HTTP, gRPC, or Thrift calls through a local linkerd instance. In many cases, integration with linkerd is a config change (e.g. setting an http_proxy environment variable) rather than a code change. Linkerd acts as a transparent proxy, and so a call to (e.g. "http://foo/bar") will be routed to the appropriate cluster, resolved in service discovery, load balanced, retried, and returned without application code being aware.

Linkerd is built on top of Finagle (https://twitter.github.io/finagle/), the high-concurrency RPC library that powers companies like Twitter, Soundcloud, Pinterest, and ING Bank. By staying close to the Finagle codebase, linkerd takes advantage of Finagle’s extensive production usage (https://github.com/twitter/finagle/blob/develop/ADOPTERS.md). Linkerd’s primary author is a core contributor to Finagle.

Sponsor / Advisor from TOC: Jonathan Boulle <jonathan.boulle@...>

Unique Identifier: linkerd

License: Apache License v2.0

Maturity Level: Inception

Source control repositories: https://github.com/linkerd

Initial Committers (leads): Oliver Gould (Buoyant) [@olix0r] and Alex Leong (Buoyant) [@adleong]

Infrastructure requirements: CI and potentially CNCF Community Cluster access. We run integration tests per commit (e.g. testing Kubernetes API integration) and periodic high-volume stress tests.

Issue tracker: https://github.com/linkerd/issues

Mailing lists: https://groups.google.com/forum/#!forum/linkerd-users

Website: https://linkerd.io/

Community: Active & growing!

Primarily focused on https://slack.linkerd.io (~400 members)

~1200 GitHub stars

~25 contributors

Release methodology and mechanics: Code review on all changes. Releases triggered manually by developer team. Using pre-1.0 semver semantics.

Social media accounts: Twitter: @linkerd, Slack: http://slack.linkerd.io/

Existing sponsorship: https://buoyant.io/

External Dependencies: Runtime: JVM. Build-time: Finagle, netty

Statement on alignment with CNCF mission:

Linkerd directly addresses the communications challenges of running microservices at scale, and integrates directly with orchestrated environments such as Kubernetes and DC/OS. Linkerd integrates with two existing CNCF projects: it can use the Kubernetes API directly as a service discovery mechanism, and it exposes metrics in Prometheus format. See this blog post (https://blog.buoyant.io/2016/10/04/a-service-mesh-for-kubernetes-part-i-top-line-service-metrics/) for an example of linkerd, Kubernetes and Prometheus working together.

Production Usage:

Monzo: used in production; k8s-based infra (https://monzo.com/blog/2016/09/19/building-a-modern-bank-backend/)

NCBI: used in production w/Consul

Quid: used in production

Douban: used in production

Houghton Mifflin Harcourt: used in production; DC/OS-based infra

Olark: used in production; k8s-based infra (https://www.youtube.com/watch?v=r0nhQwbe8OY&index=107&list=PLj6h78yzYM2PqgIGU1Qmi8nY7dqn9PCr4)

Other Contributors:

Currently ~25; >50% non-Buoyant by headcount: https://github.com/BuoyantIO/linkerd/graphs/contributors?type=a

--

Chris Aniszczyk (@cra) | +1-512-961-6719

_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc

--

Benjamin Hindman

Founder of Mesosphere and Co-Creator of Apache Mesos

Mesosphere Inc. 

Follow us on Twitter: @mesosphere

Learn how Verizon serves millions of users in real time with DC/OS

 

_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc

A nice touch would be to accept non-binding votes from wider community. 

Best

--

Duncan Johnston-Watt

CEO | Cloudsoft Corporation

+44 777 190 2653 | @duncanjw

Sent from my iPhone

On 14 Jan 2017, at 06:52, Brian Grant via cncf-toc <cncf-toc@...> wrote:

On Fri, Jan 13, 2017 at 7:49 AM, Chris Aniszczyk via cncf-toc <cncf-toc@...> wrote:

Hey CNCF TOC community, it's time to vote

TOC members, that is.

 

on the linkerd (https://linkerd.io/) proposal as an inception level project, you can view the proposal below in this email or on GitHub: https://github.com/cncf/toc/pull/25

Please vote +1/0/-1

+1.

 

---

Name of project: linkerd

Description: Linkerd is an open source service mesh for cloud-native applications. It is a layer 5/7 proxy that provides fully decentralized request-level reliability and optimization to service communication, including latency-aware load balancing, retries, failure handling, circuit breaking, and deadlines. It provides granular metrics (both of itself and of downstream services), distributed tracing, TLS, a powerful logical routing layer, and integration with most common service discovery mechanisms.

Applications use linkerd by proxying HTTP, gRPC, or Thrift calls through a local linkerd instance. In many cases, integration with linkerd is a config change (e.g. setting an http_proxy environment variable) rather than a code change. Linkerd acts as a transparent proxy, and so a call to (e.g. "http://foo/bar") will be routed to the appropriate cluster, resolved in service discovery, load balanced, retried, and returned without application code being aware.

Linkerd is built on top of Finagle (https://twitter.github.io/finagle/), the high-concurrency RPC library that powers companies like Twitter, Soundcloud, Pinterest, and ING Bank. By staying close to the Finagle codebase, linkerd takes advantage of Finagle’s extensive production usage (https://github.com/twitter/finagle/blob/develop/ADOPTERS.md). Linkerd’s primary author is a core contributor to Finagle.

Sponsor / Advisor from TOC: Jonathan Boulle <jonathan.boulle@...>

Unique Identifier: linkerd

License: Apache License v2.0

Maturity Level: Inception

Source control repositories: https://github.com/linkerd

Initial Committers (leads): Oliver Gould (Buoyant) [@olix0r] and Alex Leong (Buoyant) [@adleong]

Infrastructure requirements: CI and potentially CNCF Community Cluster access. We run integration tests per commit (e.g. testing Kubernetes API integration) and periodic high-volume stress tests.

Issue tracker: https://github.com/linkerd/issues

Mailing lists: https://groups.google.com/forum/#!forum/linkerd-users

Website: https://linkerd.io/

Community: Active & growing!

Primarily focused on https://slack.linkerd.io (~400 members)

~1200 GitHub stars

~25 contributors

Release methodology and mechanics: Code review on all changes. Releases triggered manually by developer team. Using pre-1.0 semver semantics.

Social media accounts: Twitter: @linkerd, Slack: http://slack.linkerd.io/

Existing sponsorship: https://buoyant.io/

External Dependencies: Runtime: JVM. Build-time: Finagle, netty

Statement on alignment with CNCF mission:

Linkerd directly addresses the communications challenges of running microservices at scale, and integrates directly with orchestrated environments such as Kubernetes and DC/OS. Linkerd integrates with two existing CNCF projects: it can use the Kubernetes API directly as a service discovery mechanism, and it exposes metrics in Prometheus format. See this blog post (https://blog.buoyant.io/2016/10/04/a-service-mesh-for-kubernetes-part-i-top-line-service-metrics/) for an example of linkerd, Kubernetes and Prometheus working together.

Production Usage:

Monzo: used in production; k8s-based infra (https://monzo.com/blog/2016/09/19/building-a-modern-bank-backend/)

NCBI: used in production w/Consul

Quid: used in production

Douban: used in production

Houghton Mifflin Harcourt: used in production; DC/OS-based infra

Olark: used in production; k8s-based infra (https://www.youtube.com/watch?v=r0nhQwbe8OY&index=107&list=PLj6h78yzYM2PqgIGU1Qmi8nY7dqn9PCr4)

Other Contributors:

Currently ~25; >50% non-Buoyant by headcount: https://github.com/BuoyantIO/linkerd/graphs/contributors?type=a

--

Chris Aniszczyk (@cra) | +1-512-961-6719

_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc

_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc

_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc

+1

On Fri, Jan 13, 2017 at 7:49 AM, Chris Aniszczyk via cncf-toc <cncf-toc@...> wrote:

Hey CNCF TOC community, it's time to vote on the linkerd (https://linkerd.io/) proposal as an inception level project, you can view the proposal below in this email or on GitHub: https://github.com/cncf/toc/pull/25

Please vote +1/0/-1

---

Name of project: linkerd

Description: Linkerd is an open source service mesh for cloud-native applications. It is a layer 5/7 proxy that provides fully decentralized request-level reliability and optimization to service communication, including latency-aware load balancing, retries, failure handling, circuit breaking, and deadlines. It provides granular metrics (both of itself and of downstream services), distributed tracing, TLS, a powerful logical routing layer, and integration with most common service discovery mechanisms.

Applications use linkerd by proxying HTTP, gRPC, or Thrift calls through a local linkerd instance. In many cases, integration with linkerd is a config change (e.g. setting an http_proxy environment variable) rather than a code change. Linkerd acts as a transparent proxy, and so a call to (e.g. "http://foo/bar") will be routed to the appropriate cluster, resolved in service discovery, load balanced, retried, and returned without application code being aware.

Linkerd is built on top of Finagle (https://twitter.github.io/finagle/), the high-concurrency RPC library that powers companies like Twitter, Soundcloud, Pinterest, and ING Bank. By staying close to the Finagle codebase, linkerd takes advantage of Finagle’s extensive production usage (https://github.com/twitter/finagle/blob/develop/ADOPTERS.md). Linkerd’s primary author is a core contributor to Finagle.

Sponsor / Advisor from TOC: Jonathan Boulle <jonathan.boulle@...>

Unique Identifier: linkerd

License: Apache License v2.0

Maturity Level: Inception

Source control repositories: https://github.com/linkerd

Initial Committers (leads): Oliver Gould (Buoyant) [@olix0r] and Alex Leong (Buoyant) [@adleong]

Infrastructure requirements: CI and potentially CNCF Community Cluster access. We run integration tests per commit (e.g. testing Kubernetes API integration) and periodic high-volume stress tests.

Issue tracker: https://github.com/linkerd/issues

Mailing lists: https://groups.google.com/forum/#!forum/linkerd-users

Website: https://linkerd.io/

Community: Active & growing!

Primarily focused on https://slack.linkerd.io (~400 members)

~1200 GitHub stars

~25 contributors

Release methodology and mechanics: Code review on all changes. Releases triggered manually by developer team. Using pre-1.0 semver semantics.

Social media accounts: Twitter: @linkerd, Slack: http://slack.linkerd.io/

Existing sponsorship: https://buoyant.io/

External Dependencies: Runtime: JVM. Build-time: Finagle, netty

Statement on alignment with CNCF mission:

Linkerd directly addresses the communications challenges of running microservices at scale, and integrates directly with orchestrated environments such as Kubernetes and DC/OS. Linkerd integrates with two existing CNCF projects: it can use the Kubernetes API directly as a service discovery mechanism, and it exposes metrics in Prometheus format. See this blog post (https://blog.buoyant.io/2016/10/04/a-service-mesh-for-kubernetes-part-i-top-line-service-metrics/) for an example of linkerd, Kubernetes and Prometheus working together.

Production Usage:

Monzo: used in production; k8s-based infra (https://monzo.com/blog/2016/09/19/building-a-modern-bank-backend/)

NCBI: used in production w/Consul

Quid: used in production

Douban: used in production

Houghton Mifflin Harcourt: used in production; DC/OS-based infra

Olark: used in production; k8s-based infra (https://www.youtube.com/watch?v=r0nhQwbe8OY&index=107&list=PLj6h78yzYM2PqgIGU1Qmi8nY7dqn9PCr4)

Other Contributors:

Currently ~25; >50% non-Buoyant by headcount: https://github.com/BuoyantIO/linkerd/graphs/contributors?type=a

--

Chris Aniszczyk (@cra) | +1-512-961-6719

_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc

--

Benjamin Hindman

Founder of Mesosphere and Co-Creator of Apache Mesos

Mesosphere Inc. 

Follow us on Twitter: @mesosphere

Learn how Verizon serves millions of users in real time with DC/OS

 

_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc

Hey CNCF TOC community, it's time to vote on the linkerd (https://linkerd.io/) proposal as an inception level project, you can view the proposal below in this email or on GitHub: https://github.com/cncf/toc/pull/25

Please vote +1/0/-1

---

Name of project: linkerd

Description: Linkerd is an open source service mesh for cloud-native applications. It is a layer 5/7 proxy that provides fully decentralized request-level reliability and optimization to service communication, including latency-aware load balancing, retries, failure handling, circuit breaking, and deadlines. It provides granular metrics (both of itself and of downstream services), distributed tracing, TLS, a powerful logical routing layer, and integration with most common service discovery mechanisms.

Applications use linkerd by proxying HTTP, gRPC, or Thrift calls through a local linkerd instance. In many cases, integration with linkerd is a config change (e.g. setting an http_proxy environment variable) rather than a code change. Linkerd acts as a transparent proxy, and so a call to (e.g. "http://foo/bar") will be routed to the appropriate cluster, resolved in service discovery, load balanced, retried, and returned without application code being aware.

Linkerd is built on top of Finagle (https://twitter.github.io/finagle/), the high-concurrency RPC library that powers companies like Twitter, Soundcloud, Pinterest, and ING Bank. By staying close to the Finagle codebase, linkerd takes advantage of Finagle’s extensive production usage (https://github.com/twitter/finagle/blob/develop/ADOPTERS.md). Linkerd’s primary author is a core contributor to Finagle.

Sponsor / Advisor from TOC: Jonathan Boulle <jonathan.boulle@...>

Unique Identifier: linkerd

License: Apache License v2.0

Maturity Level: Inception

Source control repositories: https://github.com/linkerd

Initial Committers (leads): Oliver Gould (Buoyant) [@olix0r] and Alex Leong (Buoyant) [@adleong]

Infrastructure requirements: CI and potentially CNCF Community Cluster access. We run integration tests per commit (e.g. testing Kubernetes API integration) and periodic high-volume stress tests.

Issue tracker: https://github.com/linkerd/issues

Mailing lists: https://groups.google.com/forum/#!forum/linkerd-users

Website: https://linkerd.io/

Community: Active & growing!

Primarily focused on https://slack.linkerd.io (~400 members)

~1200 GitHub stars

~25 contributors

Release methodology and mechanics: Code review on all changes. Releases triggered manually by developer team. Using pre-1.0 semver semantics.

Social media accounts: Twitter: @linkerd, Slack: http://slack.linkerd.io/

Existing sponsorship: https://buoyant.io/

External Dependencies: Runtime: JVM. Build-time: Finagle, netty

Statement on alignment with CNCF mission:

Linkerd directly addresses the communications challenges of running microservices at scale, and integrates directly with orchestrated environments such as Kubernetes and DC/OS. Linkerd integrates with two existing CNCF projects: it can use the Kubernetes API directly as a service discovery mechanism, and it exposes metrics in Prometheus format. See this blog post (https://blog.buoyant.io/2016/10/04/a-service-mesh-for-kubernetes-part-i-top-line-service-metrics/) for an example of linkerd, Kubernetes and Prometheus working together.

Production Usage:

Monzo: used in production; k8s-based infra (https://monzo.com/blog/2016/09/19/building-a-modern-bank-backend/)

NCBI: used in production w/Consul

Quid: used in production

Douban: used in production

Houghton Mifflin Harcourt: used in production; DC/OS-based infra

Olark: used in production; k8s-based infra (https://www.youtube.com/watch?v=r0nhQwbe8OY&index=107&list=PLj6h78yzYM2PqgIGU1Qmi8nY7dqn9PCr4)

Other Contributors:

Currently ~25; >50% non-Buoyant by headcount: https://github.com/BuoyantIO/linkerd/graphs/contributors?type=a

--

Chris Aniszczyk (@cra) | +1-512-961-6719

_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc

Send cncf-toc mailing list submissions to
        cncf-toc@...

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.cncf.io/mailman/listinfo/cncf-toc
or, via email, send a message with subject or body 'help' to
        cncf-toc-request@...

You can reach the person managing the list at
        cncf-toc-owner@...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of cncf-toc digest..."


Today's Topics:

   1. Re: [VOTE] linkerd project proposal (=?gb18030?B?0e7W0tGr?=)
   2. Re: [VOTE] linkerd project proposal (Jonathan Boulle)


----------------------------------------------------------------------

Message: 1
Date: Fri, 13 Jan 2017 23:56:33 +0800
From: "=?gb18030?B?0e7W0tGr?=" <alex@...>
To: "=?gb18030?B?QWxleGlzIFJpY2hhcmRzb24gdmlhIGNuY2YtdG9j?="
        <cncf-toc@...>,       "=?gb18030?B?Q2hyaXMgQW5pc3pjenlr?="
        <caniszczyk@linuxfoundation.org>
Cc: CNCF TOC <cncf-toc@...>
Subject: Re: [cncf-toc] [VOTE] linkerd project proposal
Message-ID: <tencent_2C0AF9EB7FD41AE838C381A3@qq.com>
Content-Type: text/plain; charset="gb18030"

+1
------------------ Original ------------------
From: "Alexis Richardson via cncf-toc"<cncf-toc@....io>
Date: Fri, Jan 13, 2017 11:55 PM
To: "Chris Aniszczyk"<caniszczyk@linuxfoundation.org>;
Cc: "CNCF TOC"<cncf-toc@...>;
Subject: Re: [cncf-toc] [VOTE] linkerd project proposal


+1


On Fri, Jan 13, 2017 at 3:49 PM, Chris Aniszczyk via cncf-toc
<cncf-toc@...> wrote:
> Hey CNCF TOC community, it's time to vote on the linkerd
> (https://linkerd.io/) proposal as an inception level project, you can view
> the proposal below in this email or on GitHub:
> https://github.com/cncf/toc/pull/25
>
> Please vote +1/0/-1
>
> ---
>
> Name of project: linkerd
>
> Description: Linkerd is an open source service mesh for cloud-native
> applications. It is a layer 5/7 proxy that provides fully decentralized
> request-level reliability and optimization to service communication,
> including latency-aware load balancing, retries, failure handling, circuit
> breaking, and deadlines. It provides granular metrics (both of itself and of
> downstream services), distributed tracing, TLS, a powerful logical routing
> layer, and integration with most common service discovery mechanisms.
>
> Applications use linkerd by proxying HTTP, gRPC, or Thrift calls through a
> local linkerd instance. In many cases, integration with linkerd is a config
> change (e.g. setting an http_proxy environment variable) rather than a code
> change. Linkerd acts as a transparent proxy, and so a call to (e.g.
> "http://foo/bar") will be routed to the appropriate cluster, resolved in
> service discovery, load balanced, retried, and returned without application
> code being aware.
>
> Linkerd is built on top of Finagle (https://twitter.github.io/finagle/), the
> high-concurrency RPC library that powers companies like Twitter, Soundcloud,
> Pinterest, and ING Bank. By staying close to the Finagle codebase, linkerd
> takes advantage of Finagle?s extensive production usage
> (https://github.com/twitter/finagle/blob/develop/ADOPTERS.md). Linkerd?s
> primary author is a core contributor to Finagle.
>
> Sponsor / Advisor from TOC: Jonathan Boulle <jonathan.boulle@...>
>
> Unique Identifier: linkerd
>
> License: Apache License v2.0
>
> Maturity Level: Inception
>
> Source control repositories: https://github.com/linkerd
>
> Initial Committers (leads): Oliver Gould (Buoyant) [@olix0r] and Alex Leong
> (Buoyant) [@adleong]
>
> Infrastructure requirements: CI and potentially CNCF Community Cluster
> access. We run integration tests per commit (e.g. testing Kubernetes API
> integration) and periodic high-volume stress tests.
>
> Issue tracker: https://github.com/linkerd/issues
>
> Mailing lists: https://groups.google.com/forum/#!forum/linkerd-users
>
> Website: https://linkerd.io/
>
> Community: Active & growing!
>
> Primarily focused on https://slack.linkerd.io (~400 members)
>
> ~1200 GitHub stars
>
> ~25 contributors
>
> Release methodology and mechanics: Code review on all changes. Releases
> triggered manually by developer team. Using pre-1.0 semver semantics.
>
> Social media accounts: Twitter: @linkerd, Slack: http://slack.linkerd.io/
>
> Existing sponsorship: https://buoyant.io/
>
> External Dependencies: Runtime: JVM. Build-time: Finagle, netty
>
> Statement on alignment with CNCF mission:
>
> Linkerd directly addresses the communications challenges of running
> microservices at scale, and integrates directly with orchestrated
> environments such as Kubernetes and DC/OS. Linkerd integrates with two
> existing CNCF projects: it can use the Kubernetes API directly as a service
> discovery mechanism, and it exposes metrics in Prometheus format. See this
> blog post
> (https://blog.buoyant.io/2016/10/04/a-service-mesh-for-kubernetes-part-i-top-line-service-metrics/)
> for an example of linkerd, Kubernetes and Prometheus working together.
>
> Production Usage:
>
> Monzo: used in production; k8s-based infra
> (https://monzo.com/blog/2016/09/19/building-a-modern-bank-backend/)
>
> NCBI: used in production w/Consul
>
> Quid: used in production
>
> Douban: used in production
>
> Houghton Mifflin Harcourt: used in production; DC/OS-based infra
>
> Olark: used in production; k8s-based infra
> (https://www.youtube.com/watch?v=r0nhQwbe8OY&index=107&list=PLj6h78yzYM2PqgIGU1Qmi8nY7dqn9PCr4)
>
> Other Contributors:
>
> Currently ~25; >50% non-Buoyant by headcount:
> https://github.com/BuoyantIO/linkerd/graphs/contributors?type=a
>
> --
> Chris Aniszczyk (@cra) | +1-512-961-6719
>
> _______________________________________________
> cncf-toc mailing list
> cncf-toc@...
> https://lists.cncf.io/mailman/listinfo/cncf-toc
>
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cncf.io/pipermail/cncf-toc/attachments/20170113/38c08631/attachment-0001.html>

------------------------------

Message: 2
Date: Fri, 13 Jan 2017 16:45:18 +0000
From: Jonathan Boulle <jonathan.boulle@...>
To: ??? <alex@...>,     Alexis Richardson via cncf-toc
        <cncf-toc@...>,       Chris Aniszczyk
        <caniszczyk@linuxfoundation.org>
Subject: Re: [cncf-toc] [VOTE] linkerd project proposal
Message-ID:
        <CAPWU_0pXAjwpnbeGVEC7EOUvBsXxK3AF+fkBopsCeVopoMr1Qg@....com>
Content-Type: text/plain; charset="utf-8"

+1

On Fri, Jan 13, 2017 at 5:03 PM ??? via cncf-toc <cncf-toc@...>
wrote:

> +1
> ------------------ Original ------------------
> *From:* "Alexis Richardson via cncf-toc"<cncf-toc@....io>
> *Date:* Fri, Jan 13, 2017 11:55 PM
> *To:* "Chris Aniszczyk"<caniszczyk@linuxfoundation.org>;
> *Cc:* "CNCF TOC"<cncf-toc@...>;
> *Subject:* Re: [cncf-toc] [VOTE] linkerd project proposal
> +1
>
>
> On Fri, Jan 13, 2017 at 3:49 PM, Chris Aniszczyk via cncf-toc
> <cncf-toc@...> wrote:
> > Hey CNCF TOC community, it's time to vote on the linkerd
> > (https://linkerd.io/) proposal as an inception level project, you can
> view
> > the proposal below in this email or on GitHub:
> > https://github.com/cncf/toc/pull/25
> >
> > Please vote +1/0/-1
> >
> > ---
> >
> > Name of project: linkerd
> >
> > Description: Linkerd is an open source service mesh for cloud-native
> > applications. It is a layer 5/7 proxy that provides fully decentralized
> > request-level reliability and optimization to service communication,
> > including latency-aware load balancing, retries, failure handling,
> circuit
> > breaking, and deadlines. It provides granular metrics (both of itself
> and of
> > downstream services), distributed tracing, TLS, a powerful logical
> routing
> > layer, and integration with most common service discovery mechanisms.
> >
> > Applications use linkerd by proxying HTTP, gRPC, or Thrift calls through
> a
> > local linkerd instance. In many cases, integration with linkerd is a
> config
> > change (e.g. setting an http_proxy environment variable) rather than a
> code
> > change. Linkerd acts as a transparent proxy, and so a call to (e.g.
> > "http://foo/bar") will be routed to the appropriate cluster, resolved in
> > service discovery, load balanced, retried, and returned without
> application
> > code being aware.
> >
> > Linkerd is built on top of Finagle (https://twitter.github.io/finagle/),
> the
> > high-concurrency RPC library that powers companies like Twitter,
> Soundcloud,
> > Pinterest, and ING Bank. By staying close to the Finagle codebase,
> linkerd
> > takes advantage of Finagle?s extensive production usage
> > (https://github.com/twitter/finagle/blob/develop/ADOPTERS.md). Linkerd?s
> > primary author is a core contributor to Finagle.
> >
> > Sponsor / Advisor from TOC: Jonathan Boulle <jonathan.boulle@...>
> >
> > Unique Identifier: linkerd
> >
> > License: Apache License v2.0
> >
> > Maturity Level: Inception
> >
> > Source control repositories: https://github.com/linkerd
> >
> > Initial Committers (leads): Oliver Gould (Buoyant) [@olix0r] and Alex
> Leong
> > (Buoyant) [@adleong]
> >
> > Infrastructure requirements: CI and potentially CNCF Community Cluster
> > access. We run integration tests per commit (e.g. testing Kubernetes API
> > integration) and periodic high-volume stress tests.
> >
> > Issue tracker: https://github.com/linkerd/issues
> >
> > Mailing lists: https://groups.google.com/forum/#!forum/linkerd-users
> >
> > Website: https://linkerd.io/
> >
> > Community: Active & growing!
> >
> > Primarily focused on https://slack.linkerd.io (~400 members)
> >
> > ~1200 GitHub stars
> >
> > ~25 contributors
> >
> > Release methodology and mechanics: Code review on all changes. Releases
> > triggered manually by developer team. Using pre-1.0 semver semantics.
> >
> > Social media accounts: Twitter: @linkerd, Slack:
> http://slack.linkerd.io/
> >
> > Existing sponsorship: https://buoyant.io/
> >
> > External Dependencies: Runtime: JVM. Build-time: Finagle, netty
> >
> > Statement on alignment with CNCF mission:
> >
> > Linkerd directly addresses the communications challenges of running
> > microservices at scale, and integrates directly with orchestrated
> > environments such as Kubernetes and DC/OS. Linkerd integrates with two
> > existing CNCF projects: it can use the Kubernetes API directly as a
> service
> > discovery mechanism, and it exposes metrics in Prometheus format. See
> this
> > blog post
> > (
> https://blog.buoyant.io/2016/10/04/a-service-mesh-for-kubernetes-part-i-top-line-service-metrics/
> )
> > for an example of linkerd, Kubernetes and Prometheus working together.
> >
> > Production Usage:
> >
> > Monzo: used in production; k8s-based infra
> > (https://monzo.com/blog/2016/09/19/building-a-modern-bank-backend/)
> >
> > NCBI: used in production w/Consul
> >
> > Quid: used in production
> >
> > Douban: used in production
> >
> > Houghton Mifflin Harcourt: used in production; DC/OS-based infra
> >
> > Olark: used in production; k8s-based infra
> > (
> https://www.youtube.com/watch?v=r0nhQwbe8OY&index=107&list=PLj6h78yzYM2PqgIGU1Qmi8nY7dqn9PCr4
> )
> >
> > Other Contributors:
> >
> > Currently ~25; >50% non-Buoyant by headcount:
> > https://github.com/BuoyantIO/linkerd/graphs/contributors?type=a
> >
> > --
> > Chris Aniszczyk (@cra) | +1-512-961-6719 <(512)%20961-6719>
> >
> > _______________________________________________
> > cncf-toc mailing list
> > cncf-toc@...
> > https://lists.cncf.io/mailman/listinfo/cncf-toc
> >
> _______________________________________________
> cncf-toc mailing list
> cncf-toc@...
> https://lists.cncf.io/mailman/listinfo/cncf-toc
> _______________________________________________
> cncf-toc mailing list
> cncf-toc@...
> https://lists.cncf.io/mailman/listinfo/cncf-toc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cncf.io/pipermail/cncf-toc/attachments/20170113/89bca9a7/attachment.html>

------------------------------

_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc


End of cncf-toc Digest, Vol 14, Issue 10
****************************************

+1 

------------------ Original ------------------

From: "Alexis Richardson via cncf-toc"<cncf-toc@...>

Date: Fri, Jan 13, 2017 11:55 PM

To: "Chris Aniszczyk"<caniszczyk@...>;

Cc: "CNCF TOC"<cncf-toc@...>;

Subject: Re: [cncf-toc] [VOTE] linkerd project proposal

+1


On Fri, Jan 13, 2017 at 3:49 PM, Chris Aniszczyk via cncf-toc
<cncf-toc@...> wrote:
> Hey CNCF TOC community, it's time to vote on the linkerd
> (https://linkerd.io/) proposal as an inception level project, you can view
> the proposal below in this email or on GitHub:
> https://github.com/cncf/toc/pull/25
>
> Please vote +1/0/-1
>
> ---
>
> Name of project: linkerd
>
> Description: Linkerd is an open source service mesh for cloud-native
> applications. It is a layer 5/7 proxy that provides fully decentralized
> request-level reliability and optimization to service communication,
> including latency-aware load balancing, retries, failure handling, circuit
> breaking, and deadlines. It provides granular metrics (both of itself and of
> downstream services), distributed tracing, TLS, a powerful logical routing
> layer, and integration with most common service discovery mechanisms.
>
> Applications use linkerd by proxying HTTP, gRPC, or Thrift calls through a
> local linkerd instance. In many cases, integration with linkerd is a config
> change (e.g. setting an http_proxy environment variable) rather than a code
> change. Linkerd acts as a transparent proxy, and so a call to (e.g.
> "http://foo/bar") will be routed to the appropriate cluster, resolved in
> service discovery, load balanced, retried, and returned without application
> code being aware.
>
> Linkerd is built on top of Finagle (https://twitter.github.io/finagle/), the
> high-concurrency RPC library that powers companies like Twitter, Soundcloud,
> Pinterest, and ING Bank. By staying close to the Finagle codebase, linkerd
> takes advantage of Finagle’s extensive production usage
> (https://github.com/twitter/finagle/blob/develop/ADOPTERS.md). Linkerd’s
> primary author is a core contributor to Finagle.
>
> Sponsor / Advisor from TOC: Jonathan Boulle <jonathan.boulle@...>
>
> Unique Identifier: linkerd
>
> License: Apache License v2.0
>
> Maturity Level: Inception
>
> Source control repositories: https://github.com/linkerd
>
> Initial Committers (leads): Oliver Gould (Buoyant) [@olix0r] and Alex Leong
> (Buoyant) [@adleong]
>
> Infrastructure requirements: CI and potentially CNCF Community Cluster
> access. We run integration tests per commit (e.g. testing Kubernetes API
> integration) and periodic high-volume stress tests.
>
> Issue tracker: https://github.com/linkerd/issues
>
> Mailing lists: https://groups.google.com/forum/#!forum/linkerd-users
>
> Website: https://linkerd.io/
>
> Community: Active & growing!
>
> Primarily focused on https://slack.linkerd.io (~400 members)
>
> ~1200 GitHub stars
>
> ~25 contributors
>
> Release methodology and mechanics: Code review on all changes. Releases
> triggered manually by developer team. Using pre-1.0 semver semantics.
>
> Social media accounts: Twitter: @linkerd, Slack: http://slack.linkerd.io/
>
> Existing sponsorship: https://buoyant.io/
>
> External Dependencies: Runtime: JVM. Build-time: Finagle, netty
>
> Statement on alignment with CNCF mission:
>
> Linkerd directly addresses the communications challenges of running
> microservices at scale, and integrates directly with orchestrated
> environments such as Kubernetes and DC/OS. Linkerd integrates with two
> existing CNCF projects: it can use the Kubernetes API directly as a service
> discovery mechanism, and it exposes metrics in Prometheus format. See this
> blog post
> (https://blog.buoyant.io/2016/10/04/a-service-mesh-for-kubernetes-part-i-top-line-service-metrics/)
> for an example of linkerd, Kubernetes and Prometheus working together.
>
> Production Usage:
>
> Monzo: used in production; k8s-based infra
> (https://monzo.com/blog/2016/09/19/building-a-modern-bank-backend/)
>
> NCBI: used in production w/Consul
>
> Quid: used in production
>
> Douban: used in production
>
> Houghton Mifflin Harcourt: used in production; DC/OS-based infra
>
> Olark: used in production; k8s-based infra
> (https://www.youtube.com/watch?v=r0nhQwbe8OY&index=107&list=PLj6h78yzYM2PqgIGU1Qmi8nY7dqn9PCr4)
>
> Other Contributors:
>
> Currently ~25; >50% non-Buoyant by headcount:
> https://github.com/BuoyantIO/linkerd/graphs/contributors?type=a
>
> --
> Chris Aniszczyk (@cra) | +1-512-961-6719
>
> _______________________________________________
> cncf-toc mailing list
> cncf-toc@...
> https://lists.cncf.io/mailman/listinfo/cncf-toc
>
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc