-
Notifications
You must be signed in to change notification settings - Fork 13
Using Packer to Publish as Custom Box #38
Comments
Any takers? |
@alayek are you saying that for each of the pre-configured stack, we have a static box hosted on Hashicorp, when people use zeus, they will download these boxes instead of running the provisioner? That is agreeable. I think this will fasten speed massively since they don't have to run the provisioner every single time but once the box is downloaded, it will be just within a minute to launch the entire vagrant up. |
@alayek this will take some time as we need to configure atlas, github, packer all in a orchestrated way. We may also need consul from hashicorp so it is not a trivial matter. I doubt that this can be realistically done before the Version 0.2.0. |
Agreed, provisionning time may be long the first time, but take a look at vagrant-cachier, a plugin for vagrant that share dependencies amongst same machines... So the first setup will be long, the second may be shorter... I added it in the PHP Vagrantfile. That can be a first approach to reduce provisionning time until we set up things with Hashicorp |
@mtancoigne well done! Thanks for adding this plugin. I take a look now and see if we can do it for the entire project. |
@mtancoigne I found out about this: fgrehm/vagrant-cachier#143 The guy who started this cannot maintain it anymore and is looking for someone else to do it. I am not sure if the release is stable. |
It's still used in puphpet boxes, so i think there is no problem for now |
Client side provisioning can go wrong at times, with fluctuating internet connection etc. It is better to package the whole box and host on Hashicorp as a public box.
We still need provisioning with shell script or Chef to help collaboorators tweak and have those tweaks reviewed in a reproducible manner. We would also need this for CI.
However, the end user doesn't need this.
With every release, we can set up a Git Hook to automatically provision, apply packer on the provisioned environment, and push to Hashicorp.
The text was updated successfully, but these errors were encountered: