1. Cncf-Toc
  2. Messages

Expanded

Topics Messages Polls
   Date   
Re: [VOTE] Rook moving to incubation

Steve Kokhang Leon
 

+1 (non binding) 


On Thu, Sep 6, 2018, 8:19 AM Chris Aniszczyk <caniszczyk@...> wrote:
Rook (https://rook.io) has requested to move to the incubation maturity level:

In the time since being accepted to the sandbox, two releases were completed, starting with v0.7 on February 21st and then v0.8 on July 18th. With those releases, Rook extended beyond just orchestration of Ceph and has built a framework of reusable specs, logic and policies for cloud-native storage orchestration of other providers. Operators and CRD types were added for both CockroachDB and Minio in the v0.8 release, initial support for NFS is nearly complete, and other storage providers are also in the works.

The Rook community believes it has fulfilled all the incubation criteria:

Document that it is being used successfully in production by at least three independent end users which, in the TOC’s judgement, are of adequate quality and scope: https://github.com/rook/rook/blob/master/ADOPTERS.md

Maintainers of the project are listed in https://github.com/rook/rook/blob/master/OWNERS.md.

Maintainers are added and removed from the project as per the policies outlined in the project governance: https://github.com/rook/rook/blob/master/GOVERNANCE.md

Demonstrate a substantial ongoing flow of commits and merged contributions:

Releases: https://github.com/rook/rook/releases
Roadmap: https://github.com/rook/rook/blob/master/ROADMAP.md
Contributors: https://github.com/rook/rook/graphs/contributors
Commit activity: https://github.com/rook/rook/graphs/commit-activity
CNCF DevStats: https://rook.devstats.cncf.io/

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

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] Rook moving to incubation

Alex Chircop
 

+1 (non-binding)

 

From: cncf-toc@... <cncf-toc@...> On Behalf Of Chris Aniszczyk
Sent: 06 September 2018 16:20
To: CNCF TOC <cncf-toc@...>
Subject: [cncf-toc] [VOTE] Rook moving to incubation

 

Rook (https://rook.io) has requested to move to the incubation maturity level:

 

In the time since being accepted to the sandbox, two releases were completed, starting with v0.7 on February 21st and then v0.8 on July 18th. With those releases, Rook extended beyond just orchestration of Ceph and has built a framework of reusable specs, logic and policies for cloud-native storage orchestration of other providers. Operators and CRD types were added for both CockroachDB and Minio in the v0.8 release, initial support for NFS is nearly complete, and other storage providers are also in the works.


The Rook community believes it has fulfilled all the incubation criteria:

Document that it is being used successfully in production by at least three independent end users which, in the TOC’s judgement, are of adequate quality and scope: https://github.com/rook/rook/blob/master/ADOPTERS.md

Maintainers of the project are listed in https://github.com/rook/rook/blob/master/OWNERS.md.

Maintainers are added and removed from the project as per the policies outlined in the project governance: https://github.com/rook/rook/blob/master/GOVERNANCE.md

Demonstrate a substantial ongoing flow of commits and merged contributions:

Releases: https://github.com/rook/rook/releases
Roadmap: https://github.com/rook/rook/blob/master/ROADMAP.md
Contributors: https://github.com/rook/rook/graphs/contributors
Commit activity: https://github.com/rook/rook/graphs/commit-activity
CNCF DevStats: https://rook.devstats.cncf.io/

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

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] Rook moving to incubation

Joseph Jacks <j@...>
 

Very big (non-binding) +1 !

On Sep 6, 2018, at 8:19 AM, Chris Aniszczyk <caniszczyk@...> wrote:

Rook (https://rook.io) has requested to move to the incubation maturity level:

In the time since being accepted to the sandbox, two releases were completed, starting with v0.7 on February 21st and then v0.8 on July 18th. With those releases, Rook extended beyond just orchestration of Ceph and has built a framework of reusable specs, logic and policies for cloud-native storage orchestration of other providers. Operators and CRD types were added for both CockroachDB and Minio in the v0.8 release, initial support for NFS is nearly complete, and other storage providers are also in the works.

The Rook community believes it has fulfilled all the incubation criteria:

Document that it is being used successfully in production by at least three independent end users which, in the TOC’s judgement, are of adequate quality and scope: https://github.com/rook/rook/blob/master/ADOPTERS.md

Maintainers of the project are listed in https://github.com/rook/rook/blob/master/OWNERS.md.

Maintainers are added and removed from the project as per the policies outlined in the project governance: https://github.com/rook/rook/blob/master/GOVERNANCE.md

Demonstrate a substantial ongoing flow of commits and merged contributions:

Releases: https://github.com/rook/rook/releases
Roadmap: https://github.com/rook/rook/blob/master/ROADMAP.md
Contributors: https://github.com/rook/rook/graphs/contributors
Commit activity: https://github.com/rook/rook/graphs/commit-activity
CNCF DevStats: https://rook.devstats.cncf.io/

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

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] Rook moving to incubation

Ihor Dvoretskyi
 

+1 (non-binding).


On Thu, Sep 6, 2018, 6:19 PM Chris Aniszczyk <caniszczyk@...> wrote:
Rook (https://rook.io) has requested to move to the incubation maturity level:

In the time since being accepted to the sandbox, two releases were completed, starting with v0.7 on February 21st and then v0.8 on July 18th. With those releases, Rook extended beyond just orchestration of Ceph and has built a framework of reusable specs, logic and policies for cloud-native storage orchestration of other providers. Operators and CRD types were added for both CockroachDB and Minio in the v0.8 release, initial support for NFS is nearly complete, and other storage providers are also in the works.

The Rook community believes it has fulfilled all the incubation criteria:

Document that it is being used successfully in production by at least three independent end users which, in the TOC’s judgement, are of adequate quality and scope: https://github.com/rook/rook/blob/master/ADOPTERS.md

Maintainers of the project are listed in https://github.com/rook/rook/blob/master/OWNERS.md.

Maintainers are added and removed from the project as per the policies outlined in the project governance: https://github.com/rook/rook/blob/master/GOVERNANCE.md

Demonstrate a substantial ongoing flow of commits and merged contributions:

Releases: https://github.com/rook/rook/releases
Roadmap: https://github.com/rook/rook/blob/master/ROADMAP.md
Contributors: https://github.com/rook/rook/graphs/contributors
Commit activity: https://github.com/rook/rook/graphs/commit-activity
CNCF DevStats: https://rook.devstats.cncf.io/

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

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
[VOTE] Rook moving to incubation

Chris Aniszczyk
 

Rook (https://rook.io) has requested to move to the incubation maturity level:

In the time since being accepted to the sandbox, two releases were completed, starting with v0.7 on February 21st and then v0.8 on July 18th. With those releases, Rook extended beyond just orchestration of Ceph and has built a framework of reusable specs, logic and policies for cloud-native storage orchestration of other providers. Operators and CRD types were added for both CockroachDB and Minio in the v0.8 release, initial support for NFS is nearly complete, and other storage providers are also in the works.

The Rook community believes it has fulfilled all the incubation criteria:

Document that it is being used successfully in production by at least three independent end users which, in the TOC’s judgement, are of adequate quality and scope: https://github.com/rook/rook/blob/master/ADOPTERS.md

Maintainers of the project are listed in https://github.com/rook/rook/blob/master/OWNERS.md.

Maintainers are added and removed from the project as per the policies outlined in the project governance: https://github.com/rook/rook/blob/master/GOVERNANCE.md

Demonstrate a substantial ongoing flow of commits and merged contributions:

Releases: https://github.com/rook/rook/releases
Roadmap: https://github.com/rook/rook/blob/master/ROADMAP.md
Contributors: https://github.com/rook/rook/graphs/contributors
Commit activity: https://github.com/rook/rook/graphs/commit-activity
CNCF DevStats: https://rook.devstats.cncf.io/

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

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

Ylinen, Mikko
 


+1 (non-binding)

On Tue, Sep 4, 2018 at 4: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: RFC: Dragonfly

AllenSun
 

Hi, Randy,

Thanks for your feedback.

We are very sure that all these adopters of Dragonfly are using Dragonfly in production like what I mentioned in my presentation.
Since Dragonfly is very neutral, and totally a plugin component for original Architecture of Enterprises, it is invasive and easy to integrate Dragonfly.

In addition, we can say Dragonfly indeed brings lots of value to help these adopters in image management. 
For China Mobile, their container platform is quite huge, more than a thousand nodes, Dragonfly in production helps a lot to speed up the image distribution efficiency.
For iTEKFLY, the most famous speech intelligent company, they have quite huge images(more than 20GB) for speech processing, Dragonfly is the perfect one for them to reduce distribution time.
For Ant Financial, sensitive business running in their datacenter, Dragonfly has also been a fundamental infrastructure tool, and tens of thousands of host are using it.
For other adopters, they are also meeting the same image distribution issues, and Dragonfly is the best choice.

In Alibaba,  we have been using Dragonfly at large scale for more than 2 years.

> how you calculated adoption

We held several meetups in China, and set up good relationship with the community. Developers from these adopters have communicated with us to share their adoption and wished to seek support from the community.
Currently we say more than 20+ adopters, but in fact I am afraid the amount of real adopters are larger than this number.

Best Regards.

Allen Sun
Alibaba Group


------------------------------------------------------------------
Sender:Randy Levensalor <R.Levensalor@...>
Sent at:2018 Sep 6 (Thu) 03:15
Recipient:Allen <allensun.shl@...>
Subject:Re: [cncf-toc] RFC: Dragonfly

Hi AllenSun, 

The dragonfly project looks very interesting. Thanks for sharing. 

I was wondering how you calculated adoption. Is this the number of companies that have Dragonfly in production or have installed it in a trial? 

Randy Levensalor | r.levensalor@...
CableLabs® | o 303.661.3455 | c 970.214.1316

On Sep 4, 2018 11:57 AM, AllenSun <allensun.shl@...> wrote:

Hi, Friends,

It is my honor to give a presentation about Dragonfly to CNCF community. Dragonfly aims at covering all the image distribution in CNCF ecosystem. And currently it works perfectly within Kubernetes. My slides are in the attachment of this email.

Please feel free to give us your feedback on Dragonfly. Any thoughts on it are welcome.

In addition, I am really happy that Jonathan Boulle would like to sponsor Dragonfly to enter sandbox level.
While we sincerely wish that an additional TOC member could sponsor this.
How to get help from Dragonfly's team, if you are interested in this, please don't hesitate to drop questions on me.
Thanks a lot.
Allen Sun
Alibaba Group


------------------------------------------------------------------
Sender:Chris Aniszczyk <caniszczyk@...>
Sent at:2018 Sep 4 (Tue) 23:33
Recipient:CNCF TOC <cncf-toc@...>
Cc:Allen <allensun.shl@...>
Subject:[cncf-toc] RFC: Dragonfly

The Dragonfly project was presented to the TOC today:

They currently have one TOC sponsor, Jonathan Boulle.

The Dragonfly community is seeking an additional TOC sponsor and happy to answer any questions from the community.

--
Chris Aniszczyk (@cra) | +1-512-961-6719
Re: [VOTE] SAFE (Security) Working Group

Yuan Chen <yuan.chen@...>
 

+1 (non-binding)

 

Yuan Chen

Principal Architect, JD Silicon Valley R&D Center

 

From: <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@...>
Date: Tuesday, September 4, 2018 at 6: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
Re: [VOTE] SAFE (Security) Working Group

Josef Adersberger
 

+1 (non-binding)

Chris Aniszczyk <caniszczyk@...> schrieb am Di. 4. Sep. 2018 um 15:50:

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

--

Beste Arbeitgeber ITK 2018 - 1.Platz für QAware
ausgezeichnet von Great Place to Work und kununu

Dr. Josef Adersberger
Technischer Geschäftsführer

QAware GmbH
Aschauer Str. 32
81549 München, Germany
Tel +49 89 232315-113
Mobil +49 170 3075572
Fax +49 89 232315-129
josef.adersberger@...
www.qaware.de

Geschäftsführer: Christian Kamm, Bernd Schlüter, Johannes Weigend, Dr. Josef Adersberger
Registergericht: München
Handelsregisternummer: HRB 163761
Re: [VOTE] SAFE (Security) Working Group

Carlos Arturo Quiroga <cquiroga@...>
 

+1 (non-binding)

Carlos Arturo Quiroga Quiroga.

"Daniel Bryant" ---09/05/2018 03:34:24 AM---+1 (non-binding) On Tue, Sep 4, 2018 at 2:50 PM Chris Aniszczyk <

From: "Daniel Bryant" <db@...>
To: CNCF TOC <cncf-toc@...>
Date: 09/05/2018 03:34 AM
Subject: Re: [cncf-toc] [VOTE] SAFE (Security) Working Group
Sent by: cncf-toc@...



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):
    https://github.com/cn-security/safe

    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

wangpengfei@yanrongyun.com
 

+1 (non-binding)


---------------------------------------
王鹏飞
Technical VP

北京焱融科技有限公司
手机：+86-13681265240
邮箱：wangpengfei@yanrongyun.com

 
Date: 2018-09-04 21:50
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
Re: [VOTE] SAFE (Security) Working Group

Evan Gilman
 

+1 non-binding
Re: [VOTE] SAFE (Security) Working Group

Yong Tang
 

+1 (non binding)

From: cncf-toc@... <cncf-toc@...> on behalf of Chris Aniszczyk <caniszczyk@...>
Sent: Tuesday, September 4, 2018 6:50 AM
To: 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
Re: [VOTE] SAFE (Security) Working Group

Daniel Bryant
 

+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: RFC: Dragonfly

AllenSun
 

Hi, Deepak Vij,

Thanks for your feedback.
Yes, it's a great job to support image pulling optimization in scheduling of Kubernetes. 

I think that the important feature you mentioned is 

  • focus on scheduler's scheduling algorithm;
  • image layer tracking information of node is a factor of scheduler;
  • scheduling algorithm may reduce the image pulling if scheduling workload to a node if image layer exists on that node.

So, image pulling optimization you mentioned in on scheduling, while Dragonfly is mainly on Image Distribution. I think they are decoupled and only have few of overlapping.
In addition, I think this feature and Dragonfly can co-exist very well to help improve image pulling. The feature decides the workload location by scheduling, and Dragonfly can improve the rest image distribution.

Dragonfly takes over the image distribution for Kubernetes, and image pulling efficiency is only one part of distribution. Besides this, it also provides:

  • image distribution flow control;
  • image distribution security.

Currently all the three parts above consist of Dragonfly's service.

Best Regards.

Allen Sun
Alibaba Group



------------------------------------------------------------------
Sender:Deepak Vij <deepak.vij@...>
Sent at:2018 Sep 5 (Wed) 09:20
Recipient:Allen <allensun.shl@...>; cncf-toc <cncf-toc@...>
Subject:Re: [cncf-toc] RFC: Dragonfly

While we are on the topic of image pulling optimizations, following granular image layers level optimizations are being worked on as part of Kubernetes Scheduling SIG future release feature:  

1)      Layer tracking system on each machine/node discovers the layer information from local file-system and reports this information to workload scheduler (for example, K8S scheduler in our case).

2)      As part of the image resolution process for an incoming container workload, image request is decomposed to underlying layer requests.

3)      Scheduler uses these two pieces of information to perform workload scheduling in accordance to the layering information on the node.

Regards,

Deepak Vij

 

From: cncf-toc@... [mailto:cncf-toc@...] On Behalf Of AllenSun
Sent: Tuesday, September 04, 2018 10:56 AM
To: cncf-toc <cncf-toc@...>
Subject: Re: [cncf-toc] RFC: Dragonfly

 

 

Hi, Friends,

 

It is my honor to give a presentation about Dragonfly to CNCF community. Dragonfly aims at covering all the image distribution in CNCF ecosystem. And currently it works perfectly within Kubernetes. My slides are in the attachment of this email.

 

Please feel free to give us your feedback on Dragonfly. Any thoughts on it are welcome.

 

In addition, I am really happy that Jonathan Boulle would like to sponsor Dragonfly to enter sandbox level.

While we sincerely wish that an additional TOC member could sponsor this.

 

How to get help from Dragonfly's team, if you are interested in this, please don't hesitate to drop questions on me.

 

Thanks a lot.

 

Allen Sun

Alibaba Group

 

 

 

 

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

Sender:Chris Aniszczyk <caniszczyk@...>

Sent at:2018 Sep 4 (Tue) 23:33

Recipient:CNCF TOC <cncf-toc@...>

Cc:Allen <allensun.shl@...>

Subject:[cncf-toc] RFC: Dragonfly

 

The Dragonfly project was presented to the TOC today:

 

They currently have one TOC sponsor, Jonathan Boulle.

 

The Dragonfly community is seeking an additional TOC sponsor and happy to answer any questions from the community.

 

--

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

 
Re: RFC: Dragonfly

Deepak Vij <deepak.vij@...>
 

While we are on the topic of image pulling optimizations, following granular image layers level optimizations are being worked on as part of Kubernetes Scheduling SIG future release feature:  

1)      Layer tracking system on each machine/node discovers the layer information from local file-system and reports this information to workload scheduler (for example, K8S scheduler in our case).

2)      As part of the image resolution process for an incoming container workload, image request is decomposed to underlying layer requests.

3)      Scheduler uses these two pieces of information to perform workload scheduling in accordance to the layering information on the node.

Regards,

Deepak Vij

 

From: cncf-toc@... [mailto:cncf-toc@...] On Behalf Of AllenSun
Sent: Tuesday, September 04, 2018 10:56 AM
To: cncf-toc <cncf-toc@...>
Subject: Re: [cncf-toc] RFC: Dragonfly

 

 

Hi, Friends,

 

It is my honor to give a presentation about Dragonfly to CNCF community. Dragonfly aims at covering all the image distribution in CNCF ecosystem. And currently it works perfectly within Kubernetes. My slides are in the attachment of this email.

 

Please feel free to give us your feedback on Dragonfly. Any thoughts on it are welcome.

 

In addition, I am really happy that Jonathan Boulle would like to sponsor Dragonfly to enter sandbox level.

While we sincerely wish that an additional TOC member could sponsor this.

 

How to get help from Dragonfly's team, if you are interested in this, please don't hesitate to drop questions on me.

 

Thanks a lot.

 

Allen Sun

Alibaba Group

 

 

 

 

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

Sender:Chris Aniszczyk <caniszczyk@...>

Sent at:2018 Sep 4 (Tue) 23:33

Recipient:CNCF TOC <cncf-toc@...>

Cc:Allen <allensun.shl@...>

Subject:[cncf-toc] RFC: Dragonfly

 

The Dragonfly project was presented to the TOC today:

 

They currently have one TOC sponsor, Jonathan Boulle.

 

The Dragonfly community is seeking an additional TOC sponsor and happy to answer any questions from the community.

 

--

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

 
Re: [VOTE] SAFE (Security) Working Group

Zhipeng Huang
 

+1 non-binding :)

On Wed, Sep 5, 2018 at 4:33 AM Ayrat Khayretdinov <akhayretdinov@...> wrote:
+1 (non-binding)

On Tue, Sep 4, 2018 at 9: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



--
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
Re: [VOTE] SAFE (Security) Working Group

Ayrat Khayretdinov <akhayretdinov@...>
 

+1 (non-binding)


On Tue, Sep 4, 2018 at 9: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

Gou Rao <grao@...>
 

+1 (non-binding)

On Tue, Sep 4, 2018 at 6: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

Tamal Saha
 

+1 (non-binding)

-Tamal


On Tue, Sep 4, 2018 at 6: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
5661 - 5680 of 8027