Vagrant
•Download as KEY, PDF•
18 likes•3,173 views
Many of us deploy to systems which are completely different from the systems we develop on, and can be difficult to set up particularly if there are a lot of moving pieces in your setup. These could be things like message queuing systems, various databases or specific versions of scripting languages such as ruby. This makes it a very time intensive process to bring new people up to speed on your projects, and to get systems set up right the first time. What if you could have a system that would launch a virtual environment, provision and run all of your systems's various components, be repeatable and fit on a thumb drive? Vagrant allows this by putting a ruby DSL on top of Oracle's VirtualBox API. It allows you to set up and provision your servers using Chef or Puppet, and to reuse those scripts on your real production environment if you want. This makes your server infrastructure version controlled just like your application code. We will go through a setup of a Vagrant instance and show how using shared folders you can develop locally, but be developing on your "local cloud", your running Vagrant instance.
Recommended
More Related Content
Viewers also liked
More from Mike Hagedorn
Recently uploaded
Recently uploaded (20)
Vagrant
- 1. Vagrant Building Virtual Development Environments With Vagrant
- 4. Vagrant Building Virtual Development Environments With Vagrant
- 5. Vagrant Building Virtual Development Environments With Vagrant Stop Cutting Cords!
- 6. Mike Hagedorn • @mwhagedorn • mike@silverchairsolutions.com
- 7. Vagrant Agenda • Why Vagrant? • Vagrant Hello World • Provisioning and Vagrant • Sample Rails App • Other cool stuff
- 8. $ git clone git://.../website.git $ rails s In a perfect world...
- 9. $ git clone git://.../website.git $ ... $ (magic occurs) $ ... $ rails s On my planet...
- 10. $ git clone git://.../website.git $ ... $ (magic occurs) Huh? $ ... $ rails s On my planet...
- 13. The Issues • No Isolation • Not Repeatable • Not Reliable
- 15. Resolved Issues • Isolation • Application Code Silo’ed • Repeatable • Server Configuration Is Controlled • Reliable • Server Configuration is Proven
- 16. Other Benefits • Bring New People Up To Speed FAST! • Server Configuration is Source Controlled • Easier What-If scenarios With Your System
- 17. Vagrant • By Mitch Hashimoto and John Bender (1/2010 first commit) • Leverages Virtual Box • Free Virtualization Solution from Oracle • Provisioning via Chef or Puppet • Others via extension API • Shared Folders • SSH Access
- 18. Installation $ gem install vagrant $ vagrant box add base http://files.vagrantup.com/lucid32.box $ vagrant init $ vagrant up
- 19. Installation $ gem install vagrant $ vagrant box add base http://files.vagrantup.com/lucid32.box $ vagrant init $ vagrant up Downloads, saves as ‘base’ (other distros vagrantboxes.es)
- 20. Installation $ gem install vagrant $ vagrant box add base http://files.vagrantup.com/lucid32.box $ vagrant init $ vagrant up Create Vagrantfile
- 21. Installation $ gem install vagrant $ vagrant box add base http://files.vagrantup.com/lucid32.box $ vagrant init $ vagrant up Launches Instance
- 22. Vagrantfile Vagrant::Config.run do |config| config.vm.box = "base" end
- 23. Demo
- 24. Other Commands $ vagrant box list $ vagrant box remove <NAME> $ vagrant up | halt #launch/shutdown $ vagrant destroy #shutdown and delete image $ vagrant suspend | resume #pause and restart
- 25. Provisioning “Logging In To The Server Is A Smell”
- 27. Customizing Provisioners Vagrant::Config.run do |config| config.vm.box = "lucid32" config.vm.forward_port ‘web’, 80,4567 # Enable and configure the chef solo provisioner config.vm.provision :chef_solo do |chef| # We're going to use a local copy of the cookbooks chef.cookbooks_path = "cookbooks" # Tell chef what recipe to run. In this case, the `vagrant_main` recipe # does all the magic. chef.add_recipe("vagrant_main") chef.json.merge!({ :my_recipe =>{ "foo" =>”bar” }) end end Per Recipe Customization
- 28. Provisioning • Chef • Chef-Solo • Puppet • Custom
- 29. Provisioning • Chef • Chef-Solo • Puppet • Custom
- 30. Chef • Abstracts away configuration details for platform • Provides DSL for managing resources • Idempotent
- 31. Chef • Ruby-based infrastructure configuration management tool • Codifies best practices • Installation components called “recipes” • Collection of recipes called “cookbook” • Server-based and standalone
- 32. Chef • “Recipes for Chef are like RubyGems for Ruby”
- 33. Chef Cookbook
- 34. Vagrantfile Vagrant::Config.run do |config| config.vm.box = "lucid32" config.vm.forward_port ‘web’, 80,4567 # Enable and configure the chef solo provisioner config.vm.provision :chef_solo do |chef| # We're going to use a local copy of the cookbooks chef.cookbooks_path = "cookbooks" # Tell chef what recipe to run. In this case, the `vagrant_main` recipe # does all the magic. chef.add_recipe("vagrant_main") end end Maps VM Port
- 35. Vagrantfile Vagrant::Config.run do |config| config.vm.box = "lucid32" config.vm.forward_port ‘web’, 80,4567 # Enable and configure the chef solo provisioner config.vm.provision :chef_solo do |chef| # We're going to use a local copy of the cookbooks chef.cookbooks_path = "cookbooks" # Tell chef what recipe to run. In this case, the `vagrant_main` recipe # does all the magic. chef.add_recipe("vagrant_main") end end Recipe Metadata Location
- 36. Vagrantfile Vagrant::Config.run do |config| config.vm.box = "lucid32" config.vm.forward_port ‘web’, 80,4567 # Enable and configure the chef solo provisioner config.vm.provision :chef_solo do |chef| # We're going to use a local copy of the cookbooks chef.cookbooks_path = "cookbooks" # Tell chef what recipe to run. In this case, the `vagrant_main` recipe # does all the magic. chef.add_recipe("vagrant_main") end end Which Recipe To Invoke
- 37. Demo
- 39. Other Commands $ vagrant provision Only Runs Provisioning Step
- 40. Multi-VM Setups Vagrant::Config.run do |config| config.vm.define :web do |web_config| web_config.vm.box = "web" web_config.vm.forward_port("http", 80, 8080) web_config.vm.network("192.168.1.10") end config.vm.define :db do |db_config| db_config.vm.box = "db" db_config.vm.forward_port("db", 3306, 3306) db_config.vm.network("192.168.1.11") end end
- 41. Packaging Own Box • Allows you to share a provisioned box
- 42. $ vagrant package --include Vagrantfile $ vagrant box add tst package.box #other person adds Create Box and Add It
- 43. Mike Hagedorn • @mwhagedorn • mike@silverchairsolutions.com • https://github.com/mwhagedorn/lsrc • spkr8.com/t/7809 Resources • http://vagrantup.com • http://vagrantbox.es • http://wiki.opscode.com/display/chef/Home • http://community.opscode.com
Editor's Notes
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- works on my machine is not a valid response\n\n
- \n
- \n
- \n
- shared folders - map a directory in your working directory to a place on the virtual file system\nuses share folders of vb by default, can use NFS if you have lots of files\nSSH access - can ssh to it from anywhere if you export and use the \n
- vagrant boxes download to ~./vagrant/boxes\ndownload once, is base for other vagrant projects, each project leaves box unmodified\n\n
- vagrant boxes download to ~./vagrant/boxes\ndownload once, is base for other vagrant projects, each project leaves box unmodified\n\nLucid32 is a Unbuntu 10.04 image\nother boxes look to vagrantbox.es\n
- explain what a vagrantfile is\nlike a rails generator\n
- imports base box HD into VB\noptionally it wil provision if its enabled\n\n
- \n
- ssh to box\nls /vagrant\ncreate a file on local\nshow it\nshow that its running inside of VB\nvagrant destroy\nmapping how it works\npossible to use NFS, some people say default sharing works not so well on big files\n\n
- explain\ninterestingly no rename\n\n
- not sure who said this, Zed Shaw perhaps\n
- by default vagrant provisioning is disabled\n\n
- you can do chef.json = in new build (chef only)\nmost examples are chef only, problem because its like italian/spanish.. similar but not same\n
- \n
- \n
- \n
- \n
- Cookbooks bundle recipes that describe how you want a part of your server to be configured along with the assets they need, such as configuration files or templates.\n
- \n
- \n
- \n
- \n
- use blink tag\n\n
- use TM\n
- vagrant reload if you have changed the cookbook path\n
- \n
- creates a package.box\n
- creates a file package.box in the same directory\nShoot for less than 500MB, otherwise too unwiedly, use tips on vagrantup.com\nDefault Memory Allocation set to 360MB\n
- \n