From 48d41e821b0a89615eaa3d2c06ff0664341069c4 Mon Sep 17 00:00:00 2001 From: Leif Johansson Date: Tue, 15 Oct 2013 13:59:22 +0200 Subject: [PATCH] docs fixes --- docs/cosmos-puppet-ops.mkd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/cosmos-puppet-ops.mkd b/docs/cosmos-puppet-ops.mkd index 7eb7c4a..023c52c 100644 --- a/docs/cosmos-puppet-ops.mkd +++ b/docs/cosmos-puppet-ops.mkd @@ -24,7 +24,7 @@ are easier to achieve using puppet than with cosmos alone. Consistency ----------- -Changes should be applied atomically across multiple system components on multiple +Changes should be applied atomically (locally on each host) across multiple system components on multiple physical and logical hosts (aka system state). The change mechanism should permit verification of state consistency and all modifications should be idempotents, i.e the same operation performend twice on the same system state should not in itself cause a problem. @@ -91,7 +91,7 @@ in multiverse. Instead 'fabric' is used to provide a simple way to loop over sub the hosts in a managed domain. Private data (eg system credentials, application passwords, or private keys) are encrypted -to a master host PGP key before stored in the cosmos repo. +to a master host-specific PGP key before stored in the cosmos repo. System state can be tied to classes used to classify systems into roles (eg "database server" or "webserver"). System classes can be assigned by regular expressions on the fqdn (eg all