Ansible 2.1 Released, with Network Automation, Containers

Re:Ansible 2.1 Released, with Network Automation, Containers by benhoyt on Thursday May 26, 2016 @08:23AM (#11777348)

I think it actually makes sense for something like Ansible to use Python 2 because it's about controlling lots of remote machines on various Linux distros, and the idea is that it's agentless. If you suddenly have to install an "agent" (Python 3) on all the remote machines before you control them with Ansible, that wouldn't be great.

On the other hand, Ansible itself could have a tiny bootstrap step which installs Python 3 on all the remote machines before it does any work.

In our case, we use Ansible daily for deployments, but haven't actually written any custom Python modules -- it's all just straight Ansible YAML. So I'm guessing for a lot of use cases it doesn't really matter what language Ansible is written in.

[ Parent | on HN ]

Re:Ansible 2.1 Released, with Network Automation, Containers by Aissen on Thursday May 26, 2016 @08:48AM (#11777482)

Or, they could support both so that they can be an agent for distros that won't have python2 installed and only python3 (AFAIK they don't exist yet).

[ Parent | on HN ]

Re:Ansible 2.1 Released, with Network Automation, Containers by renaudg on Thursday May 26, 2016 @09:10AM (#11777600)

The latest Ubuntu LTS 16.04 only has Python3 installed by default. For Ansible modules to run at all, you need to install Python 2 first (possibly using "pre_tasks" + a "raw:" command in your Ansible playbook)

[ Parent | on HN ]

Re:Ansible 2.1 Released, with Network Automation, Containers by rlpb on Thursday May 26, 2016 @09:10AM (#11777598)

Ubuntu Server no longer has Python 2 installed by default (though it's available if you want it). This is the case on 16.04.

[ Parent | on HN ]

Re:Ansible 2.1 Released, with Network Automation, Containers by Aissen on Thursday May 26, 2016 @09:41AM (#11777824)

Ah, I thought I heard about that somewhere. I did tests on 16.04 recently with ansible, but python2 was here, so I guess the image I was using wasn't a vanilla ubuntu (from a VPS provider).

[ Parent | on HN ]

Re:Ansible 2.1 Released, with Network Automation, Containers by ausjke on Thursday May 26, 2016 @09:45AM (#11777855)

if it's _truly_ agent-less why do they care about the python version on the target, I feel that python target code is the agent? I might be missing something.

Tried it a while ago, interested in developing tower-like management software(light-weight) using javascript as Tower is a bit too pricey for small/mid-sized customers.

[ Parent | on HN ]

Re:Ansible 2.1 Released, with Network Automation, Containers by calvins on Thursday May 26, 2016 @11:06AM (#11778469)

> if it's _truly_ agent-less why do they care about the python version on the target, I feel that python target code is the agent?

"Agentless" means that it works by pushing to the machine and that there isn't an agent process already running on the target. It doesn't mean that there aren't any requirements on what needs to be installed on the target already.

[ Parent | on HN ]

Re:Ansible 2.1 Released, with Network Automation, Containers by acveilleux on Thursday May 26, 2016 @09:55AM (#11777939)

It can do truly agent-less using raw mode (which is basically raw SSH). That said a version of Python 2 can be relied upon to be available on almost all Linux box.

[ Parent | on HN ]

Re:Ansible 2.1 Released, with Network Automation, Containers by ausjke on Thursday May 26, 2016 @10:03AM (#11778008)

yes that's what I used as my target is a resource-restricted router that does not have space for any python, that's the only occasion you can call it agent-less, but most people are not using that mode.

[ Parent | on HN ]