While heading back home from DrupalCon Munich after 4 days of good interaction with lots of Drupal folks.
I realized to my big suprise that there are a lot of people using Vagrant to make sure that developers are not working on platforms they invented their own. Lots of people have realized that “It works on my computer” is not something they want to hear from a developer and are reaching out to give them viable solutions to work on shared and reproducible solutions.
They contain a bunch of puppet modules that install and configure these tools. (Note that they mostly consist of
of git submodules to other puppet module repositories.
I’ve just finished presenting my talk on how I currently work on Puppet modules at Puppetcamp here in Edinburgh where I’ve been for the week talking on both FlossUK 2012 and Puppetcamp.
With @dancarley and @patrickebois just discussing the origin of the name of Veewee I figured I still had that piece of documentation I wrote up for myselve flying around …
So with no other reason than having my docs mirrored on the internet .
1. gem install veewee
1. veewee templates
shows you what templates we have around ..
1. $veewee init natty ubuntu-11.04-server-amd64
2. Init a new box natty, starting from template ubuntu-11.04-server-amd64
3. The basebox 'natty' has been successfully created from the template ''ubuntu-11.04-server-amd64'
4. You can now edit the definition files stored in definitions/natty
5. or build the box with:
6. vagrant basebox build 'natty'
As noted this will generate the definition for your natty box,
It will create a definition.rb file which describes your box.
A preseed (or kickstart or similar file) and a postinstall file
Don’t you just love Ruby errors … like the one below ?
Don’t they almost make Java stack traces look readable ?
57 lines of jibberish … where all I wanted to read was “VirtualBox in error state, check gui”
People like Randall Hanssen deserve much more visibility .. they do understand how to write a good error message and there are lots of projects that need improvement there.
Anywhow… vagrant had suddenly stopped working on me with the error below
I was testing some MySQL puppet modules on my Vagrant box earlier this week and one of them required augeas.
I kept running into “Could not find a default provider for augeas”, however all the appropriate augeas , augeas-lib and ruby-augeas packages were installed. I inspected the different ruby directories and the files were perfectly in /usr/lib/ruby/site_ruby/1.8 where I expected them.
With all the files seemd to be in the right place, my next option was to strace a small ruby script that included augeas, guess what that showed ..
I have had most of my test environment, aka puppetmasters, test mysql setups etc running in KVM for the past couple of years .. (yes I`m still using a lot of Xen in production environments, but we’ve also been using KVM for a while already .. it’s a good mix) , Virtual box has always been the lesser loved Virtualization platform , however while playing more and more with Vagrant Up I realized I needed to convirt some boxen (e.g my PuppetMaster) to Virtualbox, and google was really no good help(most people seem to go the other way , or want to use some proprietary tools )