aurora-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Farner" <>
Subject Review Request 32161: Create a packer definition to build a base vagrant box.
Date Tue, 17 Mar 2015 16:23:46 GMT

This is an automatically generated e-mail. To reply, visit:

Review request for Aurora, Joshua Cohen and Kevin Sweeney.

Bugs: AURORA-1203

Repository: aurora


Mostly getting the conversation started.  This change pushes most of the lower-velocity components
down into a vagrant base box [1], which we would fetch from vagrant cloud for the time being,
or on ASF infra if/when freemium ends on Atlas [2].  I managed to an example project that
served as a good guide [3].

Getting ahead of potential requests - commenting within packer json is not supported.

So far i have moved base package installation out of vagrant provisioning, and have seeded
the gradle cache.  With a cached machine image (~900 MiB), `vagrant up` took 5m24s (caveat:
sample size 1).  If we seed the python artifact cache as well, we should be able to shave
off another minure or two.


This change will not be submitted as-is, since i still need to host the machine image, but
i wanted to get your thoughts on it before i proceed further.


  Vagrantfile 2d6c2ae598e80035840f7e517e161be266b581dd 
  examples/packer/aurora.json PRE-CREATION 
  examples/packer/http/ubuntu-14.04-amd64/preseed.cfg PRE-CREATION 
  examples/packer/scripts/ PRE-CREATION 
  examples/packer/scripts/ PRE-CREATION 
  examples/packer/scripts/ PRE-CREATION 
  examples/vagrant/ ae500436e703140065e5c16fc0e38dbe3214e69f 




Bill Farner

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message