The fluentd project presented at today's TOC meeting: http://www.fluentd.org/ See slides

Hi all This week we have the privilege of no less than THREE project "intro presentations". They dominate the agenda, and the full hour will likely be

Noted!

In addition to definitions of "Incubation" status and benefits, it would be good to know what it takes to progress to a full acceptance.

Doug Agreed - I shall add this to the agenda for this week, so that we can have a vote soon. a

Alexis, per the charter [1], in section 9, it says: All such contributions should meet a set criteria created by the TOC and ratified by the Governing Board. I would suggest that the TOC

Hi all, As we talk to more projects, a consistent proposals process is emerging. I'd like to describe how this is working now, with a view to the TOC blessing the model. After this, let's ask Dan's

It's too bad we are not getting one in a piece like this.. Perfect example of the value proposition I've proposed we pursue for CNCF in the CNCF Vision Document. Unfortunate that nobody seems to want

interesting to see minio get a shout here - https://cloudplatform.googleblog.com/2016/07/how-to-escape-lock-in-with-a-multi-cloud-stack.html looking forward to hearing who is actually using it!

Please submit your proposals! http://events.linuxfoundation.org/events/cloudnativecon/program/cfp http://events.linuxfoundation.org/events/kubecon/program/cfp CFP Open: May 9, 2016 CFP Close: August

No worries…let me try to confirm my understanding. You’re saying there is a control plane for cloud native infrastructure (includes the fabric you reference below) and a control plane for

A quick test of the cncf-toc mailing list to confirm email forwards. Thanks!

Thanks Mark, got what you meant so apologies for not being clear. My primary point is that their are two separate and distinct paths which each exhibit the model-view-control reference pattern - one

By data plane, I meant the application data flow itself: code, runtime, OS, app data storage, app data connectivity (i.e., networking). Models and policy are important aspects that can blur lines

Would you consider “model” and control planes? It would be inclusive of “data” but also accommodates a larger context. Also, can we endeavor to capture the nano-segmentation aspects of

Thanks sir, I’m working with several POC participants to illustrate this stack with the intent of offering it up to our team here as a working example. It also shows the Eli Whitney aspects

Using the airport analogy, airplanes and airports are an orthogonal to air traffic control, baggage routing, etc. Back to our world, it's the difference between data and control planes. I'd

i actually like how you think about this Doug. it is a great flag on the hill. but can it work? complete freedom for components combined with app dev productivity.

Any thoughts folks?

The approach I've been taking on this has been from a slightly different perspective. Most definitions have started with the infrastructure and I'm starting from the application and working backwards.