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

All, Sorry I wasn't on the call today, traveling in Japan now (sorry I missed you here Chris!). I think an issue to highlight here is that we're running into very typical service provider things

I'm almost done with draft one of the periodic table of cloud native elements for you guys to throw rocks at. We should then align with ref arch Regards, Doug

To be clear. The cluster is open to all CNCF members. Submit the request as listed below, and the governance committee will respond and facilitate. Thank you, Jonathan Donaldson VP/GM, Software

I think it's important to ensure that we don't end up with projects scattered across multiple locations. The objective should always be to put all projects on the cluster. In my opinion, it's one of

I've proposed a "reference architecture" environment people could experience by "renting" time (at $0) to illustrate cloud native vs traditional virtualization approaches like openstack. Several of us

i sense a CNCF Cloud in the works ;-) Diane -- Kind Regards, Diane Mueller Director, Community Development Red Hat OpenShift @openshiftcommons We have more in Common than you know, learn more at

This would be very useful for the Docker developers as well! They would love to have access too, would that be ok?

yes it could