update TODO with ideas for playbook and latest plans
This commit is contained in:
parent
e25bb2f888
commit
6bfc275204
1 changed files with 30 additions and 6 deletions
36
TODO.md
36
TODO.md
|
@ -1,14 +1,38 @@
|
||||||
TODO list and plans
|
TODO list and plans
|
||||||
===================
|
===================
|
||||||
|
|
||||||
|
Playbook TODO:
|
||||||
|
|
||||||
|
* error codes and failure summaries
|
||||||
|
* create modules that return 'changed' attributes
|
||||||
|
* fail nodes on errors, i.e. remove from host list, rather than continuing to pound them
|
||||||
|
* further improve output
|
||||||
|
* more conditional capability
|
||||||
|
* very good logging
|
||||||
|
|
||||||
|
General:
|
||||||
|
|
||||||
|
* logging
|
||||||
|
* async options
|
||||||
* modules for users, groups, and files, using puppet style ensure mechanics
|
* modules for users, groups, and files, using puppet style ensure mechanics
|
||||||
|
* very simple option constructing/parsing for modules
|
||||||
|
* templating module (how might this work syntax wise?) with facter/ohai awareness
|
||||||
|
* probably could lay down a values.json file
|
||||||
|
* use copy capabilities to move files to tmp, run python templating
|
||||||
|
* maybe support templating engine of choice
|
||||||
|
* think about how to build idempotency guards around command module?
|
||||||
|
* think about how to feed extra JSON data onto system
|
||||||
|
|
||||||
|
Bonus utilities:
|
||||||
|
|
||||||
* ansible-inventory - gathering fact/hw info, storing in git, adding RSS
|
* ansible-inventory - gathering fact/hw info, storing in git, adding RSS
|
||||||
* ansible-slurp - recursively rsync file trees for each host
|
* ansible-slurp - recursively rsync file trees for each host
|
||||||
* very simple option constructing/parsing for modules
|
|
||||||
* Dead-simple declarative configuration management engine using
|
|
||||||
a runbook style recipe file, written in JSON or YAML
|
|
||||||
* maybe it's own fact engine, not required, that also feeds from facter
|
* maybe it's own fact engine, not required, that also feeds from facter
|
||||||
* add/remove/list hosts from the command line
|
|
||||||
* list available modules from command line
|
Not so interested really, but maybe:
|
||||||
* filter exclusion (run this only if fact is true/false)
|
|
||||||
|
* list available modules from command line
|
||||||
|
* add/remove/list hosts from the command line
|
||||||
|
* filter exclusion (run this only if fact is true/false)
|
||||||
|
-- should be doable with playbooks (i.e. not neccessary)
|
||||||
|
|
||||||
|
|
Loading…
Add table
Reference in a new issue