Turns out it was easier than I thought. [LB:children] LB0 LB1
[LB0] VMName00 ansible_host=LBName.eastus.cloudapp.azure.com ansible_port=xxxx [LB1] VMName01 ansible_host=LBName.eastus.cloudapp.azure.com ansible_port=xxxy MAc On Wednesday, January 23, 2019 at 3:11:53 PM UTC-6, Michael Cruz wrote: > > Hello All, > > I have Windows VM's in Azure behind a Public LoadBalancer the VM's are > set up to use a Network Security Group to keep traffic limited to our > office. My inventory.yml is set up by name:port where the last digit is > different > > [LBName] > LBName.eastus.cloudapp.azure.com:xxxx > LBName.eastus.cloudapp.azure.com:xxxy > LBName.eastus.cloudapp.azure.com:xxxz > > When I run a playbook I normally limit to the Group Name. I keep a > separate group_vars yml for just the login information > The issue is that because the name is the same for all 3 only the first > one ever gets reached for TASK [Gathering Facts] > > These machines only have the public IP address which is the LB they have a > Private IP which is not accessible at this time. This is why I am using the > Public IP Address DNS Name. > Writing this out I could see a potential solution with creating a new > network structure but that has a different issue for me. > Any ideas? > > Thank You! > > MAc > > -- 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/c6737729-3ef4-4253-ac47-d36b561cc19a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
