I know that controlling Linux machines from a Windows machine using Ansible is completely, totally and absolutely not supported and will not be. And I know that we shouldn't create issues in Github asking anything related.
Nevertheless, for anyone that wants to push the limits (maybe you and me) because doesn't want to have another VM (consuming resources or having to set it up) and is still stuck in Windows, I created an automated installation script (forked from another one) to be used with Babun (a better Cygwin): https://github.com/tiangolo/ansible-babun-bootstrap El miércoles, 11 de diciembre de 2013, 12:50:30 (UTC-5), Taylor Brown escribió: > > > Thanks for the feedback guys. Michael, you're right that I was talking > about controlling Linux VMs FROM a Windows machine. (Sorry for the mention > of the other tools - was just clarifying that I didn't do what other > Vagrant users seem to do in a similar situation.) > > As Michael and Brian suggested, I could indeed install a Linux VM to > provision the other VMs. It honestly didn't occur to me, maybe because I am > too new to all of this, and maybe because it felt like one too many > turtles, but it is "clean". > > I ended up doing what Brian suggested (before I had the benefit of his > reply). If I'm installing a provisioning a Linux box on a Windows host (or > a Mac host that hasn't installed Ansible), I run a script to install > Ansible on the VM and then tell it to run ansible-playbook from within the > VM in local mode. Worked like a champ. > If anyone else is interested, I posted my resultant scripts here: > https://github.com/Taytay/vagrant-ansible-postgres > > Thanks everyone. > > Taylor > > On Wednesday, December 11, 2013 2:33:36 AM UTC-3, Brian Green wrote: >> >> I used the shell provisioner to launch a script that setup Ansible and >> then used Ansible in pull mode. >> >> IIRC I was able to issue management commands via vagrant ssh (ie from >> Windows command prompt). >> >> >> On Monday, December 9, 2013 8:51:07 AM UTC-6, Taylor Brown wrote: >>> >>> >>> >>> Using Vagrant to spin up dev environments promises to end many of our >>> cross-platform server-side development issues once and for all. When >>> deciding how to provision my vagrant boxes, I considered Chef, Puppet, and >>> Ansible. I settled on Ansible for reasons that are obvious to this group's >>> readers. :) After getting my Vagrant-based Postgres box provisioned with >>> Ansible, I realized that I ironically painted us into another >>> cross-platform corner once again! My Windows devs won't be able to use the >>> Ansible provisioner at all. At this point, I can either package my Vagrant >>> .boxes and ship them to the Windows devs, or I can try to get them to >>> install >>> Cygwin and other dependencies >>> <http://dhorbach.blogspot.com.ar/2013/08/working-with-ansible-in-eclipse-and.html> >>> >>> and hope for the best. >>> >>> So, I guess this post has two purposes: >>> 1) to throw another vote towards using Ansible from Windows hosts >>> (specifically for Vagrant) >>> 2) To ask what other folks have done with my predicament? I'm guessing >>> folks use Chef or Puppet for cross platform provisioning of Vagrant boxes? >>> >>> Taylor >>> >> -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/3d428d94-b6ed-4db7-a88e-d533f443b5ad%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
