IBMOTS

I'd say "complex" - the reality is that while they all achieve similar things, they do with different POVs

Cloud Foundry can support Docker and has embraced OCI's runC

CNCF has discussed value of CF's service broker APIs

lots of competing for developer resources, and often confusing the market about where they should invest in learning/adopting the technologies.

This is the exact area that I pointed out that we need harmonization within the community.

Mesos can host a variety of schedulers

it's turtles all the way down

none of them come with "built in operations" which is still a huge barrier to adoption. public cloud adoption of these technologies will help resolve that challenge (to some extent).

They are all influencing each other. Containers have been part of Cloud Foundry since 2011. Docker containers run on CF and CF runs on OpenStack.

This kind of points back to the other question about cooperation and competition in foundations https://www.crowdcha...

they complement each other in some respects and compete in others. I don't think there's a simple A vs. B type of rivalry.

Competition is essential for progress. Kubernetes is very different from Cloud Foundry but targets a similar audience. The two projects exert influence on each other as a result.

@bgracely Can you expand on that? What would “built in operations” look like in this context?

@sramji Just to say, before @bgracely responds, that I'm not sure you'd want built in ops. Having ops outboard allows more flexibility, especially in fast evolving areas. Look at the Hasicorp model, for instance, where the products are related, but fairly

@rjhintz (oops) fairly loosely coupled

the Developer will find the "signal from the noise". Devs run from marketing hype

Mesos is showing up as a platform for stateful services; that’s a complement to Cloud Foundry’s elastic runtime for applications, and CF also has BOSH - a platform for stateful services.

@sramji I mean that the new technology is all cool, but very few people know how to operate it, so adoption in private environments significantly lags adoption in public environments.

@IBMCloud It's text configuration files all the way down

@bgracely Well, a lot of projects come with batteries included. Yes, there's an awareness issue. Means CIOs need to actually make decisions.

The biggest barrier for most users is not choosing among the different orchestration choices, it's understanding orchestration itself and its implications. At least in my experience.

@bernardgolden I'd agree with this. There's a precursor step that the organization silos have to cooperate to achieve a common understanding

Also, some of the platforms assume a working Agile/CI system is in place so that they can properly operate. Most mainstream IT orgs are still struggling to get their arms around this process.

Of course, one can run one of these platforms with handcrafted containers created by a developer, but then one is orchestrating a hot mess.

@bernardgolden or having tests, appropriate tests, automated tests, fast feedback from testing, understanding blockers for CI...

@bernardgolden As you point out, there are two issues there - one is having a CI system, and the other is adapting your team and process to use it.

@sramji Right, you can't just overlay CI wonderfulness on a dysfunctional, siloed dev-->deploy process

We’re doing economic research on the impact of Cloud Foundry this year. It’s non-trivial to untangle.

McKinsey Global Institute and the MIT Institute for Digital Enterprise are doing great work in this area.

Cloud Foundry has provide a fabric for grand scale economic impact. Look at what IBM is doing with Waston Services in #IBMBluemix IBM's congnative strategy

Cloud Foundry has provided a fabric for grand scale economic impact. Look at what IBM is doing with Waston Services in #IBMBluemix, which are core toIBM's cognitive strategy

Another interesting project to watch is #Swagger wrt API documentation & standardization

@jeffborek True. Unfortunately they didn’t contribute the #Swagger trademark to the open source project, which is a serious concern.

@jeffborek So for now we should call it the “Open API Initiative” which is less catchy :) https://openapis.org

@JerryCuomo Cloud Foundry in #IBMBluemix has been critical to our Mobile services as well, like ibm presence insights

Foundations are growing in popularity as a way to manage collaboration and competition. They provide stability in the middle of wild markets like containers.

Loved the "role of the foundation" podcast from @christo4ferris & @CloudOfCaroline -> bit.ly/1QHL4Bb

There will be more of that talk at Interconnect on @duncanjw’s panel

it's still a mixed scorecard on foundations. Linux and Cloud Foundry have done well recently, but OpenStack and some others less so. All depends on how much vendors dictate the agenda vs. community-driven goals.

We’re definitely seeing interop and execution at the same time. Not just in Cloud Foundry, but in CNCF and OCI - look at Docker and CoreOS.

"Are we headed for Foundation Fatigue" is going to be a GREAT #ibminterconnect panel w/ @sramji @tcrawford @e_monty @duncanjw

inter-dependencies and conflicts between projects is a complex fabric - I really like when I see collaboration

@sramji which is a sign of a healthy ecosystem. it's great to see the breadth of contributions and still see the competition

With #blockchain foundation members also provide a venue for readiness... we all will make sure that an open ledger is ready for 100 years of transactions!

It’s funny, we use the word “ecosystem” which we borrow from biology and perhaps think it means “peaceful”. Ecosystems in nature are quite violent. @d_lindquist

at #ibminterconnect we are going to breakdown the new linux #blockchain project and demo blockchain on @IBMCloud

@sramji but they achieve equilibrium for extended periods

@sramji agreed. people sweep "coopetition" under the rug as if it's a peaceful co-existence. it adds a 50% tax to all partnerships and interactions.

@christo4ferris Yes… after the expansion and die-off phases!

@bgracely Linux Foundation dropping community representation seems a step backwards