Posts by: GeoffFranks

If you’ve ever deployed Cloud Foundry via BOSH, you know how complicated BOSH’s deployment manifests can be – thousands of lines, many properties, many of which are repeated. This problem gets compounded when you start to host multiple copies of your BOSH deployments, such as for a sandbox, preproduction, and prod environment. Many of these

It’s been a while since we last blogged about spruce, and since then, a lot of things have changed. Here’s a quick summary of the spruce operators, and new features as of Spruce 1.4.2: play.spruce.cf Want a playground to easily experiment with spruce operators, or debug/track down/report a bug? Check out http://play.spruce.cf. Params The ((

Stark & Wayne’s Homebrew tap has been around for a little while, with only spruce. We’ve added a couple new things today to make life easier with managing deployments and credentials, safe, and genesis. Safe safe is a wrapper around Vault, written by James Hunt. It offers a lot of niceties to pick up where

logsearch-boshrelease is pretty cool, when it’s working. This is pretty easy to manage at a small scale, but as your deployment scales out, and you start processing multiple millions of records every few minutes, you might run into some issues. Below are some of the most common issues we’ve run into, and how we resolved

There are a lot of CloudFoundry services + service brokers available as BOSH releases. Many of those have errands for registering the service broker with CloudFoundry. Unfortunately some of them don’t, and some organizations might have version restrictions on the services that leave the broker-registrar errand slightly out of reach. This is where broker-registrar-boshrelease comes

I recently had the misfortune of having my bosh-lite instance keel over with 80% packet loss (or higher). Turns out, I was suffering from a routing loop. Here’s how to see if you’re suffering from it, too. Disable any routes for 10.244.x.x to 192.168.50.4 If you have configured any routes to send traffic to 10.244.x.x

If you’ve been in the BOSH/CloudFoundry community for more than 10 minutes, you’ve probably heard of, seen and even used spiff. But, if you haven’t heard of it, Spiff helps to make BOSH manifests easier to manage by merging smaller template files with environment specific template files to get the final manifest. Unfortunately, Spiff has

Let’s take an the cf-secrets.yml file from cf-boshworkspace, and see if we can convert it from a spiff based template to a spruce based template. The original file is pretty big, so for simpliticy’s sake, lets strip it down to just this: meta: admin_secret: (( merge || c1oudc0wc1oudc0w )) secret: (( merge || defaults.secret ))

At long last, kibana-me-logs now has an authentication layer, to keep your logs protected from prying eyes. To make use of it, just follow these simple instructions: # Grab the latest kibana-me-logs code cd kibana-me-logs git pull origin master # Set the env variables for auth cf set-env KIBANA_USER my_username cf set-env KIBANA_PASSWORD my_password #