Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Well I would like to add my 2 cents and I have to say my experience with Ansible has been comparably bad on Windows as a development machine. I have my tools in Windows, I rather prefer not having to duplicate all that in order to do some devops.

People used to tell it is possible to bootstrap Ansible via Vagrant on Windows:

1. define a linux box as ansible control vm, provision it using vagrant's shell provider 2. mount the playbook and run it

Well, I have spent hours on this. There were errors with Python in Linux (I forgot which, but I could solve this via searches in news groups), mounting rights, but most importantly I couldn't get the ssh part working in a multi-machine setup. I still don't understand how this could happen without Ansible halting, but Ansible did apply all the remote playbooks on the control vm itself. Even whith explicitly different ip's specified.

In the end I did gave up, having wasted so much time on a productivity tool. I am ready to accept this is due to me being stupid, but other tools don't make me look as such which is better for my self esteem.

I'll have a new try soon as Vagrant and Ansible keeps maturing and maybe I can find a tutorial this time which works with the current state of Ansible.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: