Set up machines without public IP ?

[olibet]

Hi,

I'm working on a (bash-script generated) Vagrantfile that up a big amount (100+) of machines on Azure. The thing is that I only have 60 public IP available, and I don't really need public IP on thses machines. It's possible to set Public IP at NONE via the Azure portal, is there a way to do this through vagrant-azure ?

Thanks a lot,

Olivier

[devigned]

Though I don't think public IP is optional right now, Vagrant-Azure could definitely deploy those machines without the public ip, but you would not be able to connect to sync files or ssh on the machine directly.

For a deployment with more machines than public IPs, if we were to enable sync and SSH features, I think we'd have to put all of the boxes behind a load balancer with a single public ip, then NAT traffic to the machines.

Do you need file sync and ssh?

[olibet]

Hey, thanks for the answer :)

I don't need ssh and file sync on these machines. I think about creating one machine with a public ip by network, and then access the other ones (if needed, few chances) from this one via RDP.

[wsmckenz]

Private IP is an absolute must. packer does it, don't know why vagrant cant. Also, like packer, you should be able specify an existing vnet in another rg. This is the only way this is useful in an enterprise environment.

[juju4]

If settings multiple systems, one can be used as jumphost for others. Ansible does that with Windows and PSRP https://docs.ansible.com/ansible/latest/plugins/connection/psrp.html

[mloskot]

I think, Hashicorp Terraform may serve as Vagrant alternative for more advanced set-up involving private networks and multi-machine.