Remix.run Logo
ringeryless 2 days ago

Just to clarify, for the reader, that ansible and python are only required for the deployment host, not it's targets.

being agentless and using ssh for transport, the target hosts need only have an ip address listed in the deployment hosts inventory, aka one can address target hosts directly after creating them, given ssh access.

much of ansibles python issues are just python issues.

ansible is a very flexible tool, and idempotent behavior is largely a factor of playbook design until it hits real world limits.

bravetraveler 2 days ago | parent [-]

The managed nodes do indeed need Python, though the requirements tend to be lower.

The bulk of the modules essentially generate Python payloads for Ansible to ship/run/track. Most of the burden is on the controller. Not all.

The execution environment information I linked [in another comment] covers what this user points out

Xiol32 2 days ago | parent [-]

Not low enough, unfortunely.

Ran into this recently with Ansible 2.17 which can no longer fully run (dnf/yum modules don't work) on EL8 targets due to platform-python being 3.6.

2.16 still works but goes EOL in May, when the OS is supported until 2029.

Feels like a very deliberate attempt to get you paying for Red Hat's version. On one hand I can't blame them, but on the other, that's never going to happen at my company.

bravetraveler 2 days ago | parent [-]

Definitely feels like a nudge. "Oh, you're on EL?"

More of an own-goal than anything. This'll just push more to Shuttleworth.