Blog

Pivotal has done a great job with documenting adding UAA as the authentication and authorization for BOSH instead of relying on local BOSH accounts. This allows you to later integrate with LDAP or SAML later on. The instructions have you generate a series of unsigned certs which works great except now you have to use

This post serves a specific purpose — to take Cloud Foundry’s new runtime environment, break it down into parts that hopefully make it a bit easier to understand. Diego was, for me, something that seemed a bit obscure until I dug into its vitals. I found the documentation gave me something of an idea of

I was working on an application, which talks to a few API’s to set up a lab environment on a system I’m working on. This system happens to be using Cloud Foundry to not only host its UI, but also its underlying API’s. The API’s I’m using in this case, while the source code is

I am lucky to have the opportunity to work at Stark & Wayne while earning my PhD in Computer Science and Engineering at the University at Buffalo. Stark & Wayne has lots of customers using Cloud Foundry, including GE, Intel, Swisscom, Zipcar, SAP and others. I myself have been working on various Pivotal Cloud Foundry

So you have your local BOSH-Lite, and you have your Cloud Foundry release on there, your Etcd, PostgreSQL, MySQL, Redis. You name it; it’s on there. Then you go and install the latest MacOS update and "Oh Gods, no!", You forgot to suspend that Vagrant instance, and you might be looking at an aborted state

bosh create-env is AWESOME. It lets you deploy BOSH itself using a BOSH manifest, making it really easy to customize your BOSH deployment as you see fit. It allows you to add a backup agent, some monitoring, and some troubleshooting tools, or even swap out the database with an HA alternative. However, there is one

At Stark & Wayne, we love Concourse pipelines! We use them for testing/releasing CLI utilities, deploying Cloud Foundry apps, building docker images, creating and testing BOSH releases, and vetting changes to BOSH deployments in an automated fashion starting in sandbox environments all the way to production. Uh-oh! credentials.yml file got committed? One of the most

A few of our recent posts related to standing up BOSH deployments using Genesis have all revolved around needing Vault to store your credentials safely. The vault-boshrelease makes this fairly straightforward, but there’s now a Genesis Vault template to make running Vault even easier! The procedure is similar to the other Genesis deployments: $ genesis

Using Cloud Config enables you to remove a lot out of your BOSH manifests to simplify them. However, it’s an all-or-nothing approach. You either use it for all your deployments on a director, or none. When Concourse CI hit the magic 1.0.0, they switched over to using a lot of the BOSH 2.0 features, including