Skip to content
This repository has been archived by the owner on Oct 26, 2023. It is now read-only.

Using Packer to Publish as Custom Box #38

Closed
alayek opened this issue May 26, 2016 · 7 comments
Closed

Using Packer to Publish as Custom Box #38

alayek opened this issue May 26, 2016 · 7 comments

Comments

@alayek
Copy link
Member

alayek commented May 26, 2016

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.

@alayek alayek added this to the Version 0.1.1 milestone May 26, 2016
@alayek
Copy link
Member Author

alayek commented May 26, 2016

Any takers?

@byteknacker
Copy link
Contributor

@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.

@byteknacker
Copy link
Contributor

@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.

@byteknacker byteknacker self-assigned this May 28, 2016
@byteknacker byteknacker modified the milestones: Version 0.2.0, Version 0.1.1 May 28, 2016
@mtancoigne
Copy link
Contributor

mtancoigne commented Jun 1, 2016

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

@byteknacker
Copy link
Contributor

@mtancoigne well done! Thanks for adding this plugin. I take a look now and see if we can do it for the entire project.

@byteknacker
Copy link
Contributor

@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.

@mtancoigne
Copy link
Contributor

It's still used in puphpet boxes, so i think there is no problem for now

@ghost ghost closed this as completed Jun 18, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants