From 875cb565e36be8a686b78cf9eca83367d5b542b2 Mon Sep 17 00:00:00 2001 From: Rolf Neugebauer Date: Sat, 8 Apr 2017 09:31:36 +0100 Subject: [PATCH] demo: Update etcd README Signed-off-by: Rolf Neugebauer --- projects/demo/etcd/README.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/projects/demo/etcd/README.md b/projects/demo/etcd/README.md index 6f6f013b9..c4b5ade77 100644 --- a/projects/demo/etcd/README.md +++ b/projects/demo/etcd/README.md @@ -4,6 +4,9 @@ An `etcd` cluster can be bootstrapped in different ways (see the [Documentation] The moby `etcd` package is build with [build-pkg.sh](./build-pkg.sh). It takes the official `etcd` container and adds a [script](./etcd.sh) to start `etcd`. [etcd.sh](./etcd.sh) first attempts to join a new cluster. If that fails it attempts to join an existing cluster. Note, the number and members of the cluster are somewhat hard coded in the script. +Each node is also configured with a disk, which is mounted inside the +`etcd` container. `etcd` uses it to keep some state to help with +restarts. ## Preparation @@ -38,6 +41,9 @@ the nodes and then: docker run --rm -t quay.io/coreos/etcd:v3.1.5 etcdctl --endpoints http://192.168.65.200:2379 member list ``` +You can perform rolling updates, by for example, switching the kernel version in `etcd.yml`, build a new moby, e.g., `moby build -name etcd-4.10 etcd`, update `infrakit.json`, and then commit the new configuration to InfraKit: `infrakit group commit infrakit.json`. + + ## Infrakit GCP setup Note: This setup is somewhat specific to our GCP setup (IP addresses