Tag : genesis
Photo by Michael Longmire on Unsplash Companies are looking for ways to cut costs and keep staff while offering the same level of service to their developers and customers. Hopefully, the suggestions below will help you identify a few opportunities to save money! There are a few ways operators can save money on Cloud Foundry
Genesis is an awesome deployment framework for deploying systems with BOSH to any infrastructure cloud. It has a whole catalog of open source production ready kits which make it super easy to deploy, scale, and upgrade systems such as Cloud Foundry Application Runtime (PaaS), Vault (Secrets), Concourse CI, SHIELD (backup/restore), and Minio (Object Store). Genesis
Photo by Victor Muñoz on Unsplash App Autoscaler is an add-on to Cloud Foundry to automatically scale the number of application instances based on CPU, memory, throughput, response time, and several other metrics. You can even add your own custom metrics as of v3.0.0. You decide which metrics you want to scale your app up
This month (August of 2019), we started holding regularly scheduled Roadmap Calls, where the developers and release engineers working on Genesis provide updates, explain where we are at in the roadmap, where we want to go, and answer questions form anyone who pops in. We’ll be holding these calls on the 3rd Tuesday of every
Locking down your BOSH VMs? Here’s a handy guide for some options at your disposal for overriding the default password for BOSH’s vcap user: Customize it in your manifest In each resource pool (or VM type) configuration in your BOSH manifest (or cloud config manifest), you can specify env.bosh.password. This will overwrite the value of
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
In this post, we’re going to use Genesis to deploy Cloud Foundry. We will make use of some of Genesis’s cool features to generate unique credentials for each deployment, and Vault to keep the credentials out of the saved manifests. We will do this on BOSH-Lite, but templates exist to easily deploy to AWS with
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