Posts by: Chris Weibel
Ever wonder how many of the VMS in AWS Console were deployed via BOSH? How about the number of instance types so you can start using reserved instances? The script below will show you the number of BOSH deployed VMS you have for each defined director on AWS. A few assumptions: You can log into
We recently added etcd TLS to several environments and leveraged the certificate creation scripts in cf-release/scripts. These are wonderful little scripts but leave it as an exercise to copy and paste in the contents of the flat files into your deployment manifest. After my second copy-pasta a colleague (thanks Tom) created a helpful script to
While upgrading one of the development environments we had a bad configuration of the etcd properties. This resulted in three etcd servers spinning up which each elected themselves as leader. To detect this condition look at the leader key on each etcd server. In the scenario below there are three etcd servers named: etcd_z1/0 etcd_z1/1
In the second part of configuring UAA with BOSH we’ll cover changes which are needed for Health Monitor which may not be obvious from the tutorial found at http://bosh.io/docs/director-users-uaa.html. Part I of this tutorial is here: https://www.starkandwayne.com//blog/bosh-uaa-with-signed-certificates/ Change Health Manager Authentication In your deployment manifest you should have the user and password defined similar to:
In a previous article (https://www.starkandwayne.com//blog/bosh-uaa-with-signed-certificates/) we discovered how to add a multiple/intermediate level signed certificates to UAA on BOSH. Recently I discovered one of my deployments had the certs in the wrong order and a kind gentleman named Thilak showed me how to verify the order of certificates is correct. While the bosh_cli didn’t complain
We ran into an interesting problem today while running bosh-init against AWS: CPI ‘has_vm’ method responded with error: CmdError{"type":"Unknown","message":"AWS was not able to validate the provided access credentials","ok_to_retry":false} This is a CPI error so after a bit of investigation confirmed our AWS keys were correct and valid with the awscli. After some more digging we
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
Cloud Foundry for Beginners: From Zero to Superhero Join us for a hands-on training workshop to learn about deploying and managing applications on Cloud Foundry. We will give an overview of Cloud Foundry and how it works, including specifics relating to services, buildpacks, and architecture. We will also look at how to effectively work with
To deploy Cloud Foundry (CF) to Bosh-Lite on AWS, we need to [Spin up a Bosh-Lite VM on AWS](##Spin up a Bosh-Lite VM on AWS) first, then we can [Deploy CF using the Bosh-Lite](##Deploy CF using the Bosh-Lite) we spun up. Spin up a Bosh-Lite VM on AWS Dr Nic wrote a blog Bosh-Lite can