...
|
...
|
@@ -120,7 +120,8 @@ To just transfer a file directly to many different servers:
|
120
|
120
|
|
121
|
121
|
To use templating, first run the setup module to put the template variables you would
|
122
|
122
|
like to use on the remote host. Then use the template module to write the
|
123
|
|
-files using the templates. Templates are written in Jinja2 format.
|
|
123
|
+files using the templates. Templates are written in Jinja2 format. Playbooks
|
|
124
|
+(covered below) will run the setup module for you, making this even simpler.
|
124
|
125
|
|
125
|
126
|
> ansible webservers -m setup -a "favcolor=red ntp_server=192.168.1.1"
|
126
|
127
|
> ansible webservers -m template -a "src=/srv/motd.j2 dest=/etc/motd"
|
...
|
...
|
@@ -154,9 +155,11 @@ Playbooks
|
154
|
154
|
|
155
|
155
|
Playbooks are a completely different way to use ansible and are particularly awesome.
|
156
|
156
|
|
157
|
|
-They are the basis for a really simple configuration management system, unlike
|
|
157
|
+They are the basis for a really simple configuration management and deployment system, unlike
|
158
|
158
|
any that already exist, and one that is very well suited to deploying complex
|
159
|
|
-multi-machine applications.
|
|
159
|
+multi-machine applications. While you might run the main ansible program for ad-hoc tasks,
|
|
160
|
+playbooks are more likely to be kept in source control and used to push out your configuration
|
|
161
|
+or assure the configurations of your remote systems are in spec.
|
160
|
162
|
|
161
|
163
|
An example showing a small playbook:
|
162
|
164
|
|