|
Re: [VOTE] linkerd project proposal
Duncan Johnston-Watt <duncan.johnstonwatt@...>
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:
|
|
|
Re: [VOTE] linkerd project proposal
|
|
|
Re: [VOTE] linkerd project proposal
toggle quoted messageShow quoted text
On Fri, Jan 13, 2017 at 7:49 AM, Chris Aniszczyk via cncf-toc <cncf-toc@...> wrote:
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/linkerdInitial 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/issuesMailing lists: https://groups.google.com/forum/#!forum/linkerd-usersWebsite: 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
--
_______________________________________________
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
|
|
|
Re: [VOTE] linkerd project proposal
|
|
|
Re: [VOTE] linkerd project proposal
Matt Baldwin <baldwin@...>
toggle quoted messageShow quoted text
On Fri, Jan 13, 2017 at 8:45 AM, <cncf-toc-request@...> wrote: 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
****************************************
|
|
|
Re: [VOTE] linkerd project proposal
Jonathan Boulle <jonathan.boulle@...>
toggle quoted messageShow quoted text
On Fri, Jan 13, 2017 at 5:03 PM 杨忠勋 via cncf-toc < cncf-toc@...> wrote: +1 ------------------ Original ------------------ Date: Fri, Jan 13, 2017 11:55 PM Subject: Re: [cncf-toc] [VOTE] linkerd project proposal
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
|
|
|
Re: [VOTE] linkerd project proposal
Kenneth Owens (kenowens) <kenowens@...>
+1
|
|
|
|
|
|
|
Kenneth Owens
CTO
kenowens@...
Tel:
+1 408 424 0872
|
Cisco Systems, Inc.
16401 Swingley Ridge Road Suite 400
CHESTERFIELD
63017
United States
cisco.com
|
|
|
 Think
before you print.
|
|
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use,
distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
Please
click here
for Company Registration Information.
|
toggle quoted messageShow quoted text
From: cncf-toc-bounces@... [mailto:cncf-toc-bounces@...]
On Behalf Of Chris Aniszczyk via cncf-toc
Sent: Friday, January 13, 2017 9:49 AM
To: CNCF TOC <cncf-toc@...>
Subject: [cncf-toc] [VOTE] linkerd project proposal
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
|
|
|
Re: [VOTE] linkerd project proposal
+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
|
|
|
Re: [VOTE] linkerd project proposal
+1 On Fri, Jan 13, 2017 at 3:49 PM, Chris Aniszczyk via cncf-toc <cncf-toc@lists.cncf.io> 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@coreos.com>
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@lists.cncf.io
https://lists.cncf.io/mailman/listinfo/cncf-toc
|
|
|
[VOTE] linkerd project proposal
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/linkerdInitial 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/issuesMailing lists: https://groups.google.com/forum/#!forum/linkerd-usersWebsite: 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
|
|
|
Re: RFC: Fission (http://fission.io/)
I think we should consider a working group or SIG for “serverless”
some of those solutions look naïve at best
there is a lot of overlap between k8s functionality and “serverless” on one hand, on the other it requires integration with multiple external frameworks e.g. APIs, PubSub,
Logging, K/V state storage, event triggers/streamers, identity management. Each of those may have few overlapping cloud, open-source and commercial options with pros and cons. I don’t see how one company can deliver on it all (unless its AWS/GCP/Azure), it
calls for collaboration.
the right path is to start with requirements and a framework/architecture which define the flows, layers, APIs and roles of components, what needs to be done at the orchestration
layer (k8s/mesos/..), how external triggers or resources are plugged into it, how does it scale, development tools ...
I’m willing to take active part in such a workforce
Yaron
toggle quoted messageShow quoted text
From: cncf-toc-bounces@... [mailto:cncf-toc-bounces@...]
On Behalf Of Alexis Richardson via cncf-toc
Sent: Friday, January 6, 2017 8:57 PM
To: Jonathan Boulle <jonathan.boulle@...>; Soam Vasani <soamvasani@...>
Cc: Soam Vasani <soam@...>; CNCF TOC <cncf-toc@...>
Subject: Re: [cncf-toc] RFC: Fission (http://fission.io/)
+1 especially compared to the cornucopia of new "serverless" libs that seem to have appeared of late....
On Fri, 6 Jan 2017, 18:53 Jonathan Boulle via cncf-toc, <cncf-toc@...> wrote:
I would be interested in hearing/seeing more about practical uses of fission so far. I'd also like to see the
documentation fleshed out a bit - it's a little sparse in terms of understanding how this all fits together and how users can integrate.
On 4 January 2017 at 18:01, Soam Vasani via cncf-toc
<cncf-toc@...> wrote:
Thanks very much for your time, everyone!
I'd love to answer any questions here, or do a follow-up demo in a hangout, if anyone is interested in that.
-Soam
On Wed, Jan 4, 2017 at 8:53 AM, Chris Aniszczyk
<caniszczyk@...> wrote:
At the TOC call today, we have a presentation from the Fission (http://fission.io/) team:
As part of the project proposal process, we aim to have a discussion about the project on the mailing list / TOC call before a decision is made to formally invite a project. I invite the TOC and the wider CNCF
community to comment on the mailing list.
Thanks Soam for taking the time to present!
--
_______________________________________________
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
|
|
|
Re: RFC: Fission (http://fission.io/)
+1 especially compared to the cornucopia of new "serverless" libs that seem to have appeared of late....
On Fri, 6 Jan 2017, 18:53 Jonathan Boulle via cncf-toc, < cncf-toc@...> wrote: I would be interested in hearing/seeing more about practical uses of fission so far. I'd also like to see the documentation fleshed out a bit - it's a little sparse in terms of understanding how this all fits together and how users can integrate.
thanks, Jonathan
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
|
|
|
Re: RFC: Fission (http://fission.io/)
Jonathan Boulle <jonathan.boulle@...>
I would be interested in hearing/seeing more about practical uses of fission so far. I'd also like to see the documentation fleshed out a bit - it's a little sparse in terms of understanding how this all fits together and how users can integrate.
thanks, Jonathan
On 4 January 2017 at 18:01, Soam Vasani via cncf-toc <cncf-toc@...> wrote: Thanks very much for your time, everyone!
I'd love to answer any questions here, or do a follow-up demo in a hangout, if anyone is interested in that.
-Soam
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
|
|
|
Re: CNCF cluster - maintenance window
toggle quoted messageShow quoted text
On Fri, Jan 6, 2017 at 1:11 PM, Bernstein, Joshua <Joshua.Bernstein@...> wrote:
Is there a way we can sign up or apply for time on the cluster?
-Josh
On Jan 5, 2017, at 12:35 PM, Maciej Naruszewicz via cncf-toc < cncf-toc@...> wrote:
Dan and others,
So as to avoid misunderstanding - this is the 1st step to increase the cluster's capacity and there will be some steps left to do. In other words, the cluster won't reach ~900 nodes right after this maintenance window, it will take a bit of time but still
should be finished within Q1'17.
On 01/05/2017 09:00 PM, Dan Kohn wrote:
+Public TOC list
Thanks for the heads up. We're excited to get to the full ~900 server capacity.
-- Executive Director, Cloud Native Computing Foundation < https://cncf.io/> tel:+1-415-233-1000
|
|
|
Re: CNCF cluster - maintenance window
Bernstein, Joshua <Joshua.Bernstein@...>
Is there a way we can sign up or apply for time on the cluster?
-Josh
toggle quoted messageShow quoted text
On Jan 5, 2017, at 12:35 PM, Maciej Naruszewicz via cncf-toc < cncf-toc@...> wrote:
Dan and others,
So as to avoid misunderstanding - this is the 1st step to increase the cluster's capacity and there will be some steps left to do. In other words, the cluster won't reach ~900 nodes right after this maintenance window, it will take a bit of time but still
should be finished within Q1'17.
On 01/05/2017 09:00 PM, Dan Kohn wrote:
+Public TOC list
Thanks for the heads up. We're excited to get to the full ~900 server capacity.
|
|
|
Re: CNCF cluster - maintenance window
Maciej Naruszewicz <maciej.naruszewicz@...>
Dan and others,
So as to avoid misunderstanding - this is the 1st step to
increase the cluster's capacity and there will be some steps left
to do. In other words, the cluster won't reach ~900 nodes right
after this maintenance window, it will take a bit of time but
still should be finished within Q1'17.
toggle quoted messageShow quoted text
On 01/05/2017 09:00 PM, Dan Kohn wrote:
+Public TOC list
Thanks for the heads up. We're excited to get to the full
~900 server capacity.
|
|
|
Re: CNCF cluster - maintenance window
Great, maybe this could write out to slack too?
On Thu, 5 Jan 2017, 20:27 Dan Kohn, < dan@...> wrote:
|
|
|
Re: CNCF cluster - maintenance window
toggle quoted messageShow quoted text
On Thu, Jan 5, 2017 at 3:22 PM, Alexis Richardson <alexis@...> wrote: Great to see
Would love to get regular readouts on who is using the cluster and for what.
-- Executive Director, Cloud Native Computing Foundation < https://cncf.io/> tel:+1-415-233-1000
|
|
|
Re: CNCF cluster - maintenance window
Great to see
Would love to get regular readouts on who is using the cluster and for what.
|
|
|
Re: CNCF cluster - maintenance window
+Public TOC list
Thanks for the heads up. We're excited to get to the full ~900 server capacity.
On Thu, Jan 5, 2017 at 2:57 PM, Maciej Naruszewicz <maciej.naruszewicz@...> wrote: Hi Dan,
Per our discussion on Slack I wanted to confirm that due to the expansion process we will be having a maintenance window in the CNCF cluster soon. We do not have an exact date nor the amount of time it will take but basing on what I know it should take place somewhere around last week of January - first week of February and last up to a few days. I will confirm the dates with you when we are certain about the schedule. I will also post an issue describing it on the cluster's Github page so that tenants are aware of it.
Feel free to contact me in case of any questions.
Maciej
-- Executive Director, Cloud Native Computing Foundation < https://cncf.io/> tel:+1-415-233-1000
|
|
|
Learn how Verizon serves millions