Fedora Infrastructure Ansible Repository
Find a file
2012-11-01 15:29:53 +00:00
action_plugins fix up the plugin and the playbook 2012-10-30 22:31:53 +00:00
files add ansible admin ssh key to sysadmin-main key list 2012-10-24 21:26:54 +00:00
handlers bring in and alphabetize all the normal services we would need to restart 2012-10-17 19:54:24 +00:00
inventory - add toshio's auth-keys-from-fas script to ansible public 2012-10-26 17:19:47 +00:00
library add add_host plugin and module to local ansible tree for use until 0.9 is out 2012-10-30 21:55:42 +00:00
playbooks change the default size to c1.medium 2012-10-31 05:25:15 +00:00
scripts update readme with actual invocation 2012-11-01 15:29:53 +00:00
tasks fix typo 2012-10-31 04:29:10 +00:00
vars silly python-ish vars 2012-10-26 17:24:31 +00:00
README slightly more docs 2012-10-31 15:40:57 +00:00
TODO first commit to the ansible public repo 2012-10-08 19:35:54 +00:00

ansible repository/structure

files - files and templates for use in playbooks/tasks
      - subdirs for specific tasks/dirs highly recommended

inventory - where the inventory and additional vars is stored

library - library of custom local ansible modules

playbooks - collections of plays we want to run on systems

tasks - snippets of tasks that should be included in plays


public path for everything is:

 /srv/web/infra/ansible

private path - which is sysadmin-main accessible only is:

 /srv/private/ansible


In general to run any ansible playbook you will want to run:

sudo -i ansible-playbook /path/to/playbook.yml



cloud instances:
to startup a new cloud instance and configure for basic server use run (as
root):

el6:
sudo -i ansible-playbook /srv/web/infra/ansible/playbooks/el6-temp-instance.yml

f17: 
sudo -i ansible-playbook /srv/web/infra/ansible/playbooks/f17-temp-instance.yml


The -i is important - ansible's tools need access to root's sshagent as well
as the cloud credentials to run the above playbooks successfully.

This will setup a new instance, provision it and email sysadmin-main that
the instance was created, it's instance id (for terminating it, attaching
volumes, etc) and it's ip address.

You will then be able to login, as root.