Baking up a virtual development environment

A quick introduction to the tools I used at Just Eat to make the life of new joiners easier, especially, for those who don't necessarily have the ops skills required.

Transcript

1. Baking up a Virtual Development Environment Packer + vagrant + VirtualBox
2. Marco De Bortoli (Debo) I work here I contribute(d) here I tweet here @__debo
3. Why do we need or use virtualisation?
4. We need or use virtualisation • Software requirements • Reproducible environment • Portable environment • Testing environment • Maximise productivity • Maximise flexibility
5. What problems does virtualisation help avoid?
6. Virtualisation helps avoid • Skills requirement • Additional software requirements • Increased basic hardware requirements • Additional licensing • It works on my machine
7. What virtualisation solution have you used?
8. I used
9. Let me introduce Vagrant
10. Overview Vagrant Vagrant is a tool for building and distributing virtualised development environment • Standalone self-contained ruby application (no gem dependency hell) • Provides simple interface for VirtualBox • Interacts with VirtualBox API • Extendable through a plug-in interface
11. Features Vagrant • Automated creation of VMs • Automated provisioning of VMs • Scripted configuration of VM properties • Simple interface to manage virtual environment • Reduce setup to a single command • Scripted configuration of shared file system • Scripted configuration of network
12. Automated provisioning Vagrant • Shell • CFEngine • Chef • Puppet • Ansible • Salt • Docker • Custom
13. Scripted configuration of VM properties Vagrant • CPUs • RAM • Network interfaces • Ports • Shares
14. Simple interface to manage virtual environment Vagrant • vagrant status • vagrant suspend • vagrant resume • vagrant halt • vagrant reload • vagrant ssh/rdp
15. Reduce setup to a single command Vagrant • vagrant up • vagrant provision • vagrant destroy
16. Goods Vagrant • Integrates well with well known platform • Isolates dependencies and configuration in a disposable and consistent environment • Multi-Machine • You don’t have to renounce to use your favourite tools
17. Bads Vagrant • Base boxes maintainability
18. Base boxes Vagrant • Simple VM images • Distribution and Architecture specific • Setup with a minimal set of packages • Includes a common SSH key for access or appropriate WinRM setup • Includes VirtualBox tools
19. Welcome to Packer
20. Overview Packer Packer is a tool for creating machine and container images for multiple platforms from a single source configuration. • Standalone self-contained ruby application (no gem dependency hell) • Automate the otherwise manual process of running setups
21. Features Packer • Automated creation of the base images • Scripted configuration of base image properties • Reduce build to a single command • Automated provisioning of the base images • Builds on pretty much anything you can think about
22. Provisioners
23. Choose a specific provisioning solution Provisioners • External dependency • Familiarity • Compatibility • Simplicity • Ease of learning • Extensibility • Personal preference • Cost
24. Nice but, where is the code?
25. What else
26. File sharing • Multiple shared locations • Support for NFS (Dependent upon Host) • User your preferred editor • No need to synchronise files For who needs it
27. Want to know more?
28. Resources Resources • https://docs.vagrantup.com/v2/ • https://packer.io/docs • https://hashicorp.com/ • https://technet.microsoft.com/en-us/library/hh824950.aspx • https://github.com/joefitzgerald/packer-windows
29. Questions?
30. We are hiring! Come talk to us.
31. Thank You!