Reproducible work environments

Transcript

1. Reproducible work environments Jan Schulte - @neinasaservice
2. • Jan Schulte • Backend developer • asquera GmbH
4. Back then
5. • Complete setup installed on your machine • Ruby • Rails • Postgres / MySQL • RabbitMQ • …
6. Developers use different operating systems “Development happens on Mac OS X and we deploy to Ubuntu”
7. • Difficult setup • What happens when something breaks?
8. “Works on my machine”
9. “Then we ship your machine”
10. You started a new project. ! Two months later…
11. – The client from two months ago “We now would like to have feature X implemented”
12. “Works on my machine” but not in production On your machine you have • a different operating system • a different file system • a different configuration (Users, Permissions, Services, …) than in production
13. • You may have different errors on your dev machine than in production • How do you fix issues occurring in production only?
14. Solutions
15. Installed on my dev machine • Text editor / IDE • git • Vagrant • Virtualbox / VMWare
16. It starts with dotfiles • The first thing you clone into your dev environment • Including • git • text editor (vim, Emacs, TextMate, …) • shell • …
17. Vagrant
18. • Reproducible and portable development environments • Vagrantfile describes your machine • vagrant up to start the virtual machine • vagrant destroy when you’re done
19. Disposable environments • Easy recovery when you break something • vagrant destroy -f && vagrant up • Automated setup of development environment with provisioners
20. • Bring DEV closer to PRD environment • Infrastructure changes in version control • Infrastructure setup is documented • Spend less time for setup later on
21. – From Ruby Rogues 192 “It’s effort for one person and the whole team benefits”
22. Example • Environment with multiple machines • Web server • Database server • Message queue server
23. Vagrantfile • Virtual machine image • Network configuration • Shared folders with host system • Provisioning
24. Vagrant.configure(2) do |config|
 config.vm.box = "chef/ubuntu-14.04" config.vm.network "private_network", ip: "192.168.33.10" config.vm.synced_folder "../../My_Project", "/vagrant" config.ssh.forward_agent = true
 config.vm.provision "puppet" do |puppet| puppet.manifests_path = "manifests" puppet.manifest_file = "nodes.pp" puppet.module_path = ["modules"] end end
25. Provisioning
27. • Prepare development box • Run scripts to • Install packages • configure environment (Users, Permissions, Services, …) • Describe the final state you want • Let the provisioner figure out how to accomplish this
28. • Supported provisioners • Shell • Chef • Puppet • and more…
29. Example with shell scripts
30. # -*- mode: ruby -*-
 # vi: set ft=ruby : VAGRANTFILE_API_VERSION = "2" Vagrant.configure(VAGRANTFILE_API_VERSION) do |config| config.vm.box = "chef/ubuntu-14.04" config.vm.provision "shell", path: "provision.sh" end
31. # install a ruby wget http://cache.ruby-lang.org/pub/ruby/2.1/ruby-2.1.5.tar.gz ./configure
 make && make install 
 # Install Postgresql apt-get install postgresql postgresql-contrib service postgresql start
32. Niman
33. Niman • I wrote my own provisioner • https://github.com/schultyy/niman • Vagrant plugin • vagrant plugin install niman • No need to learn a new language • It’s just plain Ruby • Do not use this in production
34. #Nimanfile Niman::Recipe.configure do |config| config.file '/home/bob/hello.txt' do |file| file.content = 'hello from alice’ end config.package do |package| package.name = 'vim' end end
35. # -*- mode: ruby -*-
 # vi: set ft=ruby : VAGRANTFILE_API_VERSION = "2" Vagrant.configure(VAGRANTFILE_API_VERSION) do |config| config.vm.box = "chef/ubuntu-14.04" config.vm.provision "niman" end
36. • http://devchat.tv/ruby-rogues/192-rr-vagrant-with- mitchell-hashimoto • https://www.youtube.com/watch?v=qKb0_13-E9w • http://devchat.tv/ruby-rogues/113-rr-devops-with- nathen-harvey
37. Thank you