andrew/disco
Archived
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

more readme

Browse Source
This commit is contained in:
Andrew Kesterson
2012-08-05 21:54:20 -04:00
parent e95fb5a461
commit 934d6fae18
1 changed files with 36 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
README.md
View File

@@ -92,18 +92,20 @@ operation, and is accessible as a filesystem tree (or the disco-param command wh
bash wrapper). These parameters appear in /var/disco/parameters on the client and server, and
default values can be found there in the client/server install before the first run of the client.
/disco/client/cmds/rsync : The rsync command to use when synching files. The source and destination
paths will be appended directly to this string.
/disco/client/cmds/rsync : The rsync command to use when synching
files.
/disco/server/uri : The rsync URI from which to fetch module definitions.
/disco/NODE_NAME/modules : This list defines the modules to install on a given node.
/disco/NODE_NAME/parameters : This tree defines all configuration parameters for the node not related to
any module in particular.
/disco/NODE_NAME/modules : This list defines the modules to install
on a given node.
/disco/NODE_NAME/parameters : This tree defines all configuration
parameters for the node not related to any module in particular.
Some special parameters are provided to the client, that do not exist on the paramters tree until
runtime:
/disco/NODE_NAME/current_module : This parameter defines the full name of the current module, such that
a module definition file can access its personal parameters via without knowing its name, e.g.:
/disco/NODE_NAME/current_module : This parameter defines the full
name of the current module, such that a module definition file
can access its personal parameters via without knowing its name, e.g.:
$(disco-param get /classes/$(disco-param get /current_module)/some/module/specific/path)
How to deploy stuff
@@ -155,7 +157,7 @@ Module Layout
A disco module (also called a "disco ball" for fun) looks like this:
MODULE
├── defs
├__ defs
│__ ├── files
│__ ├── scripts
│__ └── templates
@@ -193,10 +195,10 @@ MODULE/defs/scripts
=====
This file simply lists the (local) location of commands to execute, for this module, once all scripts have
been fetched, and all templates have been interpolated. They are executed, in order. One script failing
will not stop other scripts from failing unless told to do so in the MODULE/defs/options parameters tree
via the "disco/client/module/halt_on_failure" option. Otherwise, errors are reported, but all scripts will
be executed regardless.
been fetched, and all templates have been interpolated. The scripts cannot accept arguments. They are
executed, in order. One script failing will not stop other scripts from failing unless told to do so in the
/MODULE_NAME/halt_on_failure parameter. Otherwise, errors are reported, but all scripts will be executed
regardless.
MODULE/defs/parameters
=====