update todos - WARNING: TODO IS almost EMPTY

Signed-off-by: Nico Schottelius <nico@kr.ethz.ch>
This commit is contained in:
Nico Schottelius 2011-03-21 14:46:15 +01:00
parent 70f2d1040f
commit 9ae1026dc4
4 changed files with 21 additions and 21 deletions

View file

@ -1,18 +0,0 @@
Assume you want to configure stuff one host ("monitor node"),
depending on the configuration of other hosts ("cluster nodes").
For instance, the monitor host would like to know,
which hosts are configured with the provider
"apache" and option --start true.
This requires the monitor node to be able to
query all other configured nodes. It can't
ask for all hosts, because cdist does not
know which hosts are configured or may exist.
Example implementation
If cdist keeps ("caches") the configuration of every
node it configures, each new node can query the
cache for existing nodes that acquired the given
configuration.

View file

View file

@ -0,0 +1,2 @@
- think about using .cdist for meta information?
- otherwise: parameter, gencode-local, etc. are not valid object id stuff

View file

@ -1,6 +1,22 @@
Core: Cache:
- think about using .cdist for meta information? Assume you want to configure stuff one host ("monitor node"),
- otherwise: parameter, gencode-local, etc. are not valid object id stuff depending on the configuration of other hosts ("cluster nodes").
For instance, the monitor host would like to know,
which hosts are configured with the provider
"apache" and option --start true.
This requires the monitor node to be able to
query all other configured nodes. It can't
ask for all hosts, because cdist does not
know which hosts are configured or may exist.
Example implementation
If cdist keeps ("caches") the configuration of every
node it configures, each new node can query the
cache for existing nodes that acquired the given
configuration.
Types to be written/extended: Types to be written/extended:
- __ssh-keys (host/user) - __ssh-keys (host/user)