you can access the data from other nodes through hostvars: hostvars[<hostname>][<varname>]
On Wed, Dec 24, 2014 at 9:14 AM, Frits Hoogland <[email protected]> wrote: > Thank you Brian! > > Can you help me a bit with that? > > Please mind I created a group of one called 'primary' and a group of one > called 'standby' in the hosts file, not sure if that can be used. > I used that to have specific per node variables declared. > > It would really help in this specific case to have a value/status obtained > on one node to configure the other or others. How is that normally done with > Ansible? > > Cheers, > Frits > > > On Wednesday, December 24, 2014 3:04:36 PM UTC+1, Brian Coca wrote: >> >> register stays on the host and gets reset in the loop to reflect the >> task was skipped, you might want to use a subsequent set_fact and then >> access the variable thourgh hostvars[<primary_host_name>]. >> >> -- >> Brian Coca > > -- > 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]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/b83afdb7-fa71-4d82-84d5-07f99beaed87%40googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. -- Brian Coca -- 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]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAJ5XC8mKvq7PK8yiJyBMHCeKK3YKP74cfqwy%3DtS%2Bvotw0Owi8A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
