Christian Trabold

Developer in Frankfurt, Germany
Tags: Deployment, Devops, TYPO3

Rubygem for managing
Virtual Machines

VirtualBox-API

VirtualBox-API

+ Config Management

VirtualBox-API

+ Config Management

= SuperPowers!

We need a standard!

Shell scripts are not the solution

Don't try to make your shell scripts more flexible

Learn Chef or Puppet

Flexible out-of-the-box

Don't build production-like environments

Forget MacPorts, Homebrew and friends for real DEV

Get real with Virtualization!

Download VirtualBox

http://www.virtualbox.org

Install Vagrant

$ (sudo) gem install vagrant

Add a basebox

$ vagrant box add basebox \
  http://files.vagrantup.com/lucid64.box

Basebox = Mother of all VMs

Each Virtual Machine
is based on a basebox

Initialize workspace

$ cd ~/workspace
$ vagrant init basebox

Customize Vagrantfile

$ cat ./Vagrantfile
Vagrant::Config.run do |config|
  config.vm.box = "basebox"
  config.vm.network "192.168.56.10"
  config.vm.forward_port "http", 3000, 3000
  config.vm.share_folder "v-data", "/data", "../data"
end

Start up a Virtual Machine

vagrant up

Share code with rsync or shared folders .notes vagrant ssh connects through NAT to the VM

Log in

vagrant ssh

et voilá!

You got your VirtualMachine up and running!

Deploy code eg. with Capistrano

 cap deploy

or shared folders

$ cat ./Vagrantfile
Vagrant::Config.run do |config|
  config.vm.share_folder "v-data", "/data", "../data"
end

Use port forwarding

$ cat ./Vagrantfile
Vagrant::Config.run do |config|
  config.vm.forward_port "http", 3000, 3000
end

Or enter a static IP

$ cat ./Vagrantfile
Vagrant::Config.run do |config|
  config.vm.network "192.168.56.10"
end

Customize VMs

eg. with Chef cookbooks

$ cat ./Vagrantfile
…
config.vm.provision :chef_solo do |chef|
  chef.cookbooks_path = "cookbooks"
  chef.add_recipe "rails"
  chef.add_role "web"
end

Run Chef on the VM

$ vagrant provision

This runs chef-solo

Share a VM with colleagues

$ vagrant box repackage mybasebox

Create your
own baseboxes

$ gem install veewee
$ vagrant basebox define \
  'mybasebox' \
  'ubuntu-10.10-server-i386'

Share / search baseboxes

http://vagrantbox.es

Excellent documentation

http://vagrantup.com/docs/

You have to learn a lot:

• Understand OS & Network
• Write cookbooks
• Distribute Vagrant boxes

Devs have to learn Ops stuff

Devs have their way of setup

When talking to management, marketing, sysadmins, other developers really strange things happen.

Ops have to learn Dev stuff

Grows DevOps culture

… but it takes a while :)

Create Prototypes

A working example is worth 1000 discussions

Workshops

Involve people as much as possible!

Sharing is caring

Slow Hardware

4VMs parallel = hot!

Heavy Assets

~10 GB

Networking fails

/etc/resolv.conf #wtf

Upgrade your machines

RAM and HDs are cheap

Extend to the Cloud

https://github.com/jedi4ever/mccloud

Ask Ops for Networking issues

… or ask @DEVOPS_BORAT

For me Vagrant is

THE DevOps Tool

A perfect playground for new ideas
eg. testing Chef cookbooks

Testing Production
is now much easier

Focus on new challenges

Continuous Delivery, Testing Infrastructure

Thanks!

@ctrabold
http://christian-trabold.de