Live data from Hacker News

Ansible 2.1 Released, with Network Automation, Containers

redhat.com

21–30 of 94 posts

Re: Ansible 2.1 Released, with Network Automation, Containers

#21

now with extendended network support one question gets even more important: how do you do rollbacks with ansible? There is no default mechanism or policy that seems to help with that, so I have to hand-roll my rollbacks?

Revert your playbooks and roles to the version of your last good deployment, and redeploy. With good version control, role version management and idempotent library modules, this should be functionally equivalent to a rollback. There are plenty of caveats to the above (like the fact that the yum module won't downgrade [1], and you'll need reversible DB migrations) but that's basically the procedure. [1] https://githu…

This isn't quite accurate. It won't uninstall or remove things that a previous version put into place, unless you explicitly remove them before installing them as part of your playbooks/roles.

Re: Ansible 2.1 Released, with Network Automation, Containers

#22

I hope open sourcing Ansible Tower is still on the cards after it was promised at a conference shortly after acquisition.

We've found Rundeck to be a more flexible alternative to Ansible Tower, and Rundeck is open source: https://github.com/rundeck/rundeck

Re: Ansible 2.1 Released, with Network Automation, Containers

#23
post #17
post #15

Earlier quoted context omitted.

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).

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.

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).

Re: Ansible 2.1 Released, with Network Automation, Containers

#24
post #12

I love Ansible, and have been using it since it was a humble little git repo with a single author. Unfortunately it's probably the most important python package that doesn't support Python 3, it would be cool to see it upgraded. Apparently the hold-up is supporting very old 2.x python versions because of RHEL.

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 Py…

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.

Re: Ansible 2.1 Released, with Network Automation, Containers

#25

I hope open sourcing Ansible Tower is still on the cards after it was promised at a conference shortly after acquisition.

We've found Rundeck to be a more flexible alternative to Ansible Tower, and Rundeck is open source: https://github.com/rundeck/rundeck

Not to hijack the thread, but any pointers to good resources to sell mgmt on Rundeck? We're currently using Jenkins(!?) for role, something that enforces a divide where developers are allowed to automate, but operations isn't.

Re: Ansible 2.1 Released, with Network Automation, Containers

#27
post #24
post #12

Earlier quoted context omitted.

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 Py…

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.

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.

Re: Ansible 2.1 Released, with Network Automation, Containers

#28
post #8

Does it support python3 yet ? Also, why do we have to install aptitude to do system updates ? It has been a long time since apt-get had bad resolution issues (and aptitude isn't installed by default anymore (has it ever been?)).

Aptitude is installed by default on Debian Jessie.

Re: Ansible 2.1 Released, with Network Automation, Containers

#29

Earlier quoted context omitted.

We've found Rundeck to be a more flexible alternative to Ansible Tower, and Rundeck is open source: https://github.com/rundeck/rundeck

Not to hijack the thread, but any pointers to good resources to sell mgmt on Rundeck? We're currently using Jenkins(!?) for role, something that enforces a divide where developers are allowed to automate, but operations isn't.

I'm trying to parse your statement and I'm not sure if you want something to enforce that divide or if your complaint with Jenkins is that it enforces a divide between dev and ops?

Re: Ansible 2.1 Released, with Network Automation, Containers

#30
post #8

Does it support python3 yet ? Also, why do we have to install aptitude to do system updates ? It has been a long time since apt-get had bad resolution issues (and aptitude isn't installed by default anymore (has it ever been?)).

hmm, all my cloud images (Digital Ocean, Rackspace) with Ubuntu 12.04 and 14.04 have aptitude installed by default. Only seeing a problem with Ubuntu 16.04 there.
Post reply on HN