veewee-atlassian 0.3.11

data/.gitignore

@@ -0,0 +1,19 @@
+.DS_Store
+.bundle
+Gemfile.lock
+gems/*
+iso/*
+iso
+*.ova
+tmp/*
+definitions/*
+Vagrantfile
+Vagrantfile.*
+cookbooks/*
+manifests/*
+boxes/*
+pkg/*
+*.box
+.vagrant
+virtualfloppy.vfd
+*.swp

data/.rvmrc

@@ -0,0 +1,5 @@
+rvm use ruby-1.9.2@veewee --create
+
+alias veewee="bundle exec veewee"
+alias vagrant="bundle exec vagrant"
+alias irb="bundle exec irb"

data/CONTRIBUTE.md

@@ -0,0 +1,37 @@
+# Contribute or Improving a Veewee Templates
+
+If you have a setup working, share your 'definition' with me. That would be fun!
+
+## How to add a new OS/installation
+
+I suggest the easiest way is to get an account on [Github](https://github.com).
+
+I assume that you have a working ruby environment as described in `installation.md`.
+
+Then fork [the veewee repository](https://github.com/jedi4ever/veewee) to your account and clone it to your computer:
+
+    $ git clone https://github.com/*your account*/veewee.git
+    $ cd veewee
+    $ gem install bundler
+    $ bundle install
+
+If you don't use [rvm](https://rvm.io/), be sure to execute veewee through `bundle exec`:
+
+    $ alias veewee="bundle exec veewee"
+
+Start your new definition on base of an existing one by executing:
+
+    $ veewee vbox define 'mynewos' '<your_os_of_choice>'
+
+Now follow these best practices:
+
+- Apply your changes in `./definitions/mynewos`
+- Build it with `veewee vbox build 'mynewos'`
+- Validate with `veewee vbox validate 'mynewos'`
+- When it builds OK and all tests are green, move `definition/mynewos` to a sensible directory under templates<br>
+  Hint: Follow the naming schema of existing boxes
+- Commit the changes: `git commit -a`
+- Push the changes to github: `git push`
+- Go to github and issue a pull request: `https://github.com/*your account*/veewee/pull/new/master`
+
+TODO ct 2013-02-4 Bonuspoints for feature-branches and adding tests to verify new post installs?

data/Gemfile

@@ -0,0 +1,19 @@
+#if RUBY_VERSION =~ /1.9/
+    #Encoding.default_external = Encoding::UTF_8
+    #Encoding.default_internal = Encoding::UTF_8
+#end
+
+source "http://rubygems.org"
+
+group :windows do
+  #gem "em-winrm", :git => 'git://github.com/hh/em-winrm.git', :ref => '31745601d3'
+end
+
+group :kvm do
+  gem "ruby-libvirt"
+end
+
+group :test do
+  gem "rake"
+end
+gemspec

data/License

@@ -0,0 +1,21 @@
+The MIT License
+
+Copyright (c) 2010-2012 Patrick Debois
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,47 @@
+**VeeWee:** the tool to easily build vagrant base boxes or kvm, virtualbox and fusion images.
+
+Vagrant is a great tool to test out new things or changes in a Virtual Machine (Virtualbox) using either chef or puppet.
+
+The first step to build a new Virtual Machine 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 built. Therefore lots of people end up first building their own base box which is time consuming and often cumbersome.
+
+Veewee aims to automate all the steps for building base boxes and to collect best practices in a transparent way.
+
+Besides building Vagrant boxes, veewee can also be used for:
+
+- create Virtual Machines for [VMware (Fusion)](http://www.vmware.com/products/fusion/) and [KVM](http://www.linux-kvm.org/)
+- interact with with those VMs (up, destroy, halt, ssh)
+- export them to `OVA` for [Fusion](http://www.vmware.com/products/fusion/), `IMG` for [KVM](http://www.linux-kvm.org/) and `OVF` for [Virtualbox](https://www.virtualbox.org/)
+
+
+## Get started
+
+Before you start we recommend to read through these pages:
+
+- the [requirements](doc/requirements.md)
+- the [installation](doc/installation.md) procedure
+
+Depending on how you want to use veewee, we suggest to read through one of the following guides: (**work in progress**)
+
+- [Guide for Vagrant](doc/vagrant.md)
+- [Guide for Virtualbox](doc/vbox.md)
+- [Guide for VMware Fusion](doc/fusion.md)
+- [Guide for KVM](doc/kvm.md)
+
+More detailed pages on each subject are located in the [documentation directory](doc).
+
+
+## Contribute
+
+People have reported good experiences, why don't you give it a try?
+
+If you have a setup working, share your 'definition' with me. That would be fun!
+
+See [CONTRIBUTE](CONTRIBUTE.md).
+
+## Ideas
+
+- Integrate veewee with your CI build to create baseboxes on a daily basis
+- Use of pre_postinstall_file in `definition.rb` by whren - 2012/04/12 <br>
+  See [use of pre_postinstall_file in definition.rb](https://github.com/whren/veewee/wiki/Use-of-pre_postinstall_file-in-definition.rb)

data/Rakefile

@@ -0,0 +1,129 @@
+require 'rubygems'
+require 'bundler'
+require 'bundler/setup'
+require 'veewee'
+Bundler::GemHelper.install_tasks
+
+desc 'Default: run tests'
+task :default => :test
+
+require 'rake/testtask'
+Bundler::GemHelper.install_tasks
+
+desc 'Tests not requiring an real box'
+Rake::TestTask.new do |t|
+  t.libs << "test"
+  t.pattern = 'test/**/*_test.rb'
+end
+
+desc 'Tests requiring an real box'
+Rake::TestTask.new do |t|
+  t.name="realtest"
+  t.libs << "test"
+  t.libs << "."
+  t.pattern = 'test/**/*_realtest.rb'
+end
+
+desc 'Verify ISO'
+task :iso, [:template_name] do |t, args|
+  require 'net/http'
+  #if args.to_hash.size!=1
+  #puts "needs one arguments: rake iso [\"yourname\"]"
+  #exit
+  #end
+  Dir.glob("templates/*").each do |name|
+    definition_name = File.basename(name)
+    puts name
+    definition = Veewee::Environment.new(:cwd => ".", :definition_dir => "templates").definitions[definition_name]
+    next if definition.nil? || definition.iso_src.nil? || definition.iso_src == ""
+    begin
+      url = definition.iso_src
+      found = false
+      response = nil
+      while found == false
+        uri = URI.parse(url)
+        if uri.is_a?(URI::HTTP)
+          Net::HTTP.start(uri.host, uri.port) { |http|
+            response = http.head(uri.path)
+          }
+          unless response['location'].nil?
+            #puts "Redirecting to "+response['location']
+            url = response['location']
+          else
+            length = response['content-length']
+            found = true
+          end
+        elsif uri.is_a?(URI::FTP)
+          require 'net/ftp'
+          ftp = Net::FTP.new(uri.host)
+          ftp.login
+          begin
+            length = ftp.size(uri.path)
+            found = true
+          rescue Net::FTPReplyError => e
+            reply = e.message
+            err_code = reply[0, 3].to_i
+            unless err_code == 500 || err_code == 502
+              # other problem, raise
+              raise "Got ftp site but doesn't support size subcommand"
+            end
+            # fallback solution
+          end
+
+        end
+      end
+      if length.to_i < 10000
+        puts definition.iso_src
+        puts "Incorrect length #{length.to_i}"
+        puts uri.host, uri.port, uri.path, response.code
+      end
+    rescue Exception => ex
+      puts "Error" + ex.to_s + definition.iso_src
+    end
+  end
+end
+
+desc 'Builds a template and runs validation.'
+task :autotest, [:name] do |t, args|
+
+  # Disable color if the proper argument was passed
+  shell = ARGV.include?("--no-color") ? Thor::Shell::Basic.new : Thor::Base.shell.new
+
+  # We overrule all timeouts for tcp and ssh
+  #ENV['VEEWEE_TIMEOUT']='600'
+
+  ve = Veewee::Environment.new
+  ve.ui = ::Veewee::UI::Shell.new(ve, shell)
+  ve.templates.each do |name, template|
+
+    # If pattern was given, only take the ones that match the pattern
+    unless args[:name].nil?
+      next unless name == args[:name]
+    end
+
+    begin
+      ve.definitions.define("auto", name, { 'force' => true })
+      vd = ve.definitions["auto"]
+      box = ve.providers["virtualbox"].get_box("auto")
+      puts "AUTO: Building #{name}"
+      box.build({ "auto" => true, "force" => true, 'nogui' => true })
+      puts "AUTO: Validating #{name}"
+      box.validate_vagrant({'tags' => ['virtualbox']})
+      puts "AUTO: Success #{name}"
+      box.destroy
+    rescue Exception => ex
+      puts "AUTO: Template #{name} failed - #{ex}"
+      if box.running?
+        begin
+          screenshot = "screenshot-auto-#{name}.png"
+          puts "AUTO: Taking snapshot #{screenshot}"
+          box.screenshot(screenshot)
+        rescue Veewee::Error => ex
+          puts "AUTO: Error taking screenshot"
+        end
+      end
+      exit -1
+    end
+
+  end
+end

data/bin/veewee

@@ -0,0 +1,27 @@
+#!/usr/bin/env ruby
+begin
+  require 'rubygems'
+rescue LoadError
+end
+
+require 'veewee'
+
+env = Veewee::Environment.new
+
+begin
+  # Begin logging
+  env.ui.info("veewee") { "`veewee` invoked: #{ARGV.inspect}" }
+
+  # Disable color if the proper argument was passed
+  shell = ARGV.include?("--no-color") ? Thor::Shell::Basic.new : Thor::Base.shell.new
+
+  # Attach the UI
+  env.ui = ::Veewee::UI::Shell.new(env, shell)
+  env.load!
+
+  # Start the CLI
+  ::Veewee::CLI.start(ARGV, :env => env)
+
+rescue Veewee::Error => e
+  env.ui.error "#{e}"
+end

data/doc/TODO

@@ -0,0 +1,60 @@
+Still to document:
+
+# Requirements
+  virtualbox -> 
+
+  kvm -> ruby-libvirt gem
+    v0.8.3 or higher
+  require libvirt 0.8+ version 
+    have a default dir pool installed
+    permissions to write create new volumes
+
+  vmfusion -> VMWare fusion installed
+    Tested on VMWare fusion 0.3.x
+
+# Changes to Definitions
+
+  Virtualbox options ioapic, pae are now moved to :virtualbox => { vm_options => [ :ioapic => 'on' ]}
+    now you can pass all options you have to virtualbox
+
+# Use as a library
+
+# ostype_id (not everytime exists on all providers)
+
+# Rakefile contains check iso
+# Rakefile contains test
+# Rakefile contains real_test
+
+# Templates
+  idea is to split postinstall.sh to multiple pieces
+  check for .veewee_version or .vmfusion_version to see for which provider we are building this
+  include/exclude can do this
+  default user becomes veewee, vagrant.sh will create the vagrant user if used under vagrant 
+  uploading vmware.iso
+  uploading virtualbox.iso
+
+# Validation
+  veewee.feature (depending on virtualbox, vagrant)
+  no more ssh_steps
+  uses @tags per provider
+
+# veewee vmfusion export ova
+# vagrant basebox export box
+
+# New options
+  --postinstall-include/exclude
+  --auto (download yes)
+  --force also for export
+  --debug (debug output)
+
+  ostypes are now synchronized accross kvm
+
+Todo:
+  veewee steps (username,password, + VEEWEE env variables)
+  validate vms - + features selection
+  check libvirt version
+  windows test
+  validation of checks (also - include/exclude)
+  check execs with exit code
+  multinetwork card 
+  dkms for kernel installs

data/doc/customize.md

@@ -0,0 +1,152 @@
+# Customize Veewee Definitions
+
+Definitions are stored under a directory 'definitions' relative to the current directory.
+
+    .
+    ├── definitions
+    │   └── myubuntubox
+    │       ├── <preseed.cfg, kickstart.cfg, ...>
+    │       ├── base.sh
+    │       ├── cleanup.sh
+    │       ├── chef.sh
+    │       ├── puppet.sh
+    │       ├── ruby.sh
+    │       ├── virtualbox.sh
+    │       └── ....sh
+    └── README.md
+
+The file `definition.rb` contains all the parameters to define the machine to be build (see below):
+
+  - memorysize
+  - number of cpus
+  - user account and password
+  - sudo command
+  - shutdown command
+  - URL and checksum to download the ISO
+
+When a new machine boots, it will typically fetch its initial configuration file over http from a _kickstart_ file
+defined in `kickstart_file`. These files are usually named `preseed.cfg` or `ks.cfg`.
+
+You can define multiple files by providing an array of filenames:
+
+    :postinstall_files => [ "postinstall.sh",  "postinstall_2.sh" ],
+
+Once the initial installation is done, veewee will execute each `.sh` file on the machine.
+
+INFO: The main reason for splitting up the `postinstall.sh` we used to have, is to make the steps more reusable
+for different virtualization systems. For example there is no need to install the Virtualbox Guest Additions
+on kvm or VMware Fusion.
+
+
+### Using ERB in files
+
+Add `.erb` to your files in a definition and they will get rendered.
+
+This is useful for generating kickstart, post-install at runtime.
+
+Thanks @mconigilaro for the contribution!
+
+A definition usually consists of these files:
+
+    definition.rb   - Core definition of a box like CPU, RAM and the commands for the initial boot sequence
+    postinstall.sh  - Steps that run 'after' installing the OS
+    preseed.cfg     - Default options for the installer. See https://help.ubuntu.com/12.04/installation-guide/i386/preseed-using.html
+
+Newer definitions contain of even more files to get a finer separation of concerns for the installation.
+
+
+## definition.rb
+
+The core definition of a box. All crucial properties are defined here.
+
+The `boot_cmd_sequence` is probably the most interesting because it allows you to override the initial commands
+(like keyboard layout) that are fired up in the first boot sequence.
+
+All other settings are used internally by veewee, the virtualization tool or simply for choosing the right ISO:
+
+    Veewee::Definition.declare( {
+        :cpu_count => '1',
+        :memory_size=> '256',
+        :disk_size => '10140',
+        :disk_format => 'VDI',
+        :disk_variant => 'Standard',
+        :os_type_id => 'Ubuntu',
+        :iso_file => "ubuntu-12.10-server-i386.iso",
+        :iso_src => "http://releases.ubuntu.com/precise/ubuntu-12.10-server-i386.iso",
+        :iso_md5 => "3daaa312833a7da1e85e2a02787e4b66",
+        :iso_download_timeout => "1000",
+        :boot_wait => "10",
+        :boot_cmd_sequence => [
+            '<Esc><Esc><Enter>',
+            '/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 -- <Enter>'
+        ],
+        :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"
+    })
+
+IMPORTANT: If you need to change values in the templates, be sure to run `veewee vbox undefine` to remove the old definition and then `veewee vbox define` again to copy the updated template files into the definition.
+
+PRO Tip: If you change template settings please let us know why. We are very interested in improving the templates.
+
+
+## Provider `vm_options`
+
+Each provider _can_ take options that are specific to them; more details will
+be available in each provider documentation but let's have a quick overview:
+
+    Veewee::Definition.declare({
+        :cpu_count => '1',
+        :memory_size => '256',
+        :disk_size => '10140',
+        :disk_format => 'VDI',
+        :disk_variant => 'Standard',
+        # […]
+        :postinstall_files => [ "postinstall.sh" ],
+        :postinstall_timeout => "10000",
+        :kvm => {
+            :vm_options => [
+                'network_type' => 'bridge',
+                'network_bridge_name' => 'brlxc0'
+            ]
+        },
+        :virtualbox => {
+            :vm_options => [
+                'pae' => 'on',
+                'ioapic' => 'one'
+            ]
+        }
+    })
+
+This box will have `pae` and `ioapic` enabled on Virtualbox, and will use
+the `brlxc0` bridge on with kvm (on libvirt).
+
+
+## Changes between v0.2 -> v0.3
+
+1. The `Veewee::Session.declare` is now _deprecated_ and you should use `Veewee::Definition.declare`.
+   'Postinstall_files' prefixed with an _underscore_ are not executed by default:
+       .
+       ├── definitions
+       │   └── myubuntubox
+       │       ├── _postinstall.sh    # NOT executed
+       │       ├── postinstall_2.sh   # GETS executed
+   You can enforce including or excluding files with the `--include` and `--exclude` flag when using the `<build>` command.
+   This allows you to use different scripts for installing ruby or to disable the installation of puppet or chef.
+2. The default user of definitions is now 'veewee' and not 'vagrant'.
+   This is because on other virtualizations like fusion and `kvm`, there is not relationship with the 'vagrant'.
+   The User 'vagrant' is created by the `vagrant.sh` script and not by the preseed or kickstart file.