pedro/cdist
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

rephrase features

Browse source 
Signed-off-by: Nico Schottelius <nico@kr.ethz.ch>
This commit is contained in:
Nico Schottelius 2011-03-26 00:07:23 +01:00
parent 38a9c5d60f
commit 2a0cba4e4b
1 changed files with 19 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

32
README
View file

@ -52,22 +52,28 @@ You can [browse the documentation for the latest version online](man) as well.
### Features ### Features
Stuff that should probably be included in every configuration management, * Elegant code and clean design
but is not. Or: Why I began to write cdist: * Type and core cleanly seperated
* Small codebase in core
* Speed
* Elegant code
* Clean design
* Good documentation (man pages) * Good documentation (man pages)
* Meaningful error messages
* The no surprise factor
* Consistency in behaviour, naming and documentation * Consistency in behaviour, naming and documentation
* Meaningful error messages
* Either standard error messages from tools or added description for clearification
* The no surprise factor
* No magic guessing of what the user wants
* Simple and well-known DSL
* Posix shell
* Easy integration into bare metal installations * Easy integration into bare metal installations
* Simple and well-known DSL: posix shell * requires only ssh + sh
* It must be very easy to extend and debug cdist * Easy upgrade
* Focus on reuse of existing functionality (like sh, ssh, find, rm, ...) * ***There is no need to update cdist on target hosts!***
* Easy upgrade: ***There is no need to update cdist on target hosts!*** * cdist only needs to be updated on the master server(s)
* cdist only needs to be update on the master server * Very easy to extend
* Can be done via types, which can be stacked on top of others
* Reuse of existing functionality
* sh, ssh, find, rm, mv, ...
* Very easy to debug
* Just add set -x in the scripts
### OS support ### OS support