Michael,
I believe you are right it's much easier to start a new play and that was also the first solution i found. Because I’m just a newbie to ansible i tried to keep things consistent and place everything which is default on a server (host file, resolve.conf , ntp.conf etc) into a playbook "common" and the applications in their own playbook. Problem was that i wanted to run both a ntp server as a ntp client. Right now everything works perfectly but i will consider your approach when i go along and everything start to become too complicated. By the way, till now i really like ansible. Thanks, Kind regards. Oiver On Thursday, November 28, 2013 9:32:13 PM UTC+1, Michael DeHaan wrote: > > Often easier to just start a new play; > > - hosts: group1:!group2 > > Targets all hosts in group1 that are not in group2 > > > On Thu, Nov 28, 2013 at 5:32 AM, Serge van Ginderachter < > [email protected] <javascript:>> wrote: > >> >> On 28 November 2013 11:23, oliver bril <[email protected] >> <javascript:>>wrote: >> >>> where can i find all these kind of parameters? >> >> >> the groups magic variable is mentioned here: >> http://www.ansibleworks.com/docs/playbooks_variables.html#magic-variables-and-how-to-access-information-about-other-hosts >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ansible Project" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > Michael DeHaan <[email protected] <javascript:>> > CTO, AnsibleWorks, Inc. > http://www.ansibleworks.com/ > > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
