Date   

Re: New version of Cloud Native Landscape

alexis richardson
 

Dan

Please could you revert to the last known good version?

Alexis


On Tue, 12 Sep 2017, 05:34 Dan Kohn <dan@...> wrote:
I made the change at the last minute to deal with a spacing issue. I will revert it in the next version and restore CI/CD to the top layer. Apologies.

--
Dan Kohn <mailto:dan@...>
Executive Director, Cloud Native Computing Foundation <https://cncf.io/>
tel:+1-415-233-1000

On Mon, Sep 11, 2017 at 10:35 PM, Alexis Richardson <alexis@...> wrote:
The TOC will have to fix this, by going back to the 0.92 structure, which was correct.  And rebuilding from there.

On Tue, 12 Sep 2017, 03:06 Alexis Richardson <alexis@...> wrote:

That's very disappointing


On Tue, 12 Sep 2017, 03:05 Camille Fournier <skamille@...> wrote:
It looks like it changed pretty significantly between 0.9.5 and 0.9.6. 

On Mon, Sep 11, 2017 at 10:04 PM, Alexis Richardson <alexis@...> wrote:
Woah.  How did CICD get moved?  Wtf

Landscape 0.92 is authoritative. I'm afraid this new thing is not.

Dan, Chris, any ideas?





On Tue, 12 Sep 2017, 02:13 Camille Fournier via cncf-toc <cncf-toc@...> wrote:
Can someone point me to the doc or remind me why we decided to put "CI/CD" into the "provisioning" layer? It's a bit of an odd duck there so we must've had a good reason for it.

Thanks,
C

On Thu, Aug 17, 2017 at 11:03 PM, Dan Kohn via cncf-toc <cncf-toc@...> wrote:
You may be interested in the new version of the CNCF Cloud Native Landscape. As always, if you see something wrong, please open at issue at https://github.com/cncf/landscape:



--
Dan Kohn <mailto:dan@...>
Executive Director, Cloud Native Computing Foundation <https://cncf.io/>
tel:+1-415-233-1000

_______________________________________________
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: New version of Cloud Native Landscape

Dan Kohn <dan@...>
 

I made the change at the last minute to deal with a spacing issue. I will revert it in the next version and restore CI/CD to the top layer. Apologies.

--
Dan Kohn <mailto:dan@...>
Executive Director, Cloud Native Computing Foundation <https://cncf.io/>
tel:+1-415-233-1000

On Mon, Sep 11, 2017 at 10:35 PM, Alexis Richardson <alexis@...> wrote:
The TOC will have to fix this, by going back to the 0.92 structure, which was correct.  And rebuilding from there.

On Tue, 12 Sep 2017, 03:06 Alexis Richardson <alexis@...> wrote:

That's very disappointing


On Tue, 12 Sep 2017, 03:05 Camille Fournier <skamille@...> wrote:
It looks like it changed pretty significantly between 0.9.5 and 0.9.6. 

On Mon, Sep 11, 2017 at 10:04 PM, Alexis Richardson <alexis@...> wrote:
Woah.  How did CICD get moved?  Wtf

Landscape 0.92 is authoritative. I'm afraid this new thing is not.

Dan, Chris, any ideas?





On Tue, 12 Sep 2017, 02:13 Camille Fournier via cncf-toc <cncf-toc@...> wrote:
Can someone point me to the doc or remind me why we decided to put "CI/CD" into the "provisioning" layer? It's a bit of an odd duck there so we must've had a good reason for it.

Thanks,
C

On Thu, Aug 17, 2017 at 11:03 PM, Dan Kohn via cncf-toc <cncf-toc@...> wrote:
You may be interested in the new version of the CNCF Cloud Native Landscape. As always, if you see something wrong, please open at issue at https://github.com/cncf/landscape:



--
Dan Kohn <mailto:dan@linuxfoundation.org>
Executive Director, Cloud Native Computing Foundation <https://cncf.io/>
tel:+1-415-233-1000

_______________________________________________
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: New version of Cloud Native Landscape

alexis richardson
 

The TOC will have to fix this, by going back to the 0.92 structure, which was correct.  And rebuilding from there.

On Tue, 12 Sep 2017, 03:06 Alexis Richardson <alexis@...> wrote:

That's very disappointing


On Tue, 12 Sep 2017, 03:05 Camille Fournier <skamille@...> wrote:
It looks like it changed pretty significantly between 0.9.5 and 0.9.6. 

On Mon, Sep 11, 2017 at 10:04 PM, Alexis Richardson <alexis@...> wrote:
Woah.  How did CICD get moved?  Wtf

Landscape 0.92 is authoritative. I'm afraid this new thing is not.

Dan, Chris, any ideas?





On Tue, 12 Sep 2017, 02:13 Camille Fournier via cncf-toc <cncf-toc@...> wrote:
Can someone point me to the doc or remind me why we decided to put "CI/CD" into the "provisioning" layer? It's a bit of an odd duck there so we must've had a good reason for it.

Thanks,
C

On Thu, Aug 17, 2017 at 11:03 PM, Dan Kohn via cncf-toc <cncf-toc@...> wrote:
You may be interested in the new version of the CNCF Cloud Native Landscape. As always, if you see something wrong, please open at issue at https://github.com/cncf/landscape:



--
Dan Kohn <mailto:dan@...>
Executive Director, Cloud Native Computing Foundation <https://cncf.io/>
tel:+1-415-233-1000

_______________________________________________
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: New version of Cloud Native Landscape

alexis richardson
 

That's very disappointing


On Tue, 12 Sep 2017, 03:05 Camille Fournier <skamille@...> wrote:
It looks like it changed pretty significantly between 0.9.5 and 0.9.6. 

On Mon, Sep 11, 2017 at 10:04 PM, Alexis Richardson <alexis@...> wrote:
Woah.  How did CICD get moved?  Wtf

Landscape 0.92 is authoritative. I'm afraid this new thing is not.

Dan, Chris, any ideas?





On Tue, 12 Sep 2017, 02:13 Camille Fournier via cncf-toc <cncf-toc@...> wrote:
Can someone point me to the doc or remind me why we decided to put "CI/CD" into the "provisioning" layer? It's a bit of an odd duck there so we must've had a good reason for it.

Thanks,
C

On Thu, Aug 17, 2017 at 11:03 PM, Dan Kohn via cncf-toc <cncf-toc@...> wrote:
You may be interested in the new version of the CNCF Cloud Native Landscape. As always, if you see something wrong, please open at issue at https://github.com/cncf/landscape:



--
Dan Kohn <mailto:dan@...>
Executive Director, Cloud Native Computing Foundation <https://cncf.io/>
tel:+1-415-233-1000

_______________________________________________
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: New version of Cloud Native Landscape

Camille Fournier
 

It looks like it changed pretty significantly between 0.9.5 and 0.9.6. 

On Mon, Sep 11, 2017 at 10:04 PM, Alexis Richardson <alexis@...> wrote:
Woah.  How did CICD get moved?  Wtf

Landscape 0.92 is authoritative. I'm afraid this new thing is not.

Dan, Chris, any ideas?





On Tue, 12 Sep 2017, 02:13 Camille Fournier via cncf-toc <cncf-toc@...> wrote:
Can someone point me to the doc or remind me why we decided to put "CI/CD" into the "provisioning" layer? It's a bit of an odd duck there so we must've had a good reason for it.

Thanks,
C

On Thu, Aug 17, 2017 at 11:03 PM, Dan Kohn via cncf-toc <cncf-toc@...> wrote:
You may be interested in the new version of the CNCF Cloud Native Landscape. As always, if you see something wrong, please open at issue at https://github.com/cncf/landscape:



--
Dan Kohn <mailto:dan@linuxfoundation.org>
Executive Director, Cloud Native Computing Foundation <https://cncf.io/>
tel:+1-415-233-1000

_______________________________________________
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: New version of Cloud Native Landscape

alexis richardson
 

Woah.  How did CICD get moved?  Wtf

Landscape 0.92 is authoritative. I'm afraid this new thing is not.

Dan, Chris, any ideas?





On Tue, 12 Sep 2017, 02:13 Camille Fournier via cncf-toc <cncf-toc@...> wrote:
Can someone point me to the doc or remind me why we decided to put "CI/CD" into the "provisioning" layer? It's a bit of an odd duck there so we must've had a good reason for it.

Thanks,
C

On Thu, Aug 17, 2017 at 11:03 PM, Dan Kohn via cncf-toc <cncf-toc@...> wrote:
You may be interested in the new version of the CNCF Cloud Native Landscape. As always, if you see something wrong, please open at issue at https://github.com/cncf/landscape:



--
Dan Kohn <mailto:dan@...>
Executive Director, Cloud Native Computing Foundation <https://cncf.io/>
tel:+1-415-233-1000

_______________________________________________
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: New version of Cloud Native Landscape

Pini Reznik
 

Would be good to add a section for service providers.
Especially now, when we have the first batch of  certified kubernetes service provides 

Pini

On Mon, 11 Sep 2017 at 18:13, Camille Fournier via cncf-toc <cncf-toc@...> wrote:
Can someone point me to the doc or remind me why we decided to put "CI/CD" into the "provisioning" layer? It's a bit of an odd duck there so we must've had a good reason for it.

Thanks,
C

On Thu, Aug 17, 2017 at 11:03 PM, Dan Kohn via cncf-toc <cncf-toc@...> wrote:
You may be interested in the new version of the CNCF Cloud Native Landscape. As always, if you see something wrong, please open at issue at https://github.com/cncf/landscape:



--
Dan Kohn <mailto:dan@...>
Executive Director, Cloud Native Computing Foundation <https://cncf.io/>
tel:+1-415-233-1000

_______________________________________________
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
--
Pini Reznik
CTO

T. +31 (0) 6 317 99 811


Re: New version of Cloud Native Landscape

Camille Fournier
 

Can someone point me to the doc or remind me why we decided to put "CI/CD" into the "provisioning" layer? It's a bit of an odd duck there so we must've had a good reason for it.

Thanks,
C

On Thu, Aug 17, 2017 at 11:03 PM, Dan Kohn via cncf-toc <cncf-toc@...> wrote:
You may be interested in the new version of the CNCF Cloud Native Landscape. As always, if you see something wrong, please open at issue at https://github.com/cncf/landscape:



--
Dan Kohn <mailto:dan@linuxfoundation.org>
Executive Director, Cloud Native Computing Foundation <https://cncf.io/>
tel:+1-415-233-1000

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



Re: [VOTE] Envoy project proposal (incubation)

Dustin Kirkland <kirkland@...>
 

+1, non-binding.

Dustin Kirkland
VP of Product
Canonical, Ltd.
@dustinkirkland


On Fri, Sep 1, 2017 at 3:53 PM, Chris Aniszczyk via cncf-toc
<cncf-toc@...> wrote:
The TOC has decided to invite Envoy (https://github.com/lyft/envoy) as an
incubation level CNCF project, sponsored by Alexis Richardson from the TOC:

Envoy is a high performance C++ distributed proxy, communication bus and
universal data plane designed for large microservice service mesh
architectures. Envoy runs alongside every application and abstracts the
network by providing common features in a platform-agnostic manner. When all
service traffic in an infrastructure flows via an Envoy mesh, it becomes
easy to visualize problem areas via consistent observability, tune overall
performance, and add substrate features in a single place.

Please vote (+1/0/-1) on the full project proposal located here on GitHub:
https://github.com/cncf/toc/pull/43

Remember that the TOC has binding votes only, but we do appreciate
non-binding votes from the community as a sign of support!

Thanks!

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

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


Re: [VOTE] Jaeger project proposal (incubation)

Benjamin Hindman
 

+1

On Fri, Sep 8, 2017 at 12:32 PM, Camille Fournier via cncf-toc <cncf-toc@...> wrote:
+1

On Thu, Sep 7, 2017 at 5:02 PM, Chris Aniszczyk via cncf-toc <cncf-toc@...> wrote:
The TOC has decided to invite Jaeger (https://github.com/uber/jaeger) as an incubation level CNCF project, sponsored by Bryan Cantrill from the TOC:

Jaeger, inspired by Google Dapper (https://research.google.com/pubs/pub36356.html) and OpenZipkin (http://zipkin.io/), is a distributed tracing system that can be used for monitoring microservice-based architectures, including distributed context propagation, distributed transaction monitoring, root cause analysis, service dependency analysis and performance / latency optimization (also integrates with OpenTracing).

Please vote (+1/0/-1) on the full project proposal located here on GitHub: https://github.com/cncf/toc/pull/42

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

Thanks!

--
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




--
Benjamin Hindman
Founder of Mesosphere and Co-Creator of Apache Mesos

Follow us on Twitter: @mesosphere

 


Re: [VOTE] Jaeger project proposal (incubation)

Camille Fournier
 

+1

On Thu, Sep 7, 2017 at 5:02 PM, Chris Aniszczyk via cncf-toc <cncf-toc@...> wrote:
The TOC has decided to invite Jaeger (https://github.com/uber/jaeger) as an incubation level CNCF project, sponsored by Bryan Cantrill from the TOC:

Jaeger, inspired by Google Dapper (https://research.google.com/pubs/pub36356.html) and OpenZipkin (http://zipkin.io/), is a distributed tracing system that can be used for monitoring microservice-based architectures, including distributed context propagation, distributed transaction monitoring, root cause analysis, service dependency analysis and performance / latency optimization (also integrates with OpenTracing).

Please vote (+1/0/-1) on the full project proposal located here on GitHub: https://github.com/cncf/toc/pull/42

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

Thanks!

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

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



Re: [VOTE] Jaeger project proposal (incubation)

Naadir Jeewa <naadir@...>
 

+1 (non-binding)


--
Naadir Jeewa
Platform Lead
The Scale Factory,


Re: [VOTE] Jaeger project proposal (incubation)

Kitson, Clinton <Clinton.Kitson@...>
 

+1


Clint Kitson
Technical Director
{code} by Dell EMC
CNCF Governing Board Member
--- 
email: Clinton.Kitson@...
mobile: "+1 424 645 4116"
team: codeDellEMC.com
twitter: "@clintkitson"
github: github.com/clintkitson


From: cncf-toc-bounces@... [cncf-toc-bounces@...] on behalf of Arun Gupta via cncf-toc [cncf-toc@...]
Sent: Friday, September 8, 2017 7:25 AM
To: Chris Aniszczyk
Cc: CNCF TOC
Subject: Re: [cncf-toc] [VOTE] Jaeger project proposal (incubation)

+1 (non-binding)

On Thu, Sep 7, 2017 at 2:02 PM, Chris Aniszczyk via cncf-toc <cncf-toc@...> wrote:
The TOC has decided to invite Jaeger (https://github.com/uber/jaeger) as an incubation level CNCF project, sponsored by Bryan Cantrill from the TOC:

Jaeger, inspired by Google Dapper (https://research.google.com/pubs/pub36356.html) and OpenZipkin (http://zipkin.io/), is a distributed tracing system that can be used for monitoring microservice-based architectures, including distributed context propagation, distributed transaction monitoring, root cause analysis, service dependency analysis and performance / latency optimization (also integrates with OpenTracing).

Please vote (+1/0/-1) on the full project proposal located here on GitHub: https://github.com/cncf/toc/pull/42

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

Thanks!

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

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




--


Re: [VOTE] Jaeger project proposal (incubation)

Arun Gupta
 

+1 (non-binding)

On Thu, Sep 7, 2017 at 2:02 PM, Chris Aniszczyk via cncf-toc <cncf-toc@...> wrote:
The TOC has decided to invite Jaeger (https://github.com/uber/jaeger) as an incubation level CNCF project, sponsored by Bryan Cantrill from the TOC:

Jaeger, inspired by Google Dapper (https://research.google.com/pubs/pub36356.html) and OpenZipkin (http://zipkin.io/), is a distributed tracing system that can be used for monitoring microservice-based architectures, including distributed context propagation, distributed transaction monitoring, root cause analysis, service dependency analysis and performance / latency optimization (also integrates with OpenTracing).

Please vote (+1/0/-1) on the full project proposal located here on GitHub: https://github.com/cncf/toc/pull/42

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

Thanks!

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

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





Re: [VOTE] Jaeger project proposal (incubation)

Gary Brown
 

+1 (non-binding)

On Thu, Sep 7, 2017 at 10:02 PM, Chris Aniszczyk via cncf-toc <cncf-toc@...> wrote:
The TOC has decided to invite Jaeger (https://github.com/uber/jaeger) as an incubation level CNCF project, sponsored by Bryan Cantrill from the TOC:

Jaeger, inspired by Google Dapper (https://research.google.com/pubs/pub36356.html) and OpenZipkin (http://zipkin.io/), is a distributed tracing system that can be used for monitoring microservice-based architectures, including distributed context propagation, distributed transaction monitoring, root cause analysis, service dependency analysis and performance / latency optimization (also integrates with OpenTracing).

Please vote (+1/0/-1) on the full project proposal located here on GitHub: https://github.com/cncf/toc/pull/42

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

Thanks!

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

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



Re: [VOTE] Jaeger project proposal (incubation)

Chris Wright
 

+1! (non-binding)

On Thu, Sep 7, 2017 at 2:02 PM, Chris Aniszczyk via cncf-toc
<cncf-toc@...> wrote:
The TOC has decided to invite Jaeger (https://github.com/uber/jaeger) as an
incubation level CNCF project, sponsored by Bryan Cantrill from the TOC:

Jaeger, inspired by Google Dapper
(https://research.google.com/pubs/pub36356.html) and OpenZipkin
(http://zipkin.io/), is a distributed tracing system that can be used for
monitoring microservice-based architectures, including distributed context
propagation, distributed transaction monitoring, root cause analysis,
service dependency analysis and performance / latency optimization (also
integrates with OpenTracing).

Please vote (+1/0/-1) on the full project proposal located here on GitHub:
https://github.com/cncf/toc/pull/42

Remember that the TOC has binding votes only, but we do appreciate
non-binding votes from the community as a sign of support!

Thanks!

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

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


Re: [VOTE] Jaeger project proposal (incubation)

Brian Grant
 

+1

On Thu, Sep 7, 2017 at 2:55 PM, Ken Owens via cncf-toc <cncf-toc@...> wrote:
+1

On Thu, Sep 7, 2017 at 4:02 PM, Chris Aniszczyk via cncf-toc <cncf-toc@...> wrote:
The TOC has decided to invite Jaeger (https://github.com/uber/jaeger) as an incubation level CNCF project, sponsored by Bryan Cantrill from the TOC:

Jaeger, inspired by Google Dapper (https://research.google.com/pubs/pub36356.html) and OpenZipkin (http://zipkin.io/), is a distributed tracing system that can be used for monitoring microservice-based architectures, including distributed context propagation, distributed transaction monitoring, root cause analysis, service dependency analysis and performance / latency optimization (also integrates with OpenTracing).

Please vote (+1/0/-1) on the full project proposal located here on GitHub: https://github.com/cncf/toc/pull/42

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

Thanks!

--
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] Envoy project proposal (incubation)

Erin Boyd
 

+1 (non-binding) sounds like an interesting project!

On Thu, Sep 7, 2017 at 4:09 PM, Chris Aniszczyk via cncf-toc <cncf-toc@...> wrote:
I'll close the vote early next week to give time for other TOC members to vote in and any other non-binding community votes.

Thanks everyone for voting.

On Thu, Sep 7, 2017 at 4:55 PM, Alexis Richardson <alexis@...> wrote:
and that's six votes


On Thu, Sep 7, 2017 at 10:53 PM Ken Owens via cncf-toc <cncf-toc@...> wrote:
+1

On Thu, Sep 7, 2017 at 1:26 PM, Chris Aniszczyk <caniszczyk@...g> wrote:
+Ken's new email address so he can vote properly :)

On Fri, Sep 1, 2017 at 8:53 AM, Chris Aniszczyk <caniszczyk@...g> wrote:
The TOC has decided to invite Envoy (https://github.com/lyft/envoy) as an incubation level CNCF project, sponsored by Alexis Richardson from the TOC:

Envoy is a high performance C++ distributed proxy, communication bus and universal data plane designed for large microservice service mesh architectures. Envoy runs alongside every application and abstracts the network by providing common features in a platform-agnostic manner. When all service traffic in an infrastructure flows via an Envoy mesh, it becomes easy to visualize problem areas via consistent observability, tune overall performance, and add substrate features in a single place.

Please vote (+1/0/-1) on the full project proposal located here on GitHub: https://github.com/cncf/toc/pull/43

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

Thanks!

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



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

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



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

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



Re: [VOTE] Envoy project proposal (incubation)

Chris Aniszczyk
 

I'll close the vote early next week to give time for other TOC members to vote in and any other non-binding community votes.

Thanks everyone for voting.

On Thu, Sep 7, 2017 at 4:55 PM, Alexis Richardson <alexis@...> wrote:
and that's six votes


On Thu, Sep 7, 2017 at 10:53 PM Ken Owens via cncf-toc <cncf-toc@...> wrote:
+1

On Thu, Sep 7, 2017 at 1:26 PM, Chris Aniszczyk <caniszczyk@linuxfoundation.org> wrote:
+Ken's new email address so he can vote properly :)

On Fri, Sep 1, 2017 at 8:53 AM, Chris Aniszczyk <caniszczyk@linuxfoundation.org> wrote:
The TOC has decided to invite Envoy (https://github.com/lyft/envoy) as an incubation level CNCF project, sponsored by Alexis Richardson from the TOC:

Envoy is a high performance C++ distributed proxy, communication bus and universal data plane designed for large microservice service mesh architectures. Envoy runs alongside every application and abstracts the network by providing common features in a platform-agnostic manner. When all service traffic in an infrastructure flows via an Envoy mesh, it becomes easy to visualize problem areas via consistent observability, tune overall performance, and add substrate features in a single place.

Please vote (+1/0/-1) on the full project proposal located here on GitHub: https://github.com/cncf/toc/pull/43

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

Thanks!

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



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

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



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


Re: [VOTE] Envoy project proposal (incubation)

alexis richardson
 

and that's six votes


On Thu, Sep 7, 2017 at 10:53 PM Ken Owens via cncf-toc <cncf-toc@...> wrote:
+1

On Thu, Sep 7, 2017 at 1:26 PM, Chris Aniszczyk <caniszczyk@...> wrote:
+Ken's new email address so he can vote properly :)

On Fri, Sep 1, 2017 at 8:53 AM, Chris Aniszczyk <caniszczyk@...> wrote:
The TOC has decided to invite Envoy (https://github.com/lyft/envoy) as an incubation level CNCF project, sponsored by Alexis Richardson from the TOC:

Envoy is a high performance C++ distributed proxy, communication bus and universal data plane designed for large microservice service mesh architectures. Envoy runs alongside every application and abstracts the network by providing common features in a platform-agnostic manner. When all service traffic in an infrastructure flows via an Envoy mesh, it becomes easy to visualize problem areas via consistent observability, tune overall performance, and add substrate features in a single place.

Please vote (+1/0/-1) on the full project proposal located here on GitHub: https://github.com/cncf/toc/pull/43

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

Thanks!

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



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

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