Alvaro, That's not really a part of this use case. We'll be providing the boxes to our dev team internally and will not be hosting them in the Vagrant Cloud.
On Wednesday, April 2, 2014 3:44:03 AM UTC-5, Alvaro Miranda Aguilera wrote: > > if you host the box in vagrant cloud, you can hace thar, 1 name 2 providers > > in the vagrabt cloud you will be creating a pointer, not uploading the > actual machine, so nothing stops you to have a box that point to an > internal hostname > > i think that will help you out of the box immediately.. > > alvaros-mini:~ alvarom$ vagrant box add hashicorp/precise64 > > *==> box: Loading metadata for box 'hashicorp/precise64'* > > box: URL: https://vagrantcloud.com/hashicorp/precise64 > > This box can work with multiple providers! The providers that it > > can work with are listed below. Please review the list and choose > > the provider you will be working with. > > > 1) hyperv > > 2) virtualbox > > 3) vmware_fusion > > > Enter your choice: > > > > > On Wed, Apr 2, 2014 at 5:33 PM, Richard Boyd II > <[email protected]<javascript:> > > wrote: > >> There are several talks & slides talking about multi-provider Vagrant >> boxes but the documentation doesn't have the kind of depth that I need at >> this time so I thought I'd bring it to the community. I'll give you some >> background on what my process is and where we want to go with this: >> >> >> 1. Use packer to build the base ami and virtualbox OVA machines. >> 2. Run that through some shell provisioners. >> 3. Chunk both through the Vagrant post-processor and get two Vagrant >> boxes. >> 4. Make something happen. >> >> Step 4 is proving to be elusive. The post processor gives me (when I >> manually unpackage teh boxes) a Vagrantfile with provider specific settings >> and the metadata.json file (that is generated). >> >> What I would like to do is combine these two boxes into one uber box to >> distribute. I can manually add both boxes with the same name and launch >> vagrant init BOX_NAME then vagrant up --provider=PROVIDER_NAME successfully >> but I'd love to put both provider configs in the same Vagrantfile. So, >> here's the questions I have: >> >> A) Can one .box have one Vagrantfile with mutilple providers? >> >> B) If so, how is the metadata.json file structured to handle both >> provisioners? >> >> C) If so, for Vagrant 1.5, how does the box metadata (for versioning) >> look in multi-provider? >> >> OR >> >> Do I just make two different boxes, modify their Vagrantfiles to add more >> config info, and just continue with adding them with the same name but >> different --provider flags? >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Vagrant" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
