all, post the Tahoe f2f we agreed to run with a more "open agenda" for TOC calls. PLEASE feel free to post topics to this thread over next 24 hours, and I'll work with Chris A to devise an Agenda

CNCF will be sponsoring and helping to program content for the events below. We would encourage you to have engineers from your companies propose talks on Kubernetes and other cloud native related

Alex, I agree with Clinton’s point that we want to focus on what makes Cloud-Native different, not sure covering all the legacy Storage protocols serves that purpose There are too many users

Clinton / Yaron, Thank you for the feedback. We will get some of that added to the doc, although we were thinking of covering some of those topics in more depth in future articles. We’ll

If you are interested in hearing about the progress of the CI working group, I am planning on using the CI mailing list for public discussion. Please join that mailing list,

Alex, Sorry for the late review. My concern currently is that the document spends 80% of the time talking about what is known about some storage platforms today and the last portion discussing what

I wrote a post a while ago on impact of Cloud-Native on Storage, can reuse its content, you may want to take the abstraction to the next level just like we did on compute (from VMs to

Hi, We have prepared the content for the first topic in the list (albeit a little later than we hoped for). This is the first doc we have produced and is meant to serve as an overview of storage

All, An agenda item for the TOC f2f was the possible formation of "working groups". These have come up a number of times in the last 9+ months since the TOC formed. The idea is to spawn CNCF TOC

Andy, thanks, sure we should follow w “How” after the “Why” Another reason for that order is to set the architecture context, e.g. many still view containers as lightweight VMs, can see

I agree the emphasis of our outbound messaging should be on the why (and the "what's in it for me?"). And Yaron's suggestion of "because it gets you business agility through continuous dev and ops")

If anyone care to watch Simon’s talk pointed by Tony: "people don't buyWHAT you do, but WHY you do it", Containers, micro-services, .. are thewhat, my point is we should focus on the Why i.e.

I agree with some earlier comments about being too opinionated. A broad definition could be "a computing environment focused on optimizing for applications in cloud operating models". This feels like

+1 That's very concrete, and provides a framework for explaining what and why.

+1 for Thursdays at the same time. - Lee

As a big fan of Joe Beta and Craig McLuckie, my three ingredients for cloud-native operations are containers, orchestrators and microservice frameworks. These three terms come from Craig's post

I think the key message of Cloud-Native should be about its value: Continuous Development and Operation (Enabling Business Agility/Transformation) Decomposition to micro-services, stateless,

Management includes scaling, so IMO "dynamically managed" implies dynamic scaling, as well as a higher rate of change than people had been accustomed to in the past. In practice, the way this is

+1 (non-binding) Regards, Tony Hsu

Either works for me -- Nicholas Weaver Director - Software Engineering Intel, Datacenter Solutions Group From: <cncf-toc-bounces@...> on behalf of Camille Fournier via cncf-toc