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.

yes I do think that network and a couple of other things are, ideally, pluggable in each platform.

Of course they start with one of the major monolithic solutions in this space, k8s, mesos, docker dc. However, they are working with different networking, monitoring, service r&d solutions. Is

I find that startling. Are you sure they are not just creating integration points around the 'edge' of Kubernetes or Docker Data Center or ...

I'm referring mostly to large enterprises. Alan

Alan, Thank-you. "anyone assembling a container management solution (orchestrator, control plane etc.) and anyone attempting to build a functional component that would fit within that architecture.

I think this goes back to what is the charter of the CNCF. Taking a few short cuts in this narrative and avoiding some of the politics. Containers became mainstream when docker "standardized"

All, Here is a slightly cleaned up version of the "projects and products" data that I mentioned. It is also a cloud native market landscape. Ken and I used this to inform our initial thinking on the

Alexis, I think the new picture is fine to show things at a very high level (e.g. IaaS at the bottom, PaaS and SaaS are higher up, etc.) but I think most of my conversations will very quickly get

Hi all, Yesterday we had our 2nd discussion about the 'marketecture' stack that Ken and I put out. One piece of feedback, from Doug Davis by email, and then eg from Alan Conley on the call, was that

Hi all, There was some interest in talking with people who work on Minio. I have copied Anand "AB" Periasamy, with whom I spoke on Tuesday. AB, On the TOC call yesterday, I introduced the idea of

hi all, there was a fun convo on slack yesterday, that I thought it might be of interest to the mailing list.... a Kit Abstract question: if one were to 'check' a source project for cloud-nativeness