Cloud Foundry deploys application containers on so-called Diego cells.
Each Diego cell runs a number of application containers and exposes the applications through random ports on the Diego cell.
This blog post shows some very useful debugging and analysis tricks for Diego.
First, we determine the Cloud Foundry app belonging to a Diego container and second, we locate the containers for a specific application URL using the cfdot command line utility.
Running open-source Cloud Foundry is a challenging task.
Compared to vendor-distilled distributions deploying open-source Cloud Foundry requires in-depth knowledge of BOSH and Cloud Foundry itself.
This blog post shows solutions to typical operations topics when taking open-source Cloud Foundry to production and gives an overview of what it takes to run the Cloud Foundry core itself.
Automated installation of buildpack with concourse is easy.
In enterprise environment you might not want to install all buildpacks directly in production.
This blog post shows you how developers can test their application before the buildpacks are in production and you are still up to date.
Concourse is a highly versatile continuous-thing-doer.
At mimacom, we use Concourse a lot to automate Cloud Foundry deployments and naturally, when there is Cloud Foundry there is also BOSH as underlying deployment automation.
Concourse has different deployment options, of which one is a BOSH deployment.
In this blog post we will walk through how to prepare and setup a Concourse BOSH deployment.
We planned to upgraded a PCF installation from 1.9 to 1.12 in less than 72 hours.
During the upgrade we learned a lot.
In this blog post it is described what you can learn and which tools we suggest.
In addition, you can learn from our challanges during the upgrade with several redis nodes and the new relic service broker.