Ansible 2.x support

[koobs]

Tracking issue to document the need for Ansible 2.x support. See:

FreeBSD Issue #213730: sysutils/ansible1: Remove deprecated port

[fschulze]

We will most likely need a ploy_ansible2 for this, because too many internals changed. For bsdploy we'd like to move away from ansible for license and usability reasons, but got no funding/time for it yet.

[koobs]

@fschulze Thanks for the quick update. Is it reasonable to assume that saltstack is the presumptive candidate alternative, given it's written in Python?

[fschulze]

@koobs it's definitely a good candidate. Another one is mgmt.

[rene0]

From the FreeBSD side, is there any news on this ticket?

[fschulze]

No, I hope to get to it in march. Easiest is most likely ploy_ansible2. Everything else is too much work at the moment, unless I get funding for it.

Any specific issues you need help tackling to move up the timeline for getting ploy_ansible2 out? I'm currently finding myself doing this from scratch and it's not fun reinventing the wheel.

[fschulze]

@queerbsd I started here https://github.com/fschulze/ploy_ansible/tree/ansible2

What do you mean with "doing this from scratch"?

Ideal for me would be funding to implement it. Maybe someone can also take my branch further. One big thing is adding vault support back in. The remaining tasks is getting the old functionality back that I threw out in the branch to get going at all. The absolute basics are there now.

"from scratch" on my end means reimplementing a jail management configuration entirely in Ansible 2 without the benefit of ploy. But thanks for the tip, I'll see what I can do.

[fschulze]

So, https://github.com/ployground/ploy_ansible/tree/ansible2 is mostly done I think, but I haven't done extensive testing on complex setups yet. Also bsdploy may or may not work with it, the tests definitely fail atm, because of the ploy 2.x requirement. I spent 4 days on this now and can't look into the bsdploy tests atm.

[fschulze]

I'v released a beta: ploy_ansible 2.0.0b2, currently the ploy_crypted lookup plugin is most likely broken, didn't test it yet.

[fschulze]

Fixed ploy_crypted in 2.0.0b3. Last remaining thing to test is sudo support in playbooks.

[fschulze]

With 2.0.0b4 sudo (or rather the become stuff) works as well.

[neirbowj]

Could you give us an idea of what sort of "funding" would be required to drop ansible1 as a dependency?

[fschulze]

@neirbowj I'm a freelancer. So far ploy was funded mostly by projects where it's used in production and some of my spare time because I use it myself. Recently none of these projects had the need to go beyond Ansible 1.9.x considering the involved work. I also made the observation that Ansible 2.x is much slower than Ansible 1.9.x because the way SSH connections are made changed and my custom plugin included in ploy_ansible doesn't work with the new way Ansible 2.x handles that. The only alternative I know is mitogen, but it seems it's not well received in the Ansible community. I also haven't tried it myself yet and don't know if it would play together with ploy. So overall my interest in Ansible 2.x has waned. The current state of ploy_ansible in my development branch is that both 1.9.x and 2.4.x are almost working at the same time, but 2.4.x is slower and has at least one bug (filtering tasks by tag doesn't work). I guess there isn't much left, but I was very busy with other stuff the last months. I'm also fully booked until at least the end of march, probably also april as it looks at the moment. I'm pretty sure that I will finish the porting work at some point, since it's almost there, but I either need some spare time or someone paying for it in or after april. If someone wants to book me for it, contact me via email.