https://github.com/szuecs/veewee

Easing the building of vagrant boxes
https://github.com/szuecs/veewee

Last synced: 3 months ago
JSON representation

Easing the building of vagrant boxes

• Host: GitHub
• URL: https://github.com/szuecs/veewee
• Owner: szuecs
• Fork: true (jedi4ever/veewee)
• Created: 2012-01-03T13:44:50.000Z (almost 13 years ago)
• Default Branch: master
• Last Pushed: 2011-12-31T07:29:19.000Z (almost 13 years ago)
• Last Synced: 2023-04-13T13:26:09.742Z (over 1 year ago)
• Language: Shell
• Homepage:
• Size: 1.42 MB
• Stars: 1
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
**VeeWee:** the tool to easily build vagrant base boxes

Vagrant is a great tool to test new things or changes in a virtual machine(Virtualbox) using either chef or puppet.

The first step is to download an existing 'base box'. I believe this scares a lot of people as they don't know who or how this box was build. Therefore lots of people end up first building their own base box to use with vagrant.

Veewee tries to automate this and to share the knowledge and sources you need to create a basebox. Instead of creating custom ISO's from your favorite distribution, it leverages the 'keyboardputscancode' command of Virtualbox so send the actual 'boot prompt' keysequence to boot an existing iso.

Before we can actually build the boxes, we need to take care of the minimal things to install:

- Have Virtualbox 4.x installed -> download it from http://download.virtualbox.org/virtualbox/

People have reported good experiences, why don't you give it a try?

## Installation:

__as a gem__

    $ gem install veewee

__from source__

    $ git clone https://github.com/jedi4ever/veewee.git

    $ cd veewee

    $ gem install bundler

    $ bundle install

If you don't use rvm, be sure to execute vagrant through bundle exec

    $ alias vagrant="bundle exec vagrant"

## List all templates

    $ vagrant basebox templates

    The following templates are available:

    vagrant basebox define '' 'CentOS-4.8-i386'

    vagrant basebox define '' 'CentOS-5.5-x86_64-netboot'

    vagrant basebox define '' 'CentOS-5.6-i386'

    vagrant basebox define '' 'CentOS-5.6-i386-netboot'

    vagrant basebox define '' 'CentOS-5.6-x86_64-netboot'

    vagrant basebox define '' 'CentOS-5.7-i386-netboot'

    vagrant basebox define '' 'CentOS-5.7-x86_64-netboot'

    vagrant basebox define '' 'CentOS-6.0-i386'

    vagrant basebox define '' 'CentOS-6.0-i386-netboot'

    vagrant basebox define '' 'CentOS-6.0-x86_64'

    vagrant basebox define '' 'CentOS-6.0-x86_64-minimal'

    vagrant basebox define '' 'CentOS-6.0-x86_64-netboot'

    vagrant basebox define '' 'Debian-5.0.8-amd64-netboot'

    vagrant basebox define '' 'Debian-5.0.8-i386-netboot'

    vagrant basebox define '' 'Debian-6.0.3-amd64-netboot'

    vagrant basebox define '' 'Debian-6.0.3-i386-netboot'

    vagrant basebox define '' 'Fedora-14-amd64'

    vagrant basebox define '' 'Fedora-14-amd64-netboot'

    vagrant basebox define '' 'Fedora-14-i386'

    vagrant basebox define '' 'Fedora-14-i386-netboot'

    vagrant basebox define '' 'Fedora-15-i386'

    vagrant basebox define '' 'Fedora-15-i386-netboot'

    vagrant basebox define '' 'Fedora-15-x86_64'

    vagrant basebox define '' 'Fedora-15-x86_64-netboot'

    vagrant basebox define '' 'Sysrescuecd-2.0.0-experimental'

    vagrant basebox define '' 'archlinux-i386'

    vagrant basebox define '' 'archlinux-i386-netboot'

    vagrant basebox define '' 'archlinux-x86_64'

    vagrant basebox define '' 'archlinux-x86_64-netboot'

    vagrant basebox define '' 'freebsd-8.2-experimental'

    vagrant basebox define '' 'freebsd-8.2-pcbsd-i386'

    vagrant basebox define '' 'freebsd-8.2-pcbsd-i386-netboot'

    vagrant basebox define '' 'gentoo-latest-i386-experimental'

    vagrant basebox define '' 'openSUSE-11.4-DVD-i586'

    vagrant basebox define '' 'openSUSE-11.4-DVD-x86_64'

    vagrant basebox define '' 'openSUSE-11.4-NET-i586'

    vagrant basebox define '' 'openSUSE-11.4-NET-x86_64'

    vagrant basebox define '' 'openindiana-148-ai-x86'

    vagrant basebox define '' 'opensuse-11.4-i386-experimental'

    vagrant basebox define '' 'scientificlinux-6.1-i386-netboot'

    vagrant basebox define '' 'scientificlinux-6.1-x86_64-netboot'

    vagrant basebox define '' 'solaris-11-express-i386'

    vagrant basebox define '' 'ubuntu-10.04.2-amd64-netboot'

    vagrant basebox define '' 'ubuntu-10.04.2-server-i386-netboot'

    vagrant basebox define '' 'ubuntu-10.04.3-server-amd64'

    vagrant basebox define '' 'ubuntu-10.04.3-server-amd64-alt'

    vagrant basebox define '' 'ubuntu-10.04.3-server-i386'

    vagrant basebox define '' 'ubuntu-10.10-server-amd64'

    vagrant basebox define '' 'ubuntu-10.10-server-amd64-netboot'

    vagrant basebox define '' 'ubuntu-10.10-server-i386'

    vagrant basebox define '' 'ubuntu-10.10-server-i386-netboot'

    vagrant basebox define '' 'ubuntu-11.04-server-amd64'

    vagrant basebox define '' 'ubuntu-11.04-server-i386'

    vagrant basebox define '' 'ubuntu-11.10-server-amd64'

    vagrant basebox define '' 'ubuntu-11.10-server-amd64-ishaya'

    vagrant basebox define '' 'ubuntu-11.10-server-amd64-ruby192'

    vagrant basebox define '' 'ubuntu-11.10-server-i386'

    vagrant basebox define '' 'ubuntu-8.04.4-server-amd64'

    vagrant basebox define '' 'ubuntu-8.04.4-server-i386'

    vagrant basebox define '' 'windows-2008R2-amd64'

## Define a new box

Let's define a  Ubuntu 10.10 server i386 basebox called myunbuntubox

this is essentially making a copy based on the  templates provided above.

    $ vagrant basebox define 'myubuntubox' 'ubuntu-10.10-server-i386'

    The basebox 'myubuntubox' has been succesfully created from the template ''ubuntu-10.10-server-i386'

    You can now edit the definition files stored in definitions/myubuntubox

    or build the box with:

    vagrant basebox build 'myubuntubox'

-> This copies over the templates/ubuntu-10.10-server-i386 to definition/myubuntubox

    $ ls definitions/myubuntubox

    definition.rb	postinstall.sh	postinstall2.sh	preseed.cfg

## Optionally modify the definition.rb , postinstall.sh or preseed.cfg

    Veewee::Session.declare( {

    :cpu_count => '1', :memory_size=> '256', 

    :disk_size => '10140', :disk_format => 'VDI',

    :os_type_id => 'Ubuntu',

    :iso_file => "ubuntu-10.10-server-i386.iso", 

    :iso_src => "http://releases.ubuntu.com/maverick/ubuntu-10.10-server-i386.iso",

    :iso_md5 => "ce1cee108de737d7492e37069eed538e",

    :iso_download_timeout => "1000",

    :boot_wait => "10",

    :boot_cmd_sequence => [ 

        '',

        '/install/vmlinuz noapic preseed/url=http://%IP%:%PORT%/preseed.cfg ',

        'debian-installer=en_US auto locale=en_US kbd-chooser/method=us ',

        'hostname=%NAME% ',

        'fb=false debconf/frontend=noninteractive ',

        'console-setup/ask_detect=false console-setup/modelcode=pc105 console-setup/layoutcode=us ',

        'initrd=/install/initrd.gz -- ' 

      ],

    :kickstart_port => "7122", :kickstart_timeout => "10000",:kickstart_file => "preseed.cfg",

    :ssh_login_timeout => "10000",:ssh_user => "vagrant", :ssh_password => "vagrant",:ssh_key => "",

    :ssh_host_port => "2222", :ssh_guest_port => "22",

    :sudo_cmd => "echo '%p'|sudo -S sh '%f'",

    :shutdown_cmd => "shutdown -H",

    :postinstall_files => [ "postinstall.sh"],:postinstall_timeout => "10000"

     }

    )

If you need to change values in the templates, be sure to run the rake undefine, the rake define again to copy the changes across.

## Getting the cdrom file in place

Put your isofile inside the 'currentdir'/iso directory or if you don't run

    $ vagrant basebox build 'myubuntubox'

- the build assumes your iso files are in 'currentdir'/iso

- if it can not find it will suggest to download the iso for you

- use '--force' to overwrite an existing install

## Build the new box:

    $ vagrant basebox build 'myubuntubox'

- This will create a machine + disk according to the definition.rb

- Note: :os_type_id = The internal Name Virtualbox uses for that Distribution

- Mount the ISO File :iso_file

- Boot up the machine and wait for :boot_time

- Send the keystrokes in :boot_cmd_sequence

- Startup a webserver on :kickstart_port to wait for a request for the :kickstart_file (don't navigate to the file in your browser or the server will stop and the installer will not be able to find your preseed)

- Wait for ssh login to work with :ssh_user , :ssh_password

- Sudo execute the :postinstall_files

## Validate the vm 

    $ vagrant basebox validate 'myubuntubox'

this will run some cucumber test against the box to see if it has the necessary bits and pieces for vagrant to work

## Export the vm to a .box file

    $ vagrant basebox export 'myubuntubox'

this is actually calling - vagrant package --base 'myubuntubox' --output 'boxes/myubuntubox.box'

this will result in a myubuntubox.box

## Add the box as one of your boxes

To import it into vagrant type:

    $ vagrant box add 'myubuntubox' 'myubuntubox.box'

## Use it in vagrant

To use it:

    $ vagrant init 'myubuntubox'

    $ vagrant up

    $ vagrant ssh

## How to add a new OS/installation (needs some love)

I suggest the easiest way is to get an account on github and fork of the veewee repository

    $ git clone https://github.com/*your account*/veewee.git

    $ cd veewee

    $ gem install bundler

    $ bundle install

If you don't use rvm, be sure to execute vagrant through bundle exec

    $ alias vagrant="bundle exec vagrant"

Start of an existing one

    $ vagrant basebox define 'mynewos' 'ubuntu...'

- Do changes in the currentdir/definitions/mynewos

- When it builds ok, move the definition/mynewos to a sensible directory under templates

- commit the changes (git commit -a)

- push the changes to github (git push)

- go to the github gui and issue a pull request for it

## If you have a setup working, share your 'definition' with me. That would be fun! 

IDEAS:

- Now you integrate this with your CI build to create a daily basebox

FUTURE IDEAS:

- export to AMI too

- provide for more failsafe execution, testing parameters

- Do the same for Vmware Fusion