The pattern for a playbook can be dictated inside the playbook file.

However, it would be nice to write patterns that could be applied when desired, especially for when bringing up new cloud instances. Make it possible to pass --hosts into playbook to override the pattern for each and every play in the playbook.

regression, should include results for just one host each

standardize a function for parse_kv, and include it where needed, same for parse_str, exit_with_json, etc.

Make things less scripty

this way, it would be possible to use variables as parameters to things like the poll interval

make install should not require a2x usage, nor should RPM build

causes issues on some RHEL 6 builds, not so much of a problem on CentOS

also remove from RPM build requires

things that are from utils should say "utils.foo", etc.

Same for "errors"

would just automate the combo of copy+shell , which is already possible, down to one command. Should be doable entirely in Runner as a virtual module with no actual module needed.

we don't want to be a script driven system but might as well make this as easy as possible for when someone is doing deployments and needs to fire off a DB upgrade, etc.

Need async wrapper to daemonize better?

See email to list.

$ sudo make install
a2x -D docs/man/man1/ -d manpage -f manpage docs/man/man1/ansible.1.asciidoc
a2x: ERROR: xmllint --nonet --noout --valid /Users/nocturnal/Development/homebrew/ansible/docs/man/man1/ansible.1.xml returned non-zero exit status 4
make: *** [docs/man/man1/ansible.1] Error 1
$ sudo xmllint --noent --noout --valid /Users/nocturnal/Development/homebrew/ansible/docs/man/man1/ansible.1.xml

On Mac OS X Lion 10.7.3, it used to work before the last git pull.

Lots of room for cleanup, some stuff belongs in utils

permissions
ownership

do it

remote login address, username + password constant

cache result (?)

less cobbler API calls

all the prune host stuff is getting kind of evil, should move lots of things into utils also

chaoslemur should return ok sometimes, failure sometimes, nothing sometimes, and invalid JSON sometimes, so that you can load up your system with lots of duplicate host aliase and check that failed hosts get filtered out and reported on correctly.

we do not have ship chaoslemur but it would be very useful for testing.

theoretical support of seperate alternative transport should be easily doable, make paramiko remain the default

rst files == website data

asciidoc == manpage, include all current command line options

consider deleting ansible-playbook (5) and just redirecting to Wiki

comparison can go on rst files

for service, 'running' is a valid state, but 'started' should also be, because 'restarted' is one and it's easy to type the wrong thing

for 'file', 'present' should probably be legal for people who are trying to do puppet things. in fact, most state names should take the puppet values even if we don't take all the various flags (because we're simpler, etc)

Ignore host entries starting with "#"

would be nice?

It seems the setup module needs to shell quote but does not, so parameters that are long strings can confuse the setup module.

if we accept the patch that makes arguments come from files (not the command line), create a scripts script to make testing them via the command line (outside of ansible) trivial.

include this in the module development guide

<tbielawa>@(deepfryer)[~/Projects/ansible] 12:25:01  (master) 
$ make install
...
running install_lib
creating /usr/lib/python2.7/site-packages/ansible
error: could not create '/usr/lib/python2.7/site-packages/ansible': Permission denied
make: *** [install] Error 1

Whoops!

This will help if some module returns Failed=False, which it shouldn't, but could be a common form of user error

slows things down a lot because it's called a ton.

consider using environment variable or something to set default?

See ML thread

also clarify var usage in examples/ files

allegedly filters out unsafe API calls in templates

Maybe something we want for the default as I think templates should only be good for variables anyway

example: if X is in the variables, do this

also should probably include previous command results in those vars

- name: blah
action: foo
if: x equal 3

- name: blah
action: foo
if: x like bar

ETC ETC ETC

on task notify, no event seems to be called in tests when a notifer is started ...

and we also should pass the successful results to the on_ok handler (which probably is called).

we can test all these via TestPlaybooks.py

so vars don't have to be shared with the public

also write a cobbler plugin for the contrib repo where the profile is named after the group. maybe.

Would make many modules, especially bash modules, much easier to write.

...

make some common functions (optionally) insertable into each module prior to xfer.

{{ ANSIBLE_QUICKSTART }}

also includes required python imports

parse_kv_args() -> dict

parse_string_args() -> string

require_fields(dict)

exit_with_json(dict) -> prints and calls sys.exit()

make it happen

"No such module echo" if you forget "shell echo" or "command echo" ... verify and improve this error msg

results could be large