From 70884245b8e175f53e59a7f348b799aca6eac489 Mon Sep 17 00:00:00 2001
From: godog <godog@autistici.org>
Date: Sat, 21 Sep 2019 15:20:33 +0200
Subject: [PATCH] docs: add operating.md

---
 README.md         |  1 +
 docs/operating.md | 17 +++++++++++++++++
 2 files changed, 18 insertions(+)
 create mode 100644 docs/operating.md

diff --git a/README.md b/README.md
index b0a7d18a..50dd986b 100644
--- a/README.md
+++ b/README.md
@@ -73,6 +73,7 @@ and in README files for individual Ansible roles:
 * [Docker usage](roles/docker/README.md)
 * [CLI tool usage](docs/cli.md)
 * [Testing](docs/testing.md)
+* [Operating](docs/operating.md)
 
 ### Built-in services documentation
 
diff --git a/docs/operating.md b/docs/operating.md
new file mode 100644
index 00000000..c8779c6d
--- /dev/null
+++ b/docs/operating.md
@@ -0,0 +1,17 @@
+Operating float
+===============
+
+This document covers operational aspects of running float, and how
+these operations can impact users of the services.
+
+# Unreachable hosts
+
+Configurations that depend on data from *other* hosts (e.g. the vpn
+service *tinc* needs to know about all hosts) can diverge when some
+hosts cannot be reached by float.
+
+In this situation there's effectively a *partition* between the
+configurations: care must be applied to make sure that they still make
+sense and the service behaves correctly. Once the hosts are reachable
+again then the next float run will bring the configurations back in
+sync.
-- 
GitLab