Tag Archives: etcd

From the Interns: Introducing SHIELD etcd Plugin

This guest post is brought to you by our four Summer 2019 Interns, Jason Zhou, Naveed Ahmad, Pururva Lakkad, and Sriniketh Varma Dasarraju. We spent the summer over at Stark & Wayne designing and building the etcd plugin for SHIELD. The basic functionalities include backing up data from etcd and then restoring this data to

Cloud Foundry service broker for CoreOS etcd

We have been big fans of CoreOS etcd since it first came out. A simple to use distributed key value store. Many of our own distributed systems built for customers have used etcd for coordination of components. Cloud Foundry itself has used Etcd for many years. Whilst there is a wonderfully maintained etcd release for

ETCD Gets Knocked Down and it Gets Up Again

You are never gonna keep it down Purple Rain got you down? Monit thrashing etcd? Just want to know if ETCD is healthy in your Cloud Foundry deployment? Checking Health Start by getting the list of etcd servers in your CF deployment: bosh vms <your deployment> | grep etc Adjust the following script for your

Configuring etcd.cluster Job Property in Cloud Foundry

A few new job properties were added to the etcd bosh release. One of these is etcd.cluster and reading the spec file you get the helpful hint that it is to represent Information about etcd cluster. So what is this job property supposed to be set to? After a bit of trial and error and

Adding Certs to Cloud Foundry Deployments

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

Detect ETCD Split Brain for Cloud Foundry

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