Hacker News Reader

Comment by jacques_chester | Hacker News Reader

Since we're calling out OSS alternatives that the author missed, I'll point out Cloud Foundry. It solved the "rolling upgrade" problem years ago.

Currently you can run it on AWS, OpenStack or vSphere; Azure and GCE support are being worked in concert with Microsoft and Google respectively.

Disclaimer: I work for Pivotal, the company which donates the largest chunk of engineering effort to Cloud Foundry.

View on HN

We use open source CF to host > 1000 applications in my company. I have virtually zero complains from an operational point of view and the developers love it.

I wish more people would spend the time to look into it instead of just defaulting to Docker + tooling, just because.

Thanks for the reminder, I completely left out Cloud Foundry when I did my own search for this kind of tool.

I'll definitely have a look at it.

If you'd like any help, email me (see profile).

Actually, Azure is fully supported! Microsoft wrote the CPI adapter themselves.

FD: I work on Cloud Foundry

Why describe your contributions as a donation? There are paid Cloud Foundry hosting options, so it is in your company's best interest to make the system awesome.

There's a foundation that's a separate entity that owns the IP: https://www.cloudfoundry.org/membership/members/

As helloiamaperson said, the IP is owned by the Cloud Foundry Foundation. Pivotal has an interest in making Cloud Foundry awesome because we sell products and services based on it.

But IBM also has such an interest, so too HP and Fujitsu and NTT and Anynines and Intel and other members of the Foundation I've rudely neglected.

In a given team you can often find engineers from multiple companies. Or you'll find that different companies will provide a team. For example, the `cf` CLI was previously a Pivotal team, then a mixed Pivotal-IBM team, then an IBM team, now I believe Fujitsu are assigning engineers.

Voting rights in the Foundation are proportional to contributions, so it's in the interest of each participant to be generous in providing people, resources and IP. A defined high-level process, modelled after Pivotal's, is used to ensure a common approach to working on the platform -- pair programming, TDD, product management from a Tracker backlog and so forth. Every engineer goes through the same "dojo" onboarding.

I don't think anyone has ever tried anything quite like this before. At the corporate level it's press releases at twenty paces, but in the trenches it's a lot more seamless.

It solved the "rolling upgrade" problem years ago.

Did it?

For simplicity, http://deis.io should be preferred for modern "deploy-by-buildpack" architectures.

> Did it?

Strictly, BOSH solved it. But BOSH was originally written for Cloud Foundry, so through the fuzzy lens of distant history it looks the same.

In Pivotal we upgrade our public-facing Cloud Foundry installation, Pivotal Web Services, within a day or two of a new CF release being blessed. Typically nobody ever notices. Hundreds to thousands of VMs (I don't know how many we are running now) are upgraded to the most recent version of Cloud Foundry in a few hours and nobody notices.

Yeah. It's solved.

Reply on news.ycombinator.com