Could you not spin up a linux box in Azure and put ansible on that? Then you can manage your azure windows nodes from there. Its always best to keep your ansible controlers 'near' (in networking terms) to the machines you are managing anyway.
At work we have 1 ansible controller per datacenter. They can all pull their configuration from source control so the roles and playbooks are consistent and it works ok for us. On Friday, October 20, 2017 at 10:56:32 PM UTC+1, Sam Cogan wrote: > > I'm currently assessing various configuration management systems for > managing mostly Windows machines. I'm liking the look of Ansible so far, > but I am concerned I have a fairly major blocker. I need the chosen system > to be able to manage nodes that are both on a local network (which is fine) > and on a remote network (inside Azure) that is not directly connected to my > main network. > I know Ansible can talk to Azure resources, but I am primarily thinking > about configuring the Azure VMs once created. These VMs are not currently > directly addressable over the internet and ideally, I want to avoid having > to give every VM a public IP and expose WINRM for all machines. When > looking at an agent-based system such as Puppet it works fine as the nodes > call into the master, but obviously, that is not the case with Ansible. I > note that it is possible ot use a jump server, but this appears to be Linux > only. > Given this requirement, is Ansible a no-go or is there a way round this? > -- 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/4fe1e056-c9ca-4d9c-8a75-fa8db19ae958%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
