veewee 0.3.7 → 0.3.9

data/doc/README-changes.txt

@@ -1,20 +0,0 @@
-Changelog
-  now has include-postinstall, exclude-postinstall
-  now has pre_postinstall_file allowing pre postinstall execution (ie to export http_proxy, https_proxy)
-  ostypes are now synchronized accross kvm
-  require libvirt 0.8+ version 
-  user veewee instead of vagrant
-  veewee::session.declare / not veewee.defintion...
-  veewee subcommand compared to vagrant subcommand
-  veewee ssh
-  veewee start/stop
-  veewee steps (username,password, + VEEWEE env variables)
-
-Todo:
-  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/TODO

@@ -1,60 +0,0 @@
-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/definition.md

@@ -1,83 +0,0 @@
-# Veewee definition
-
-## Creating a definition
-A definition is created by 'cloning' a *template*.
-
-To create a definition you use the 'define' subcommand:
-
-    veewee vbox define 'myubuntu' 'ubuntu-10.10-server-amd64'
-
-If you want to use an external repo for the definition you can specify a git-url
-
-    veewee vbox define 'myubuntu' 'git://github.com/jedi4ever/myubuntu'
-
-## Modifying a definition
-Definitions are stored under a directory 'definitions' relative to the current directory.
-
-    <currentdir>
-    |- <definitions>
-    |   |--myubuntu
-    |      |-- definition.rb
-    |      |-- <preseed.cfg,kickstart.cfg,....>
-           |-- base.sh
-           |-- ....sh
-           |-- ruby.sh
-           |-- chef.sh
-           |-- puppet.sh
-           |-- virtualbox.sh
-           |-- ...sh
-           |-- cleanup.sh
-
-The file 'definition.rb' contains all the parameters to define the machine to be build:
-
-  - memorysize
-  - number of cpus
-  - user account and password
-  - sudo command
-  - shutdown command
-  - URL and checksum to download the ISO
-  - ....
-
-When a new boots, it will typically fetch it's initial configuration file over http from a preseed.cfg, kickstart, ... file
-
-Once the initial installation is done, veewee will log in to the sytem and starts executing the 'shell files'
-
-The main reason for splitting up the postinstall.sh we used to have, it to make the script parts reusable for different virtualization systems: f.i. no need to install virtualbox guest additions on kvm or vmware fusion.
-
-_Changes between v0.2 -> v0.3_
-
-The 'Veewee::Session.declare' is now deprecated and you should use 'Veewee::Definition.declare'
-
-'Postinstall_files' prefixed with an  _underscore_ are not executed but can be toggled with the --include, --exclude with the <build> command. This allows you to insert different ruby.sh scripts, disable the installation of puppet, etc...
-
-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'. Users 'vagrant' are created by the 'vagrant.sh' script and not by the preseed or kickstart.
-
-_Using ERB in files_
-
-Add '.erb' to your files in a definition and they will get rendered (useful for generting kickstart,postinstall) (thx @mconigilaro)
-
-## Listing existing definitions
-
-    veewee vbox list
-
-## Removing a definition
-
-    veewee vbox undefine 'myubuntu'
-
-## Provider ``vm_options``
-
-Each provider _can_ take options that are specific to them ; more detail 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).

data/doc/install.md

@@ -1,16 +0,0 @@
-## 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"
-

data/doc/running.md

@@ -1,83 +0,0 @@
-# Running veewee
-
-## Calling veewee
-
-### Using veewee cli
-The first way to call veewee is through the 'veewee' cli command:
-
-    $ veewee
-    Tasks:
-      veewee fusion       # Subcommand for Vmware fusion
-      veewee help [TASK]  # Describe available tasks or one specific task
-      veewee kvm          # Subcommand for kvm
-      veewee vbox         # Subcommand for virtualbox
-      veewee version      # Prints the Veewee version information
-
-### Using veewee as a vagrant plugin
-The second way is to use it a vagrant plugin. Veewee registeres itself as a subcommand 'basebox'
-
-    $ vagrant basebox
-    Usage: vagrant basebox <command> [<args>]
-
-    Available subcommands:
-         build
-         define
-         destroy
-         export
-         halt
-         list
-         ostypes
-         ssh
-         templates
-         undefine
-         up
-
-    For help on any individual command run `vagrant basebox COMMAND -h`
-
-## Available commands
-
-The following command are available: change the vbox to fusion or kvm if you want to use a different <provider>
-
-    Tasks:
-      veewee vbox build [BOX_NAME]             # Build box
-      veewee vbox define [BOXNAME] [TEMPLATE]  # Define a new basebox starting fr...
-      veewee vbox destroy [BOXNAME]            # Destroys the basebox that was built
-      veewee vbox halt [BOXNAME]               # Activates a shutdown on the basebox
-      veewee vbox help [COMMAND]               # Describe subcommands or one spec...
-      veewee vbox list                         # Lists all defined boxes
-      veewee vbox ostypes                      # List the available Operating Sys...
-      veewee vbox ssh [BOXNAME] [COMMAND]      # Shows SSH information
-      veewee vbox templates                    # List the currently available tem...
-      veewee vbox undefine [BOXNAME]           # Removes the definition of a base...
-      veewee vbox up [BOXNAME]                 # Starts a Box
-      veewee vbox validate [NAME]              # Validates a box against vagrant ...
-
-## Non-Vagrant usage
-A typical cycle would be:
-
-  $ veewee vbox define 'mybuntu' 'ubuntu-10.10-amd64'
-  $ veewee vbox build 'myubuntu'
-  $ veewee vbox ssh 'myubuntu'
-  $ veewee vbox halt 'myubuntu'
-  $ veewee vbox up 'myubuntu'
-  $ veewee vbox export 'myubuntu'
-
-## Vagrant usage
-
-A typical cycle would be:
-
-    $ vagrant basebox define 'myubuntu' 'ubuntu-10.10-amd64'
-    $ vagrant basebox  build 'myubuntu'
-    $ vagrant basebox  export 'myubuntu'
-
-    $ vagrant basebox add 'myubuntu' 'myubuntu.box'
-    $ vagrant init 'mybuntu'
-    $ vagrant up
-    $ vagrant ssh
-
-## Exporting a vm
-The export format depends on the provider:
-
-- fusion : exports to an 'ova' file
-- kvm : export to a raw '.img' file
-- vbox: exports to a '.box' format (for use in vagrant)

data/doc/template.md

@@ -1,153 +0,0 @@
-# Veewee Template
-
-## Listing available templates
-
-Veewee provides templates for a lot of different os-es.
-
-To see all the templates provided:
-
-    veewee vbox templates
-
-    The following templates are available:
-    veewee vbox define '<box_name>' 'archlinux-i386'
-    veewee vbox define '<box_name>' 'archlinux-i386-netboot'
-    veewee vbox define '<box_name>' 'archlinux-x86_64'
-    veewee vbox define '<box_name>' 'archlinux-x86_64-netboot'
-    veewee vbox define '<box_name>' 'CentOS-4.8-i386'
-    veewee vbox define '<box_name>' 'CentOS-5.5-i386-netboot'
-    veewee vbox define '<box_name>' 'CentOS-5.5-x86_64-netboot'
-    veewee vbox define '<box_name>' 'CentOS-5.6-i386'
-    veewee vbox define '<box_name>' 'CentOS-5.6-i386-netboot'
-    veewee vbox define '<box_name>' 'CentOS-5.6-x86_64-netboot'
-    veewee vbox define '<box_name>' 'CentOS-5.6-x86_64-netboot-packages'
-    veewee vbox define '<box_name>' 'CentOS-5.7-i386-netboot'
-    veewee vbox define '<box_name>' 'CentOS-5.7-x86_64-netboot'
-    veewee vbox define '<box_name>' 'CentOS-5.8-i386'
-    veewee vbox define '<box_name>' 'CentOS-5.8-i386-netboot'
-    veewee vbox define '<box_name>' 'CentOS-5.8-x86_64'
-    veewee vbox define '<box_name>' 'CentOS-5.8-x86_64-netboot'
-    veewee vbox define '<box_name>' 'CentOS-6.0-i386'
-    veewee vbox define '<box_name>' 'CentOS-6.0-i386-netboot'
-    veewee vbox define '<box_name>' 'CentOS-6.0-x86_64'
-    veewee vbox define '<box_name>' 'CentOS-6.0-x86_64-minimal'
-    veewee vbox define '<box_name>' 'CentOS-6.0-x86_64-netboot'
-    veewee vbox define '<box_name>' 'CentOS-6.1-x86_64-minimal'
-    veewee vbox define '<box_name>' 'CentOS-6.1-x86_64-netboot'
-    veewee vbox define '<box_name>' 'CentOS-6.2-i386-minimal'
-    veewee vbox define '<box_name>' 'CentOS-6.2-x86_64-minimal'
-    veewee vbox define '<box_name>' 'CentOS-6.2-x86_64-netboot'
-    veewee vbox define '<box_name>' 'CentOS-6.3-i386-minimal'
-    veewee vbox define '<box_name>' 'CentOS-6.3-x86_64-minimal'
-    veewee vbox define '<box_name>' 'Debian-5.0.8-amd64-netboot'
-    veewee vbox define '<box_name>' 'Debian-5.0.8-i386-netboot'
-    veewee vbox define '<box_name>' 'Debian-5.0.10-amd64-netboot'
-    veewee vbox define '<box_name>' 'Debian-5.0.10-i386-netboot'
-    veewee vbox define '<box_name>' 'Debian-6.0.3-amd64-netboot'
-    veewee vbox define '<box_name>' 'Debian-6.0.3-i386-netboot'
-    veewee vbox define '<box_name>' 'Debian-6.0.4-amd64-netboot'
-    veewee vbox define '<box_name>' 'Debian-6.0.4-i386-netboot'
-    veewee vbox define '<box_name>' 'Debian-6.0.5-amd64-netboot'
-    veewee vbox define '<box_name>' 'Debian-6.0.5-i386-netboot'
-    veewee vbox define '<box_name>' 'Debian-6.0.6-amd64-netboot'
-    veewee vbox define '<box_name>' 'Debian-6.0.6-i386-netboot'
-    veewee vbox define '<box_name>' 'Debian-7.0-b2-i386-netboot'
-    veewee vbox define '<box_name>' 'Debian-7.0-b3-amd64-netboot'
-    veewee vbox define '<box_name>' 'Fedora-14-amd64'
-    veewee vbox define '<box_name>' 'Fedora-14-amd64-netboot'
-    veewee vbox define '<box_name>' 'Fedora-14-i386'
-    veewee vbox define '<box_name>' 'Fedora-14-i386-netboot'
-    veewee vbox define '<box_name>' 'Fedora-15-i386'
-    veewee vbox define '<box_name>' 'Fedora-15-i386-netboot'
-    veewee vbox define '<box_name>' 'Fedora-15-x86_64'
-    veewee vbox define '<box_name>' 'Fedora-15-x86_64-netboot'
-    veewee vbox define '<box_name>' 'Fedora-16-i386'
-    veewee vbox define '<box_name>' 'Fedora-16-x86_64'
-    veewee vbox define '<box_name>' 'Fedora-16-x86_64-netboot'
-    veewee vbox define '<box_name>' 'Fedora-17-i386'
-    veewee vbox define '<box_name>' 'Fedora-17-x86_64'
-    veewee vbox define '<box_name>' 'Fedora-18-i386'
-    veewee vbox define '<box_name>' 'Fedora-18-x86_64'
-    veewee vbox define '<box_name>' 'freebsd-8.2-experimental'
-    veewee vbox define '<box_name>' 'freebsd-8.2-pcbsd-i386'
-    veewee vbox define '<box_name>' 'freebsd-8.2-pcbsd-i386-netboot'
-    veewee vbox define '<box_name>' 'freebsd-9.0-RELEASE-amd64'
-    veewee vbox define '<box_name>' 'funtoo-latest-generic_64-stable'
-    veewee vbox define '<box_name>' 'funtoo-latest-x86_64'
-    veewee vbox define '<box_name>' 'gentoo-latest-i386-experimental'
-    veewee vbox define '<box_name>' 'gentoo-latest-x86_64-experimental'
-    veewee vbox define '<box_name>' 'openbsd50_amd64'
-    veewee vbox define '<box_name>' 'openbsd50_i386'
-    veewee vbox define '<box_name>' 'openindiana-148-ai-x86'
-    veewee vbox define '<box_name>' 'openSUSE-11.4-DVD-i586'
-    veewee vbox define '<box_name>' 'openSUSE-11.4-DVD-x86_64'
-    veewee vbox define '<box_name>' 'opensuse-11.4-i386-experimental'
-    veewee vbox define '<box_name>' 'openSUSE-11.4-NET-i586'
-    veewee vbox define '<box_name>' 'openSUSE-11.4-NET-x86_64'
-    veewee vbox define '<box_name>' 'openSUSE-12.1-DVD+NET-i586'
-    veewee vbox define '<box_name>' 'openSUSE-12.1-DVD+NET-x86_64'
-    veewee vbox define '<box_name>' 'OracleLinux-6.3-x86_64-DVD'
-    veewee vbox define '<box_name>' 'scientificlinux-6.1-i386-netboot'
-    veewee vbox define '<box_name>' 'scientificlinux-6.1-x86_64-netboot'
-    veewee vbox define '<box_name>' 'scientificlinux-6.2-i386-netboot'
-    veewee vbox define '<box_name>' 'scientificlinux-6.2-x86_64-netboot'
-    veewee vbox define '<box_name>' 'scientificlinux-6.3-i386-netboot'
-    veewee vbox define '<box_name>' 'scientificlinux-6.3-x86_64-netboot'
-    veewee vbox define '<box_name>' 'SLES-11-SP1-DVD-i586-GM'
-    veewee vbox define '<box_name>' 'SLES-11-SP1-DVD-x86_64-GM'
-    veewee vbox define '<box_name>' 'solaris-11-express-i386'
-    veewee vbox define '<box_name>' 'Sysrescuecd-2.0.0-experimental'
-    veewee vbox define '<box_name>' 'ubuntu-10.04.2-amd64-netboot'
-    veewee vbox define '<box_name>' 'ubuntu-10.04.2-server-i386-netboot'
-    veewee vbox define '<box_name>' 'ubuntu-10.04.3-server-amd64'
-    veewee vbox define '<box_name>' 'ubuntu-10.04.3-server-amd64-alt'
-    veewee vbox define '<box_name>' 'ubuntu-10.04.3-server-i386'
-    veewee vbox define '<box_name>' 'ubuntu-10.04.4-server-amd64'
-    veewee vbox define '<box_name>' 'ubuntu-10.04.4-server-i386'
-    veewee vbox define '<box_name>' 'ubuntu-10.10-server-amd64'
-    veewee vbox define '<box_name>' 'ubuntu-10.10-server-amd64-netboot'
-    veewee vbox define '<box_name>' 'ubuntu-10.10-server-i386'
-    veewee vbox define '<box_name>' 'ubuntu-10.10-server-i386-netboot'
-    veewee vbox define '<box_name>' 'ubuntu-11.04-server-amd64'
-    veewee vbox define '<box_name>' 'ubuntu-11.04-server-i386'
-    veewee vbox define '<box_name>' 'ubuntu-11.10-server-amd64'
-    veewee vbox define '<box_name>' 'ubuntu-11.10-server-amd64-ishaya'
-    veewee vbox define '<box_name>' 'ubuntu-11.10-server-amd64-ruby192'
-    veewee vbox define '<box_name>' 'ubuntu-11.10-server-amd64-rvm'
-    veewee vbox define '<box_name>' 'ubuntu-11.10-server-i386'
-    veewee vbox define '<box_name>' 'ubuntu-12.04.1-server-amd64'
-    veewee vbox define '<box_name>' 'ubuntu-12.04.1-server-amd64-packages'
-    veewee vbox define '<box_name>' 'ubuntu-12.04.1-server-i386'
-    veewee vbox define '<box_name>' 'ubuntu-12.04.1-server-i386-packages'
-    veewee vbox define '<box_name>' 'ubuntu-12.10-server-amd64'
-    veewee vbox define '<box_name>' 'ubuntu-12.10-server-amd64-packages'
-    veewee vbox define '<box_name>' 'ubuntu-12.10-server-i386'
-    veewee vbox define '<box_name>' 'ubuntu-12.10-server-i386-packages'
-    veewee vbox define '<box_name>' 'ubuntu-8.04.4-server-amd64'
-    veewee vbox define '<box_name>' 'ubuntu-8.04.4-server-i386'
-    veewee vbox define '<box_name>' 'windows-2008R1-serverstandard-amd64'
-    veewee vbox define '<box_name>' 'windows-2008R1-serverweb-amd64'
-    veewee vbox define '<box_name>' 'windows-2008R1-serverwebcore-amd64'
-    veewee vbox define '<box_name>' 'windows-2008R1-serverweb-i386'
-    veewee vbox define '<box_name>' 'windows-2008R2-amd64'
-    veewee vbox define '<box_name>' 'windows-2008R2-serverstandard-amd64'
-    veewee vbox define '<box_name>' 'windows-2008R2-serverstandard-amd64-winrm'
-    veewee vbox define '<box_name>' 'windows-2008R2-serverweb-amd64'
-    veewee vbox define '<box_name>' 'windows-2008R2-serverwebcore-amd64'
-    veewee vbox define '<box_name>' 'windows-7-enterprise-amd64'
-    veewee vbox define '<box_name>' 'windows-7-enterprise-amd64-winrm'
-    veewee vbox define '<box_name>' 'windows-7-enterprise-i386'
-    veewee vbox define '<box_name>' 'windows-7-premium-amd64'
-    veewee vbox define '<box_name>' 'windows-7-professional-amd64'
-    veewee vbox define '<box_name>' 'windows-7sp1-ultimate-amd64'
-    veewee vbox define '<box_name>' 'windows-7-ultimate-amd64'
-    veewee vbox define '<box_name>' 'windows-8-preview-amd64'
-
-
-## Structure
-Templates have the same structure as a <definition> but are provided by veewee as templates for definitions.
-
-## Extending templates
-
-- fork veewee
-- add a new template under the templates directory
-- send me a pull request

data/lib/veewee/provider/vmfusion/box/export_ova.rb

@@ -1,49 +0,0 @@
-require 'tempfile'
-
-module Veewee
-  module Provider
-    module Vmfusion
-      module BoxCommand
-        # This function 'exports' the box based on the definition
-        def export_ova(options)
-          debug="--X:logToConsole=true --X:logLevel=\"verbose\""
-          debug=""
-          flags="--compress=9"
-
-          if File.exists?("#{name}.ova")
-            if options["force"]
-              env.logger.debug("#{name}.ova exists, but --force was provided")
-              env.logger.debug("removing #{name}.ova first")
-              FileUtils.rm("#{name}.ova")
-              env.logger.debug("#{name}.ova removed")
-            else
-              raise Veewee::Error, "export file #{name}.ova already exists. Use --force option to overwrite."
-            end
-          end
-
-          # Need to check binary first
-          if self.running?
-            # Wait for the shutdown to complete
-            begin
-              Timeout::timeout(20) do
-                self.halt(options)
-                status=self.running?
-                unless status
-                  return
-                end
-                sleep 4
-              end
-            rescue TimeoutError::Error => ex
-              raise Veewee::Error,ex
-            end
-          end
-
-          # before exporting the system needs to be shut down
-
-          # otherwise the debug log will show - The specified virtual disk needs repair
-          shell_exec("#{File.dirname(vmrun_cmd).shellescape}/ovftool/ovftool.bin #{debug} #{flags} #{vmx_file_path.shellescape} #{name}.ova")
-        end
-      end
-    end
-  end
-end