remake: no --follow-strict-remakes; a strict remake failing says who

A strict remake takes a majority of members whose --strict-keys take
its manifest's signer: no node votes for one without, so
--follow-strict-remakes (1173) goes. A node that doesn't vote still
switches once the others commit, as with any remake.

So that an operator can tell why one fails: a strict remake aborted
for want of a majority (the voting period over, or a majority out of
reach) says in its reason (GET /admin/remakes/{id}, and the
coordinator's log) which members didn't vote, and that a member votes
for one only with its manifest signed by a key of its --strict-keys.
Each of those logs why itself (`Not voting for a strict remake`).

The sim a_strict_remake_too_few_take: only a takes the manifest; the
remake aborts, naming b and c.

1 files changed, 2 insertions, 6 deletions

diff --git a/docs/example.toml b/docs/example.toml
index 2c3a2ab..d5af848 100644
--- a/docs/example.toml
+++ b/docs/example.toml
@@ -107,14 +107,10 @@ htpasswd = "/etc/continuum/htpasswd"
 
 # SSH keys, as authorized_keys lines (ssh-ed25519 <base64> [comment]), whose signature
 # on a strict remake's manifest this node takes: the values kept when the swarm turns
-# strict (docs/access.md). Without, it votes for no strict remake, unless
-# follow-strict-remakes.
+# strict (docs/access.md). Without, it votes for no strict remake; a majority of the
+# members must take the manifest's signer for one to commit.
 # strict-keys = ["ssh-ed25519 AAAA… alice"]
 
-# Without strict-keys: vote for strict remakes all the same, taking the manifests as
-# the members proposing them sign them.
-# follow-strict-remakes = false
-
 # Where the reverse proxies whose user-header is believed connect from: IP addresses (or
 # ranges, as ADDRESS/BITS), and unix for the API's Unix sockets (bind-addr). On a host
 # with other users, leave out the addresses and have the proxy use a Unix socket: others