Bento is a project that encapsulates Veewee definitions for building Vagrant baseboxes. We use these boxes internally at Opscode for testing Hosted Chef, Private Chef and our open source cookbooks.
These basebox definitions are originally based on work done by Tim Dysinger to make "Don't Repeat Yourself" (DRY) modular baseboxes. Thanks Tim!
The following baseboxes are publicly available and were built using this project, and Chef 11.4.4. Future releases of Chef and baseboxes will follow the naming convention used here:
opscode_PLATFORM-VERSION_chef-VERSION.box
and located in the opscode-vm S3 bucket's vagrant directory as linked below.
64-bit boxes:
32-bit boxes:
The following base boxes were built with Chef 11.4.0.
64-bit boxes:
32-bit boxes:
The following base boxes were built with Chef 11.2.0. (No 32-bit boxes were built for Chef 11.2.0.)
The following base boxes were built with Chef 10.18.2.
- opscode-centos-5.8-i386
- opscode-centos-5.8
- opscode-centos-6.3-i386
- opscode-centos-6.3
- opscode-ubuntu-10.04-i386
- opscode-ubuntu-10.04
- opscode-ubuntu-12.04-i386
- opscode-ubuntu-12.04
The following base boxes were built with Chef 10.14.4.
- opscode-centos-5.8-i386
- opscode-centos-5.8
- opscode-centos-6.3-i386
- opscode-centos-6.3
- opscode-ubuntu-10.04
- opscode-ubuntu-10.04-i386
- opscode-ubuntu-12.04
- opscode-ubuntu-12.04-i386
First, clone the project, then install the required Gems with Bundler.
$ git clone git://github.com/opscode/bento.git
$ cd bento
$ bundle install
List available baseboxes that can be built:
$ bundle exec veewee vbox list
Build, for example, the ubuntu-12.04 basebox.
$ bundle exec veewee vbox build ubuntu-12.04
You can validate the basebox using Veewee's built in validator.
However note that the test for Ruby (and Puppet) will fail. The Ruby
installation is in /opt/chef/embedded, and we do not add the bin
directory to the $PATH, and we don't use Puppet internally.
$ bundle exec veewee vbox validate ubuntu-12.04
Aside from that, the basebox should be ready to use. Export it:
$ bundle exec veewee vbox export ubuntu-12.04
Congratulations! You now have ./ubuntu-12.04.box, a fully functional
basebox that you can then add to Vagrant and start testing cookbooks.
Veewee reads the definition specified and automatically builds a
VirtualBox machine. The VirtualBox guest additions and the target OS
ISO are downloaded into the iso/ directory.
We use Veewee version 0.3.0.alpha+ because it contains fixes for building CentOS boxes under certain circumstances.
The definitions themselves are split up into directories that get symlinked into specific basebox directories.
Most of the files are symlinked for a particular box. The one
exception is the definition.rb file, which contains the specific
configuration for the Veewee session for a basebox, including the ISO
filename, its source URL, and the MD5 checksum of the file.
chef-client.sh: Installs Chef and Ruby with Opscode's full stack installerminimize.sh: Zeroes out the root disk to reduce file size of the boxruby.sh: Deprecated Usechef-client.shsession.rb: Baseline session settings for Veeweevagrant.sh: Installs VirtualBox Guest Additions, adds the Vagrant SSH key
cleanup.sh: Removes unneeded packages, cleans up package cache, and removes the VBox ISO and Chef rpmks.cfg: Kickstart file for automated OS installationsession.rb: General CentOS session settings for Veewee
cleanup.sh: Removes unneeded packages, cleans up package cache, and removes the VBox ISO and Chef debnetworking.sh: Removes networking setup like udev that may interfere with Vagrant network setuppreseed.cfg: The Debian Preseed file for automated OS installationsession.rb: General Ubuntu session settings for Veeweesudoers.sh: Customization for/etc/sudoersupdate.sh: Ensures that the OS installation is updated
install-chef.bat: Installs Chef and Ruby with Opscode's full stack installeroracle-cert.cer: Needed for automated install via install-vbox.batinstall-vbox.bat: Installs VirtualBox Guest Additionsmount-validation.bat: Mounts the validation drive
Use the issue tracker to report bugs, features or other issues.
How to contribute to Opscode open source software projects
- Author:: Seth Chisamore ([email protected])
- Author:: Stephen Delano ([email protected])
- Author:: Joshua Timberman ([email protected])
- Author:: Tim Dysinger ([email protected])
- Author:: Chris McClimans ([email protected])
- Author:: Julian Dunn ([email protected])
Copyright:: 2012-2013, Opscode, Inc ([email protected]) Copyright:: 2011-2012, Tim Dysinger ([email protected])
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.