Hi, yeah i know we can do some sort of work around it to keep track.
Just thought if ansible already has something in place..

i remembered puppet has this site.pp file which includes the manifests that 
the nodes have.. (or my recollection fails me..)

On Tuesday, May 8, 2018 at 10:16:14 AM UTC+8, Michael Pechner wrote:
>
> I'm new as well.  If you are suing tower, does it track this?
> If not using tower...
> Since when ansible runs, other than the effects of the playbooks, it 
> cleans it self up.
> In each playbook you can always maintain an ini or some resource file you 
> recreate at each run to add an entry for each playbook.
> Or an ini with a section  for each playbook, and a time stamp for the run 
> to keep a running log.
>
> This way you can run a ansible job that queries this file to see the last 
> time each playbook ran.
>
> My 2 cents.  
>
> On Mon, May 7, 2018 at 6:53 PM, Edmund Cheng <[email protected] 
> <javascript:>> wrote:
>
>> Well, I have not found something in ansible which can tell us that info 
>> at a glance.
>>
>>
>>
>> On Monday, May 7, 2018 at 5:10:18 PM UTC+8, Benny Kusman wrote:
>>>
>>> good question. wondering if there is a way to find out this as well.
>>> i find that ansible inventory "management" is rather tricky
>>>
>>> On Mon, May 7, 2018 at 5:49 AM, Edmund Cheng <[email protected]> wrote:
>>>
>>>> Hi,
>>>> I recently started ansible and have a question:
>>>>
>>>> - Lets say we have like 100 playbooks running against a few hundred 
>>>> hosts, perhaps some playbooks are running against different groups as 
>>>> defined in the ansible host file.
>>>> Do we have a way to know which groups of hosts have which playbooks 
>>>> that are running against them?
>>>> Meaning I do not have to open each and every playbook just to see what 
>>>> hosts they are running against?
>>>>
>>>> Any advise is appreciated!
>>>> Thanks...
>>>>
>>>> -- 
>>>> 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/345ed2b0-40ca-4120-b271-d813eaf5bc0e%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/ansible-project/345ed2b0-40ca-4120-b271-d813eaf5bc0e%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> -- 
>> 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:>.
>> To post to this group, send email to [email protected] 
>> <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/ansible-project/0447a872-6dd2-46b8-ab8e-afb124373077%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/ansible-project/0447a872-6dd2-46b8-ab8e-afb124373077%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Michael Pechner
> NE6RD - Amateur Extra
> [email protected] <javascript:>
>

-- 
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/61742de1-852d-4ebf-b4eb-81da55569f70%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to