Vagrant: How & Why

What is Vagrant? Why do you need it?

Transcript

1. Vagrant: How & Why? A beginners guide to Vagrant
2. What is Vagrant? Vagrant is a tool that allows you create and configure lightweight, reproducible, and portable development environments. Build virtual cloud on your workstation.
3. The problem?
4. It works on my machine (Said by every single engineer/developer)
5. Pre-Vagrant
6. What is Vagrant? Vagrant is a tool that allows you create and configure lightweight, reproducible, and portable development environments. Build virtual cloud on your workstation. Image source: laracast.com
7. Pre-vagrant TYPICAL SETUP WHERE VAGRANT ISN’T INVOLVED 1. Install everything directly unto the machine. 2. Maintain a long non-updated documentation.
8. Post-Vagrant
9. Post-vagrant TYPICAL SETUP AFTER VAGRANT IS INVOLVED 1. Consistency. 2. Things just works. 3. Issue of it works on machine doesn’t exist. 4. Life is beautiful.
10. Core concepts Vagrantfile Boxes Virtual Box Vagrant
11. vagrant init hashicorp/precise64
12. Core concepts: Vagrantfile
13. Core concepts: Vagrantfile config.vm.box = "servlet" config.vm.hostname = "celestine.blog" config.vm.network "forwarded_port", guest: 80, host: 8081 config.vm.provision :shell, :path => "vagrant/setup.sh" Box - Name of the box Hostname - Machine’s hostname Network - Network port Provision - Creating and bootstraping machine.
14. vagrant up
16. The concept of Vagrant Vagrant relies on the concept of virtualisation which entails creating a virtual version of a machine with its own OS inside a simulated hardware environment i.e. a whole new OS is started on your machine with its own kernel, ports, filesystem e.t.c. Virtualisation is enabled using an hypervisor which also uses part of the host’s resources.
17. The concept of Docker Docker essentially uses the concept of containerisation which entails encapsulating/packaging an application in a container with its own operating environment. Containerisation allows multiple applications to run in isolated partitions of a single Linux kernel running directly on the physical hardware. Containers reuse kernel, ports and other low level resources of your machine instead dispatching their own.
19. • Higher performance than virtualisation since there is no hypervisor overhead. • Containers work like just any other process on the host machine, thereby using little host resources when compared to VM’s. • Cached build processes. Faster instantiation time. • Kernel between all instances are shared which makes it lightweight. • Requires a static amount of resources (CPU, RAM e.t.c.) to the VM’s, and the hypervisor uses a lot of resources. • Better integration with Config Mgt tools like Chef, Ansible and Puppet. • Application resources are well isolated thereby achieving near-complete separation. • Runs a wide variety of boxes from Ubuntu, CentOS, WIndows, Solaris e.t.c
20. Questions?
21. Thank you