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
|
|
|
|
|
|
|
|
|
|
|
2012-10-31 15:40:57 +00:00
|
|
|
In general to run any ansible playbook you will want to run:
|
|
|
|
|
|
|
|
|
|
sudo -i ansible-playbook /path/to/playbook.yml
|
|
|
|
|
|
|
|
|
|
|
2012-10-31 05:25:15 +00:00
|
|
|
|
|
|
|
|
cloud instances:
|
|
|
|
|
to startup a new cloud instance and configure for basic server use run (as
|
|
|
|
|
root):
|
|
|
|
|
|
|
|
|
|
el6:
|
2012-10-31 15:22:43 +00:00
|
|
|
sudo -i ansible-playbook /srv/web/infra/ansible/playbooks/el6-temp-instance.yml
|
2012-10-31 05:25:15 +00:00
|
|
|
|
|
|
|
|
f17:
|
2012-10-31 15:22:43 +00:00
|
|
|
sudo -i ansible-playbook /srv/web/infra/ansible/playbooks/f17-temp-instance.yml
|
2012-10-31 05:31:51 +00:00
|
|
|
|
|
|
|
|
|
2012-10-31 15:22:43 +00:00
|
|
|
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.
|
|
|
|
|
|
2012-10-31 05:31:51 +00:00
|
|
|
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.
|
