mirror of
https://pagure.io/fedora-infra/ansible.git
synced 2026-03-20 12:07:34 +08:00
22cbcb1b2e6b1d7bace017e1b16ecd2db07e30e3
takes ip addresses instead of instance ids for shutting down instances
…
…
…
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.
Description
Languages
JavaScript
31.8%
Jinja
24.4%
CSS
22.1%
Python
14.9%
Shell
3.4%
Other
3.3%