Date   

Re: [VOTE] SAFE (Security) Working Group

Chase Pettet
 

+1 non-binding

How awesome would it be to have common nomenclature and practices across similar methodology for CNCF projects.  This in and of itself would be a huge value add CNCF can bring to the table.

On Tue, Sep 4, 2018 at 8:50 AM, Chris Aniszczyk <caniszczyk@...> wrote:
A new CNCF Working Group has been proposed (sponsored by Ken Owens):

Secure Access for Everyone (SAFE) Working Group will explore secure access, policy control and safety for operators, administrators, developers, and end-users across the cloud native ecosystem

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/146

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

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




--
Chase Pettet
chasemp on phabricator and IRC


Re: [VOTE] SAFE (Security) Working Group

Justin Cormack
 

+1 (non binding)


On Tue, Sep 4, 2018 at 2:50 PM, Chris Aniszczyk <caniszczyk@...> wrote:
A new CNCF Working Group has been proposed (sponsored by Ken Owens):

Secure Access for Everyone (SAFE) Working Group will explore secure access, policy control and safety for operators, administrators, developers, and end-users across the cloud native ecosystem

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/146

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

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



Re: [VOTE] SAFE (Security) Working Group

ytijani@...
 

+1 non-binding

Le mar. 4 sept. 2018 à 15:52, Tom Phelan <tap@...> a écrit :
+1 (non-binding)

On Tue, Sep 4, 2018 at 6:51 AM, Geri Jennings <geri.jennings@...> wrote:

+1 (non-binding)

 

From: <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@...>
Date: Tuesday, September 4, 2018 at 9:50 AM
To: CNCF TOC <cncf-toc@...>
Subject: [cncf-toc] [VOTE] SAFE (Security) Working Group

 

A new CNCF Working Group has been proposed (sponsored by Ken Owens):

 

Secure Access for Everyone (SAFE) Working Group will explore secure access, policy control and safety for operators, administrators, developers, and end-users across the cloud native ecosystem

 

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/146

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

 

--

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


_______________________________________________
This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure.
If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error.




--

view

Thomas Phelan

Chief Architect

650 533 6462

Try BlueData on AWS: www.bluedata.com/AWS


Re: [VOTE] SAFE (Security) Working Group

Tom Phelan
 

+1 (non-binding)

On Tue, Sep 4, 2018 at 6:51 AM, Geri Jennings <geri.jennings@...> wrote:

+1 (non-binding)

 

From: <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@linuxfoundation.org>
Date: Tuesday, September 4, 2018 at 9:50 AM
To: CNCF TOC <cncf-toc@...>
Subject: [cncf-toc] [VOTE] SAFE (Security) Working Group

 

A new CNCF Working Group has been proposed (sponsored by Ken Owens):

 

Secure Access for Everyone (SAFE) Working Group will explore secure access, policy control and safety for operators, administrators, developers, and end-users across the cloud native ecosystem

 

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/146

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

 

--

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


_______________________________________________
This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure.
If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error.




--

view

Thomas Phelan

Chief Architect

650 533 6462

Try BlueData on AWS: www.bluedata.com/AWS


Re: [VOTE] SAFE (Security) Working Group

Ken Owens
 

+1 binding

On Tue, Sep 4, 2018 at 8:50 AM Chris Aniszczyk <caniszczyk@...> wrote:
A new CNCF Working Group has been proposed (sponsored by Ken Owens):

Secure Access for Everyone (SAFE) Working Group will explore secure access, policy control and safety for operators, administrators, developers, and end-users across the cloud native ecosystem

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/146

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

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


Re: [VOTE] SAFE (Security) Working Group

Geri Jennings
 

+1 (non-binding)

 

From: <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@...>
Date: Tuesday, September 4, 2018 at 9:50 AM
To: CNCF TOC <cncf-toc@...>
Subject: [cncf-toc] [VOTE] SAFE (Security) Working Group

 

A new CNCF Working Group has been proposed (sponsored by Ken Owens):

 

Secure Access for Everyone (SAFE) Working Group will explore secure access, policy control and safety for operators, administrators, developers, and end-users across the cloud native ecosystem

 

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/146

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

 

--

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


_______________________________________________
This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure.
If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error.


[VOTE] SAFE (Security) Working Group

Chris Aniszczyk
 

A new CNCF Working Group has been proposed (sponsored by Ken Owens):

Secure Access for Everyone (SAFE) Working Group will explore secure access, policy control and safety for operators, administrators, developers, and end-users across the cloud native ecosystem

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/146

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

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


Re: RSocket Followup (post TOC meeting)

Ben Christensen
 

> why did you feel it necessary to add an additional layer of application flow control on top of what TCP already provides?
 
This is discussed in the FAQ of the project:  https://github.com/rsocket/rsocket/blob/master/FAQ.md#why-reactive-streams-requestn-flow-control
 
The key difference is that RSocket offers end-to-end instead of hop-to-hop flow control and expects to have message-level flow control exposed through APIs into the application layer. This allows non-blocking bounded message queues in user code and prevents buffer bloating of intermediaries. 
 
A key example is an experience I had with a load balancer (TCP, not HTTP in that case) where the hop-to-hop behavior did what it does best - filled the entire buffer of the proxy (load balancer) - which resulted in increasing latency of the end consumer (fast producer, slow consumer problem) until eventually the proxy would OOM and reboot. This required bad hacks to address since the protocol in use did not support end-to-end flow control. Neither HTTP or TCP expose end-to-end flow control mechanisms into the application layer, RSocket allows this. 
 
The responses from Ben Hale earlier also did a good job of explaining this and provided further examples I won't repeat here. 


Re: RSocket Followup (post TOC meeting)

Ben Christensen
 

> Other than to support non-TCP transports (like UDP), which I would assume are fairly uncommon,
 
This is actually something we leverage in production:
 
- TCP for server-to-server
- WebSocket for browser-to-server
- single HTTP/2 stream treated like TCP on shared HTTP/2 connection
 
The need to target both WebSockets and TCP was actually a very concrete initial reason for creating RSocket, since HTTP/2 framing is not exposed in browsers or most client/server APIs. More on this is found in the Motivations doc: https://github.com/rsocket/rsocket/blob/master/FAQ.md#why-not-http2


Re: RSocket Followup (post TOC meeting)

Ben Christensen
 

> How much interoperability testing have you done?
 
We use rsocket-cpp, rsocket-js, and rsocket-java together. C++ as both client and server. JS as a client against C++ and Java, and recently starting to be a server (but that's less tested). Java as client against C++, and as server for JS. 
 
We use TCP, WebSocket, and a single HTTP/2 stream on a shared connection in different places as the transport.
 
- For server-to-server we primarily use TCP. 
- For browser-to-server we use WebSocket. 
- For mobile-to-server we use a single H2 stream for RSocket on a potentially hared H2 connection. 
- For mobile-to-server we are evaluating mapping RSocket streams onto HTTP/2 streams, while being multitenant with other protocols on the same HTTP/2 connection. 
- Both approaches with HTTP/2 do not work with standard HTTP/2 APIs and only work because we expose internals of the protocol in our implementation. The mapping to H2 streams and being multi-tenant also requires custom extensions to H2 so isn't viable broadly (unless we evolve H2). And the H2 mapping does not work in browsers, so we use WebSockets there. 
 


Re: TOC + Community Input: Cloud Native Buildpacks

Chris Aniszczyk
 

Thanks Alexis, I let the folks know to put together an official proposal for the sandbox:

On Tue, Aug 28, 2018 at 10:02 AM, Alexis Richardson <alexis@...> wrote:
I am happy to co-sponsor.

alexis


On Tue, Aug 21, 2018 at 4:45 PM, Chris Aniszczyk
<caniszczyk@linuxfoundation.org> wrote:
> The buildpacks.io community presented at the TOC meeting today:
> https://github.com/cncf/toc/issues/122
>
> Brian Grant is willing to sponsor this for the sandbox so we are looking for
> one more (Camille is potentially interested but needs more time to review).
> We are also seeking input from the TOC and wider community.
>
> Thank you!
>
> --
> Chris Aniszczyk (@cra) | +1-512-961-6719



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


Re: TOC + Community Input: Cloud Native Buildpacks

alexis richardson
 

I am happy to co-sponsor.

alexis


On Tue, Aug 21, 2018 at 4:45 PM, Chris Aniszczyk
<caniszczyk@...> wrote:
The buildpacks.io community presented at the TOC meeting today:
https://github.com/cncf/toc/issues/122

Brian Grant is willing to sponsor this for the sandbox so we are looking for
one more (Camille is potentially interested but needs more time to review).
We are also seeking input from the TOC and wider community.

Thank you!

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


Re: [VOTE] etcd project proposal (incubation)

Michael Hausenblas <mhausenb@...>
 

+1 (non-binding)

Cheers,
Michael

--
Michael Hausenblas, Developer Advocate
OpenShift by Red Hat
Mobile: +353 86 0215164 | Twitter: @mhausenblas
http://openshift.com | http://mhausenblas.info

-----Original Message-----
From: Chris Aniszczyk <caniszczyk@...>
Reply: Chris Aniszczyk <caniszczyk@...>
Date: 21 August 2018 at 16:57:45
To: CNCF TOC <cncf-toc@...>
Subject:  [cncf-toc] [VOTE] etcd project proposal (incubation)

The etcd project is being proposed as an INCUBATION level CNCF project,
sponsored by Brian Grant from the TOC: https://github.com/coreos/etcd

etcd is a consistent distributed key-value store, designed to hold small
amounts of data that can fit entirely in memory and mainly used as a
separate coordination service for other distributed systems like
Kubernetes. It is used by a variety organizations and projects:
https://github.com/coreos/etcd/blob/master/Documentation/production-users.md

Please vote (+1/0/-1) by replying to this thread; the full project proposal
located here: https://github.com/cncf/toc/pull/143

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

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




Re: Feedback on Cortex presentation + call for TOC sponsors

Tom Wilkie <tom.wilkie@...>
 

Thanks Bryan! 


On Wed, Aug 22, 2018 at 7:45 PM Chris Aniszczyk <caniszczyk@...> wrote:

On Wed, Aug 22, 2018 at 1:40 PM, Bryan Cantrill <bryan@...> wrote:

Just to follow up on this: after speaking with the Cortex team, I'm happy to co-sponsor them as a CNCF sandbox project! 

         - Bryan

P.S.  Thanks, too, to the team for educating me as to the surprising subtitle of Mary Shelley's "Frankenstein"!


On Tue, Jun 5, 2018 at 9:16 AM, Tom Wilkie <tom.wilkie@...> wrote:
Hello

First off: thanks for hosting our presentation today!

This is a follow up email as per Chris' suggestion, there were some questions on the chat we didn't get a chance to answer.  Also, if anyone has any other questions, feel free to fire away - and if you'd like to sponsor us... that'd be awesome!

Thanks

Tom





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


Re: [VOTE] etcd project proposal (incubation)

Ken Owens
 

+1 Binding

On Tue, Aug 21, 2018 at 6:34 PM Junghyun Kim <kjh@...> wrote:

+1 (non-binding)

 

From: <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@...>
Date: Tuesday, 21 August 2018 at 11:57 PM
To: CNCF TOC <cncf-toc@...>
Subject: [cncf-toc] [VOTE] etcd project proposal (incubation)

 

The etcd project is being proposed as an INCUBATION level CNCF project, sponsored by Brian Grant from the TOC: https://github.com/coreos/etcd

 

etcd is a consistent distributed key-value store, designed to hold small amounts of data that can fit entirely in memory and mainly used as a separate coordination service for other distributed systems like Kubernetes. It is used by a variety organizations and projects: https://github.com/coreos/etcd/blob/master/Documentation/production-users.md


Please vote (+1/0/-1) by replying to this thread; the full project proposal located here: https://github.com/cncf/toc/pull/143


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

 

--

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


Re: [VOTE] etcd project proposal (incubation)

Erin Boyd
 

+1 non-binding

On Tue, Aug 21, 2018 at 9:35 AM, Isaac Mosquera via Lists.Cncf.Io <isaac=armory.io@...> wrote:
+1 (non-binding)

On Tue, Aug 21, 2018 at 8:29 AM, Andrew Randall <andy@...> wrote:
+1 (non-binding)

-- 
Andy Randall
Co-Founder, VP Business Development
Tigera
andy@... | M: +1 510-520-0999 | @andrew_randall
Follow us: Blog | Twitter | LinkedIn 

Zero Trust Network Security & Continuous Compliance for Modern Applications

On Aug 21, 2018, at 7:57 AM, Chris Aniszczyk <caniszczyk@...g> wrote:

The etcd project is being proposed as an INCUBATION level CNCF project, sponsored by Brian Grant from the TOC: https://github.com/coreos/etcd

etcd is a consistent distributed key-value store, designed to hold small amounts of data that can fit entirely in memory and mainly used as a separate coordination service for other distributed systems like Kubernetes. It is used by a variety organizations and projects: https://github.com/coreos/etcd/blob/master/Documentation/production-users.md

Please vote (+1/0/-1) by replying to this thread; the full project proposal located here: https://github.com/cncf/toc/pull/143

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

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




--


#velocity,


I S A A C  M O S Q U E R A

Chief Technology Officer

e: isaac@...

p: 703.795.5322

t: imosquera



Re: [VOTE] etcd project proposal (incubation)

Tamal Saha
 

+1 non-binding

Regards,
-Tamal


On Tue, Aug 21, 2018 at 7:57 AM Chris Aniszczyk <caniszczyk@...> wrote:
The etcd project is being proposed as an INCUBATION level CNCF project, sponsored by Brian Grant from the TOC: https://github.com/coreos/etcd

etcd is a consistent distributed key-value store, designed to hold small amounts of data that can fit entirely in memory and mainly used as a separate coordination service for other distributed systems like Kubernetes. It is used by a variety organizations and projects: https://github.com/coreos/etcd/blob/master/Documentation/production-users.md

Please vote (+1/0/-1) by replying to this thread; the full project proposal located here: https://github.com/cncf/toc/pull/143

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

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


Re: [VOTE] etcd project proposal (incubation)

iftach Schonbaum
 

+1 non-binding

 

Iftach Schonbaum

Senior Solution Architect

+972-52-8281751

cloudzone.io

 

 

 

From: <cncf-toc@...> on behalf of 郑淮城 <huaicheng.zheng@...>
Date: Thursday, 23 August 2018 at 5:01
To: Chris Aniszczyk <caniszczyk@...>, CNCF TOC <cncf-toc@...>
Subject: Re: [cncf-toc] [VOTE] etcd project proposal (incubation)

 

+1 non-binding

 

郑淮城
星环信息科技(上海)有限公司
15216615728
徐汇区虹漕路88号越虹广场B11-12

 

 

发件人: <cncf-toc@...> 代表 Chris Aniszczyk <caniszczyk@...>
日期: 2018821 星期二 下午10:57
收件人: CNCF TOC <cncf-toc@...>
主题: [cncf-toc] [VOTE] etcd project proposal (incubation)

 

The etcd project is being proposed as an INCUBATION level CNCF project, sponsored by Brian Grant from the TOC: https://github.com/coreos/etcd

 

etcd is a consistent distributed key-value store, designed to hold small amounts of data that can fit entirely in memory and mainly used as a separate coordination service for other distributed systems like Kubernetes. It is used by a variety organizations and projects: https://github.com/coreos/etcd/blob/master/Documentation/production-users.md


Please vote (+1/0/-1) by replying to this thread; the full project proposal located here: https://github.com/cncf/toc/pull/143


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

 

--

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


Re: [VOTE] etcd project proposal (incubation)

郑淮城 <huaicheng.zheng@...>
 

+1 non-binding

 

郑淮城
星环信息科技(上海)有限公司
15216615728
徐汇区虹漕路88号越虹广场B11-12

 

 

发件人: <cncf-toc@...> 代表 Chris Aniszczyk <caniszczyk@...>
日期: 2018821 星期二 下午10:57
收件人: CNCF TOC <cncf-toc@...>
主题: [cncf-toc] [VOTE] etcd project proposal (incubation)

 

The etcd project is being proposed as an INCUBATION level CNCF project, sponsored by Brian Grant from the TOC: https://github.com/coreos/etcd

 

etcd is a consistent distributed key-value store, designed to hold small amounts of data that can fit entirely in memory and mainly used as a separate coordination service for other distributed systems like Kubernetes. It is used by a variety organizations and projects: https://github.com/coreos/etcd/blob/master/Documentation/production-users.md


Please vote (+1/0/-1) by replying to this thread; the full project proposal located here: https://github.com/cncf/toc/pull/143


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

 

--

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


Re: [VOTE] etcd project proposal (incubation)

colin@...
 

+1 non-binding

5021 - 5040 of 7342