Blog
You can become a superhero of automation and development by learning and practicing. This is our blog from our learnings and practice.
We are consultants and trainers in Cloud Foundry, devops automation and continous delivery. We have the best jobs in the world helping you have the best job in the world.
The result of running bosh deploy might be unfortunately failing. The output will show which jobs (VMs) did not successfully run by the end of the timeout period. We can use the BOSH API to discover specifically which job template(s) are failing using trusty curl and jq: Setup environment variables: export bosh_target=https://10.58.111.45:25555 export bosh_username=admin export
At Stark & Wayne we are concerned with the complete lifecycle of deployments and simple upgrade paths are an important ingredient to any long running system. For users of the cf-containers-broker (a service broker that will let you run and bind services that live in docker containers) upgrading their services just got much simpler. By
Earlier today I logged into a jumpbox session and was greeted with some lovely error messages: $ channel 12: open failed: administratively prohibited: open failed channel 13: open failed: administratively prohibited: open failed channel 19: open failed: administratively prohibited: open failed channel 20: open failed: administratively prohibited: open failed channel 21: open failed: administratively prohibited:
In the development and release of Dingo S3 we developed a Concourse CI pipeline for building, uploading and installing Pivotal tiles. In this blog post I wanted to share some of the tools and APIs that we used. This is useful for all PCF/Ops Manager admins who can create their own pipelines or CI jobs
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
Within Cloud Foundry 2016, with Diego support enabled and the latest cf CLI you can now run one-off tasks natively in your Cloud Foundry. For Ruby on Rails applications this means you can run database migrations or seed the database from your local computer very easily. Conceptually you would run either: cf ssh <appname> cf
GitHub Releases are a great resource for open source projects to expand on the simple git tag concept. You can add release notes in Markdown format, and you can upload finalized assets – such as compiled executables. As a user I had the question – how do I script "download the latest release, please?" For
BOSH makes a whole lot of tasks in the operations / systemsmanagement space way easier than ever before. Combine that with tools like Spruce and Genesis, and you have a really powerful paradigm for managing your deployments. Pair that with Concourse and it seems like the sky is the limit! Then you run into the
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