Cloud Foundry on mcclain.sh

Hacking on Cloud Foundry's Gorouter

Mon, 12 May 2014 00:00:00 +0000

Late last week, a couple colleagues and myself discovered a small bug in Cloud Foundry’s gorouter in which a websocket upgrade was not completed if a comma-separated list of values in the Connection header was provided. A pull request was pieced together, submitted and is currently being looked at by Pivotal. However, I figured, why let the learning stop there?

There were several things that I was unfamiliar with:

Cloud Foundry the API Way

Thu, 05 Sep 2013 00:00:00 +0000

This is a topic I’ve seen come up a couple times in the last few weeks. It started with Dr. Nic Williams when we were discussing share-my-cloudfoundry when he wanted to provide compatibility with Cloud Foundry v1 and v2 in the same application. This situation came up again with a personal project that I will detail later.

It required a bit of discussion, but I finally tracked down the answers. Although the cfoundry gem states that it is compatible with Cloud Foundry v1 and v2, after some digging, it looks like it’s only compatible with v2. To make things a bit more complicated, even though the old cfoundry library was moved to a separate repository, it retained the “cfoundry” gem name, meaning I could not include both gems in a single Gemfile.

Cloud Foundry v2: What's New?

Fri, 14 Jun 2013 00:00:00 +0000

I’ve mentioned Cloud Foundry v2 a few times before (here, here, and here), but I wanted to really get my hands dirty with the new bits and pieces before I wrote about it. Andy Piper wrote about CFv2 a bit on his blog, in which he outlines the major features to users of CF. I wanted to dig a bit deeper into the major changes in some of the components that make up CFv2.

Buildpacks in Cloud Foundry v2

Thu, 16 May 2013 00:00:00 +0000

NOTE: The referenced tweet has since been deleted

The above tweet summarizes a very productive and exciting lunch I had today, in which after getting CF v2 working last night thanks to nise_bosh, I started reading about buildpacks.

To summarize buildpacks, taken straight from the Cloud Foundry documentation…

Buildpacks are a convenient way of packaging framework and/or runtime support for your application. For example, Cloud Foundry doesn’t support Django or Python by default. Using a buildpack for Python and Django would allow you to add support for these at the deployment stage.