Hey Eduardo, the current feeling within the TOC was that everyone was slammed with the conference coming up next week to do formal reviews.

We plan to discuss the graduation review process at the TOC F2F next week and make a decision.

Thanks.

On Fri, Dec 1, 2017 at 7:32 PM, Eduardo Silva via cncf-toc <cncf-toc@...> wrote:

Hello TOC!, 

Fluentd team have sent a PR with the required information for the graduation review of the project, would you please take a look at it and share some feedback ? 

https://github.com/cncf/toc/pull/69

thanks, 

--

Eduardo Silva

Open Source, Treasure Data

http://www.treasuredata.com/opensource

 

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

--

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

Hello TOC!, 

Fluentd team have sent a PR with the required information for the graduation review of the project, would you please take a look at it and share some feedback ? 

https://github.com/cncf/toc/pull/69

thanks, 

--

Eduardo Silva

Open Source, Treasure Data

http://www.treasuredata.com/opensource

 

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

Hey all, just letting you know the TOC Principles have been approved:

https://github.com/cncf/toc/blob/master/PRINCIPLES.md

+1 binding TOC votes from:

Alexis: https://lists.cncf.io/pipermail/cncf-toc/2017-November/001382.html
BrianG: https://lists.cncf.io/pipermail/cncf-toc/2017-November/001314.html
Solomon: https://lists.cncf.io/pipermail/cncf-toc/2017-November/001324.html
Jon: https://lists.cncf.io/pipermail/cncf-toc/2017-November/001353.html
Ken: https://lists.cncf.io/pipermail/cncf-toc/2017-November/001354.html
Ben: https://lists.cncf.io/pipermail/cncf-toc/2017-November/001355.html
Camille: https://lists.cncf.io/pipermail/cncf-toc/2017-November/001379.html
Bryan: https://lists.cncf.io/pipermail/cncf-toc/2017-November/001380.html
SamL: https://github.com/cncf/toc/pull/47#issuecomment-344150385

+1 non-binding community votes:

Bassam Tabbara: https://lists.cncf.io/pipermail/cncf-toc/2017-November/001317.html

Lee Calcote: https://lists.cncf.io/pipermail/cncf-toc/2017-November/001321.html

Bradley Allen: https://lists.cncf.io/pipermail/cncf-toc/2017-November/001323.html

Nick Chase: https://lists.cncf.io/pipermail/cncf-toc/2017-November/001319.html

John Belamaric: https://lists.cncf.io/pipermail/cncf-toc/2017-November/001322.html

Erin Boyd: https://lists.cncf.io/pipermail/cncf-toc/2017-November/001381.html

Thanks all!

--

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

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

 +1 non-binding

On Mon, Nov 20, 2017 at 6:24 PM, Bryan Cantrill via cncf-toc <cncf-toc@...> wrote:

+1 (And sorry for the delay!)

         - Bryan

On Thu, Nov 2, 2017 at 9:00 AM, Chris Aniszczyk via cncf-toc <cncf-toc@...> wrote:

Hey all y'all, the CNCF TOC principles had enough time to bake and are ready for TOC vote:

https://github.com/cncf/toc/pull/47

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

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

+1 (And sorry for the delay!)

         - Bryan

On Thu, Nov 2, 2017 at 9:00 AM, Chris Aniszczyk via cncf-toc <cncf-toc@...> wrote:

Hey all y'all, the CNCF TOC principles had enough time to bake and are ready for TOC vote:

https://github.com/cncf/toc/pull/47

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

Hey all y'all, the CNCF TOC principles had enough time to bake and are ready for TOC vote:

https://github.com/cncf/toc/pull/47

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

+1

On Mon, Nov 13, 2017 at 9:30 AM Ken Owens via cncf-toc <cncf-toc@...> wrote:

+1 

On Mon, Nov 13, 2017 at 7:47 AM, Jonathan Boulle via cncf-toc <cncf-toc@...> wrote:

+1 from me

On 2 November 2017 at 23:29, Chris Aniszczyk via cncf-toc <cncf-toc@...> wrote:

email is immutable so we stick with that for official voting

thanks Solomon!

On Thu, Nov 2, 2017 at 10:28 PM, Solomon Hykes <solomon.hykes@...> wrote:

+1

Do you want us to approve in github also? Or does email voting remain the source of truth?

On Thursday, November 2, 2017, Chris Aniszczyk via cncf-toc <cncf-toc@...> wrote:

Hey all y'all, the CNCF TOC principles had enough time to bake and are ready for TOC vote:

https://github.com/cncf/toc/pull/47

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

_______________________________________________
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

Mesosphere Inc. 

Follow us on Twitter: @mesosphere

 

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

I've been reading it this morning. I think SPIFFE/SPIRE, OPA, and Vault fit nicely within that framing. Frankly, I think proxies fit within the AAA category, too.

Maybe we're even talking about "AAA" being a new horizontal layer below "Orchestration & Management," within which include the following four (4) categories:

1) Authentication

2) Authorization

3) Key Management

4) Proxies

That said, I'm happy to defer to more thoughtful evaluations :)

---

SJ | sunil@... | Scytale & SPIFFE

On Wed, Nov 15, 2017 at 11:55 AM, Alexis Richardson <alexis@...> wrote:

On Wed, Nov 15, 2017 at 7:52 PM, Sunil James <sunil@...> wrote:

Tough one, but I'd say "yes."

I am ok with that.  Wonder what others think?

 

FWIW, we should probably read through RFC 2989 (specifically the agreed-upon terminology) for historical context.

Is that an offer? ;-)

a

 

---

SJ | sunil@... | Scytale & SPIFFE

On Wed, Nov 15, 2017 at 11:32 AM, Alexis Richardson <alexis@...> wrote:

would you suggest moving key management to AAA?

On Wed, Nov 15, 2017 at 6:09 PM, Sunil James via cncf-toc <cncf-toc@...> wrote:

+1 to this framing, particularly to its cross-cutting nature. While I agree 'security' is a natural starting bucket, the value propositions these (and other) projects address go beyond this (over time).

Visually, perhaps the TOC should consider a "AAA" box (or something more elegantly worded) to the right (or left) of 'Service Management'?

---

SJ | sunil@... | Scytale & SPIFFE

On Wed, Nov 15, 2017 at 8:13 AM, Tim Hinrichs via cncf-toc <cncf-toc@...> wrote:

+1 to the Authentication (SPIFFE, spire), Authorization (OPA), Audit (?).  Classically these are part of Security, but there's no box for that.  

AAA is typically cross-cutting.  OPA, for example, has integrations with Kube (orchestration), Istio (app), Terraform (provisioning), AWS (cloud).

Tim

On Wed, Nov 15, 2017 at 7:33 AM Guru Chahal via cncf-toc <cncf-toc@...> wrote:

Similar functions have often been classified as "AAA" in traditional systems (Authentication, Authorization, Accounting). I agree that no box really captures these well today - the closest are likely 'coordination and service discover' or perhaps 'service management'. I'd imagine 'service management' is the the likely best current home... Istio is listed there as well today (most adjacent to these projects today). 

-Guru

On Wed, Nov 15, 2017 at 6:59 AM, Alexis Richardson via cncf-toc <cncf-toc@...> wrote:

That was where I was going...

Do others agree?

On Wed, Nov 15, 2017 at 2:58 PM, Nick Chase <nchase@...> wrote:

I think OPA belongs in the top layer but I don't think it fits in any of the existing subcategories.  In fact I feel that way about all three.

---- Nick

On Wednesday, November 15, 2017, Alexis Richardson via cncf-toc <cncf-toc@...> wrote:

All,

Question about the landscape.

https://raw.githubusercontent.com/cncf/landscape/master/landscape/CloudNativeLandscape_latest.jpg

- do we want to put OPA in the top layer, either inside, or next to App Def?

- what about identity - spiffe and spire?

- do we think key management should move to top layer?

a

_______________________________________________
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

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

On Wed, Nov 15, 2017 at 7:52 PM, Sunil James <sunil@...> wrote:

Tough one, but I'd say "yes."

I am ok with that.  Wonder what others think?

 

FWIW, we should probably read through RFC 2989 (specifically the agreed-upon terminology) for historical context.

Is that an offer? ;-)

a

 

---

SJ | sunil@... | Scytale & SPIFFE

On Wed, Nov 15, 2017 at 11:32 AM, Alexis Richardson <alexis@...> wrote:

would you suggest moving key management to AAA?

On Wed, Nov 15, 2017 at 6:09 PM, Sunil James via cncf-toc <cncf-toc@...> wrote:

+1 to this framing, particularly to its cross-cutting nature. While I agree 'security' is a natural starting bucket, the value propositions these (and other) projects address go beyond this (over time).

Visually, perhaps the TOC should consider a "AAA" box (or something more elegantly worded) to the right (or left) of 'Service Management'?

---

SJ | sunil@... | Scytale & SPIFFE

On Wed, Nov 15, 2017 at 8:13 AM, Tim Hinrichs via cncf-toc <cncf-toc@...> wrote:

+1 to the Authentication (SPIFFE, spire), Authorization (OPA), Audit (?).  Classically these are part of Security, but there's no box for that.  

AAA is typically cross-cutting.  OPA, for example, has integrations with Kube (orchestration), Istio (app), Terraform (provisioning), AWS (cloud).

Tim

On Wed, Nov 15, 2017 at 7:33 AM Guru Chahal via cncf-toc <cncf-toc@...> wrote:

Similar functions have often been classified as "AAA" in traditional systems (Authentication, Authorization, Accounting). I agree that no box really captures these well today - the closest are likely 'coordination and service discover' or perhaps 'service management'. I'd imagine 'service management' is the the likely best current home... Istio is listed there as well today (most adjacent to these projects today). 

-Guru

On Wed, Nov 15, 2017 at 6:59 AM, Alexis Richardson via cncf-toc <cncf-toc@...> wrote:

That was where I was going...

Do others agree?

On Wed, Nov 15, 2017 at 2:58 PM, Nick Chase <nchase@...> wrote:

I think OPA belongs in the top layer but I don't think it fits in any of the existing subcategories.  In fact I feel that way about all three.

---- Nick

On Wednesday, November 15, 2017, Alexis Richardson via cncf-toc <cncf-toc@...> wrote:

All,

Question about the landscape.

https://raw.githubusercontent.com/cncf/landscape/master/landscape/CloudNativeLandscape_latest.jpg

- do we want to put OPA in the top layer, either inside, or next to App Def?

- what about identity - spiffe and spire?

- do we think key management should move to top layer?

a

_______________________________________________
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

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

would you suggest moving key management to AAA?

On Wed, Nov 15, 2017 at 6:09 PM, Sunil James via cncf-toc <cncf-toc@...> wrote:

+1 to this framing, particularly to its cross-cutting nature. While I agree 'security' is a natural starting bucket, the value propositions these (and other) projects address go beyond this (over time).

Visually, perhaps the TOC should consider a "AAA" box (or something more elegantly worded) to the right (or left) of 'Service Management'?

---

SJ | sunil@... | Scytale & SPIFFE

On Wed, Nov 15, 2017 at 8:13 AM, Tim Hinrichs via cncf-toc <cncf-toc@...> wrote:

+1 to the Authentication (SPIFFE, spire), Authorization (OPA), Audit (?).  Classically these are part of Security, but there's no box for that.  

AAA is typically cross-cutting.  OPA, for example, has integrations with Kube (orchestration), Istio (app), Terraform (provisioning), AWS (cloud).

Tim

On Wed, Nov 15, 2017 at 7:33 AM Guru Chahal via cncf-toc <cncf-toc@...> wrote:

Similar functions have often been classified as "AAA" in traditional systems (Authentication, Authorization, Accounting). I agree that no box really captures these well today - the closest are likely 'coordination and service discover' or perhaps 'service management'. I'd imagine 'service management' is the the likely best current home... Istio is listed there as well today (most adjacent to these projects today). 

-Guru

On Wed, Nov 15, 2017 at 6:59 AM, Alexis Richardson via cncf-toc <cncf-toc@...> wrote:

That was where I was going...

Do others agree?

On Wed, Nov 15, 2017 at 2:58 PM, Nick Chase <nchase@...> wrote:

I think OPA belongs in the top layer but I don't think it fits in any of the existing subcategories.  In fact I feel that way about all three.

---- Nick

On Wednesday, November 15, 2017, Alexis Richardson via cncf-toc <cncf-toc@...> wrote:

All,

Question about the landscape.

https://raw.githubusercontent.com/cncf/landscape/master/landscape/CloudNativeLandscape_latest.jpg

- do we want to put OPA in the top layer, either inside, or next to App Def?

- what about identity - spiffe and spire?

- do we think key management should move to top layer?

a

_______________________________________________
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

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

+1 to this framing, particularly to its cross-cutting nature. While I agree 'security' is a natural starting bucket, the value propositions these (and other) projects address go beyond this (over time).

Visually, perhaps the TOC should consider a "AAA" box (or something more elegantly worded) to the right (or left) of 'Service Management'?

---

SJ | sunil@... | Scytale & SPIFFE

On Wed, Nov 15, 2017 at 8:13 AM, Tim Hinrichs via cncf-toc <cncf-toc@...> wrote:

+1 to the Authentication (SPIFFE, spire), Authorization (OPA), Audit (?).  Classically these are part of Security, but there's no box for that.  

AAA is typically cross-cutting.  OPA, for example, has integrations with Kube (orchestration), Istio (app), Terraform (provisioning), AWS (cloud).

Tim

On Wed, Nov 15, 2017 at 7:33 AM Guru Chahal via cncf-toc <cncf-toc@...> wrote:

Similar functions have often been classified as "AAA" in traditional systems (Authentication, Authorization, Accounting). I agree that no box really captures these well today - the closest are likely 'coordination and service discover' or perhaps 'service management'. I'd imagine 'service management' is the the likely best current home... Istio is listed there as well today (most adjacent to these projects today). 

-Guru

On Wed, Nov 15, 2017 at 6:59 AM, Alexis Richardson via cncf-toc <cncf-toc@...> wrote:

That was where I was going...

Do others agree?

On Wed, Nov 15, 2017 at 2:58 PM, Nick Chase <nchase@...> wrote:

I think OPA belongs in the top layer but I don't think it fits in any of the existing subcategories.  In fact I feel that way about all three.

---- Nick

On Wednesday, November 15, 2017, Alexis Richardson via cncf-toc <cncf-toc@...> wrote:

All,

Question about the landscape.

https://raw.githubusercontent.com/cncf/landscape/master/landscape/CloudNativeLandscape_latest.jpg

- do we want to put OPA in the top layer, either inside, or next to App Def?

- what about identity - spiffe and spire?

- do we think key management should move to top layer?

a

_______________________________________________
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

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