Re: [ansible-devel] Fixing architecture-specific gaps in ansible core facts?
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 affect the controller by occupying the forks for too long and delaying the play in general. -- -- Brian Coca -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-devel/CACVha7dEJX3UNMeJ4MMBSwZxKbvZWFMWBFxTzYa4LPygTmcwtQ%40mail.gmail.com.
[ansible-devel] Install Ansible Tower
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 Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-devel/0276067d-6681-4f6a-b4cc-ba54f1ac5014n%40googlegroups.com.
Re: [ansible-devel] Fixing architecture-specific gaps in ansible core facts?
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 wrote: > > 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 on the method/code used to > do the gathering, which can vary by platform, OS, distro, distro > version, etc. I have not found a good way to handle that yet. > > -- > Brian Coca > -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-devel/CAFHSqWpEdWXZSqTaytHmwsfKTjR4OAOGVxhp%2Bq8PHEjwGXQ33w%40mail.gmail.com.
Re: [ansible-devel] Fixing architecture-specific gaps in ansible core facts?
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 on the method/code used to do the gathering, which can vary by platform, OS, distro, distro version, etc. I have not found a good way to handle that yet. -- Brian Coca -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-devel/CACVha7fgxqap%3DVJ5ar5-Mjvuvq781%2BO3VPva7arF9p_PGLekSA%40mail.gmail.com.
Re: [ansible-devel] Fixing architecture-specific gaps in ansible core facts?
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 if you are wanting to refresh one or more similarly named facts. To provide some context, I have been spending a lot of time recently trying to improve the performance of Ansible at a moderate (~200) scale. As I'm sure you're aware, facts are a *huge* source of slowness, taking us from a baseline of 2 seconds to execute a task to 30+ seconds. In our particular case the target hosts are the controllers and hypervisors in an OpenStack cloud. On these machines there can be many virtual network interfaces, each creating a large fact. Our current solution looks like this: filter: "ansible_[!qt]*" Which removes the virtual interfaces that begin with q or t. We are lucky to not be filtering out any useful facts with this. A more flexible system such as a list of regexes would be a big help. Thanks, Mark On Fri, 4 Jun 2021 at 20:33, Brian Coca wrote: > > For now module_utils/facts/ is best place to add these. > > In the long run, I hope to be able to make a bunch of 'facts modules' > and eventually deprecate 'setup.py'. > Many of the changes to fact gathering have been moving in this direction: > - gather_facts action is now responsible for the play's gather_facts > (normally still calls setup module) > - gather_facts supports configurable set of modules (network_os > resolution already built in) > - gather_facts can run multiple modules in parallel > > > > > -- > -- > Brian Coca > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Development" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ansible-devel+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-devel/CACVha7dRGV-gw86qO1JUsenWi9DxFRkKD6F_bLyC66SMf0WAxA%40mail.gmail.com. -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-devel/CAFHSqWoq9x8ERXh7Rszc4e3EgYoB3Gh%2BvLKAarspdTsHB2mDZQ%40mail.gmail.com.
