Vagrant at LA Ruby

Vagrant
Virtualize your development environment.

Thursday, September 9, 2010

Mitchell Hashimoto
github.com/mitchellh
twitter.com/mitchellh


$ git clone git://.../website.git
...
$ ???WTF!#A@#)!???
...
$ script/server
...


User space
Browser Editor
Queue Other
Music Server Server

Web DB App
IRC IM
Server Server Server

Operating System


BIG PROBLEMS


BIG PROBLEMS
1. No isolation (Oh sorry, is that Tweetie Server Edition™?)


BIG PROBLEMS

2. Not repeatable (That README ain’t gonna run itself)


BIG PROBLEMS

2. Not repeatable (That README ain’t gonna run itself)

3. No guarantees (But it works on my computer!!)


VIRTUALIZATION!

EC2, Slicehost, Linode, Xen, KVM, ...


User space
Virtualized OS

Browser Editor
Web DB App
Server Server Server

IRC IM

Operating System


PROBLEMS SOLVED


PROBLEMS SOLVED
1. Isolation


PROBLEMS SOLVED
1. Isolation

2. Repeatable


PROBLEMS SOLVED
1. Isolation

2. Repeatable

3. Guarantees


BUSINESS BENEFITS


BUSINESS BENEFITS
• Lower resource on-boarding time


BUSINESS BENEFITS
• Version controlled server infrastructure


BUSINESS BENEFITS
• Version controlled server infrastructure
• Designers get up and running in minutes


WHY NOW?
(Why haven’t we been doing this all along?)


WHY NOW?

• Big companies have been!


WHY NOW?

• Only recently possible on local machines


WHY NOW?

๏ Low RAM cost (4 GB standard, 8 GB quickly coming)


WHY NOW?

๏ Low RAM cost (4 GB standard, 8 GB quickly coming)

๏ Desktop virtualization API


HIGH LEVEL OVERVIEW
‣ Describe environment via versionable Vagrantfile

‣ Manage virtual machine lifecycle

‣ Share folder from host to guest via NFS

‣ Provide SSH access to instance

‣ Provision instance using Chef, Puppet, etc.

‣ Manage host/guest networking


Vagrantﬁle
• Describes the virtual machine environment in code
๏ One per project

๏ Commit to version control

๏ Pure Ruby - Limitless conﬁguration.


Vagrantﬁle
Vagrant::Config.run do |config|
config.vm.box = "lucid32"
end


Virtual Machine Lifecycle
‣ vagrant binary

‣ Completely managed from creation to destruction

๏ (and creation... and destruction... and creation... and so on!)

$ vagrant up
$ vagrant halt
$ vagrant suspend
$ vagrant destroy
$ vagrant reload
$ vagrant ssh
$ vagrant --help


Shared Folders via NFS
‣ File changes on host are immediately mirrored in the VM

‣ Continue using your favorite editor on your machine!

‣ By default mounted to /vagrant in VM


DEMO


Onto the good stuff...
(let’s make it useful)


Provisioning
• Use Chef, Puppet, Bash, etc. to provision your VM
๏ Repeatable! (BIG Problem #2, remember?)

๏ Use the same tools as production


Provisioning

config.vm.provisioner = :chef_solo
end


Networking
• Assign an IP to your VM
๏ Access VM using your own browser


Networking

config.vm.provisioner = :chef_solo
config.vm.network("33.33.33.10")
end


Other stuff...
(no demos here, you can experiment)


Packaging
• Package built development environments
๏ vagrant package

๏ Distributable

๏ Minimize setup time


Multi-VM
• Represent multi-server environments
๏ e.g. web + db + utility


Multi-VM
config.vm.define :web do |web|
# ...
end

config.vm.define :db do |db|
# ...
end
end


Rake Integration
• Use vagrant as a library
๏ Invoke command line actions

๏ Custom SSH commands


Rake Integration

require 'vagrant'

desc "Restart the web application"
task :restart do
env = Vagrant::Environment.load!
env.ssh.execute do |ssh|
ssh.exec!("touch /vagrant/tmp/restart.txt")
end
end


Plugins (0.6)
• Extend Vagrant using a supported API
• Add new commands to vagrant binary
• Add new conﬁguration options
• Modify existing commands
• e.g. vagrant rake - Just pass through arguments to rake
on the VM.


Review

• Continue using your existing development tools
• Run your web app in a VM
• VM setup ﬁle (Vagrantﬁle) in version control


LOSE NOTHING. GAIN EVERYTHING.


Vagrant IN ACTION
Virtualize your development environment.


• Vagrant for all projects since March
• Around 15 to 20 developers using it all day every day
• Unexpected: Unique testing not possible before


• All Rails projects since July on Vagrant
• Massive reduction in on-boarding difﬁculty for new hires
• Looking into using it for Java-based projects in the near future


• Multi-VM setup (web + db + ﬂash media server)
• Solved: No easy way to emulate FMS on Mac.
• Forced devops good practices
• Example of successful distribution of boxes


About the Project
• Current release: 0.5.4
• Started development in January. First release in March.
• 0.6 development well under way:
๏ 179 commits, 226 ﬁles changed, 4081 lines added, 5730 lines deleted.

๏ Aiming for release in about 4 weeks.

๏ Biggest release yet


Getting Started + More Info
• Website: vagrantup.com
• IRC: #vagrant on Freenode
• Github: http://github.com/mitchellh/vagrant


Vagrant at LA Ruby

Recomendados

Recomendados

Mais conteúdo relacionado

Destaque

Destaque (8)

Semelhante a Vagrant at LA Ruby

Semelhante a Vagrant at LA Ruby (20)

Último

Último (20)

Vagrant at LA Ruby