Consider adding other variable inputs

[lamoni]

I've kept the variables.json to a bare minimum for a simple homelab-style Junos Space deployment.

It is easy to add things like NTP server, disk expansion, etc..., but I'm going to hold off on that until it's decided that this (Packer) is definitely a good route to take for auto-provisioning/deploying Junos Space.

[taliesins]

@lamoni you probably want to use Packer to spin up a base box and then use something like Terraform or Vagrant for environment provisioning.

I am also in the process of automating vMX and Space. I have tweaked the 2 vms needed for the vMX so that they boot via DHCP, so you can use them as base boxes. This allows you to use static macs in Vagrant, so you can assign it a "static ip" via dhcp. Works great for spinning up vMXs in VSphere and Virtual Box.

You ever tried configuring Space to run with DHCP? Any hints?

[lamoni]

@taliesins Sorry for not seeing this (I'm just now going back through a bunch of my old repos). I know Space had some issues with DHCP because there are a bunch of internal "homebaked" scripts that run when you enter the IP and subnet values during initial setup, I never looked further into bypassing any of that (or hacking it up to where it waits and reads the DHCP assigned address)

I know it's been over 2 years lol, did you make any progress, out of curiosity? I don't really deal with Space anymore, but still interested to hear. Haven't set the thing up in like 3 years, so not sure if they ever made the process cleaner.