Well, 2 diff 'performance' considerations, target and controller, yes
filter and ignore will be the same on that side, but this is also a
problem on some targets in which accessing a fact can hang or take
very long time .. think badly performant nfs mount. Even then, target
performance can also
Hi Team,
1. How to install ansible tower on AIX nodes?
2.Can we install ansible tower without subscription?
3.Is there any RPM package to install ansible tower for ansible 2.9.
Pls share any related documents.
Thanks,
Swamy.
--
You received this message because you are subscribed to the
Absolutely, avoiding gathering the facts in the first place is
preferable. However, in terms of performance I would say that the
overhead of gathering the facts is minimal compared with the effect
that those facts have in slowing down subsequent tasks.
Mark
On Mon, 7 Jun 2021 at 16:30, Brian Coca
I was not going to use 'filter' for that since this is an 'after
gathering' feature, but a more 'proactive' ignore capability for each
subsystem, filter just removes the transmission of the data back to
the controller, not the actual gathering of it.
The issue with ignore, it is very dependant
Hi Brian,
If you are making changes in this area, then something that would be
really helpful is providing more fine grained control over which facts
are collected (currently gather_subset), and which are stored
(filter). The gather_subset is quite coarse grained, and filter is
only really usable
