Download as PDF, PPTX
Uploaded bysys army
Vagrant Workshop
1) Vagrant allows developers to easily create and manage virtual development environments that mirror production. With a few simple commands like "vagrant up", development teams can have consistent environments that reduce bugs from differing local setups. 2) Real use cases demonstrated how Vagrant improved testing workflows by allowing clean, reproducible environments with just a few commands rather than complex virtual machine management. It also helped standardize environments across large development teams. 3) Benefits of Vagrant include consistent environments within and across projects, easy setup and teardown of multiple environments, and lower learning curves for teams through standardized environments.
More Related Content
Vagrant Workshop
- 1. Vagrant Workshopby Eduardo Casarero(ecasarero@gmail.com || @jedux) vagrant up (TECHNOLOGY) — phrasal verb with vagrant “just hit vagrant up” and ‘automágicamente’ download the box, unpack it, add it to the box repo, clone it into VirtualBox, start it, provision it and give access to the user.
- 2. Who? ● Eduardo Casarero(@jedux) ● Almost Engineer (UADE) ● Sysadmin > 10 years ● DevOps <3 ● #sysarmy (irc, sysarmy/help, adminbirras) ● #nerdearla
- 3. Hashicorp Candy factory forSysadmins.
- 4. Application delivery doneright. HashiCorp delivers pragmatic solutions to maximize developer and operator agility. Build microservice-driven applications that are codified, automated, scalable and secure.
- 5.
- 6. Hashicorp Ecosystem Packer isa HashiCorp tool for creating machine images and deployable artifacts such as AMIs, OpenStack images, Docker containers, etc. Terraform is a HashiCorp tool for creating, combining, and modifying infrastructure. In the Atlas workflow Terraform reads from the artifact registry and provisions infrastructure. Consul is a HashiCorp tool for service discovery, service registry, and health checks. Serf is a HashiCorp tool for cluster membership and failure detection. Vagrant is a HashiCorp tool for managing development environments that mirror production. Vagrant environments reduce the friction of developing a project and reduce the risk of unexpected behavior appearing after deployment.
- 7.
- 8.
- 9. Pre-Vagrant scenario (real) Usecase 1 (easy one): “ASAP test this package/app/config/etc (in a clean environment)” ● First approach: use my notebook/desktop ○ my desktop is not a “clean” environment, it’s more like a polluted one. ● Second approach: use a virtual machine on virtualbox ○ easy, install from iso in virtualbox, test, destroy vm… too much time to setup. ○ Corporate Virtual Machine “black” market -> not clean environment ● Third approach: cd vagrant/ubuntu-server && vagrant up ○ Learn vagrant, created one base box like a production environment ○ up -> test -> destroy -> up -> test -> destroy :) :) :) :)
- 10.
- 11. Vagrant! Virtualized development environmentmade easy ● command line tool ● lowers provisioning time ● fully control environment and versions ● kills “work on my machine” excuse ● many providers: virtualbox, vmware, aws, etc ● can use puppet, chef, ansible, bash scripts ● FREE and open source
- 12. 80% of Vagrant ●5 simple commands: ○ vagrant up ○ vagrant provision ○ vagrant ssh ○ vagrant halt ○ vagrant destroy ● Really more like 16 commands, but you really use these 5.
- 13. Go -> Level0 & 1 Get the workshop environment from https://github.com/edux/vagrant_workshop
- 14. Shortfalls of environments ●Does not mirror “testing” or production setup ● Each developer has a different one ● Easily out of sync with standards ● Many versions of php, mysql, java, etc. ● High learning curve for new devs/qa/it ● ‘works in my computer’ culture.
- 15.
- 17.
- 18. Benefits ● Solo Developers ○consistency across multiple projects ○ can run multiple environments on a single host (dev, test, staging) ○ easy tear down and rebuild ● TEAMS ○ identical development environments (kills ‘works on my pc’ excuse) ○ consistent and portable ● COMPANIES ○ lowering learning curve ○ build once, distribute to everyone ○ lower costs
- 19.
- 20. Real use case:take 2 PM: please fix our “switch to replica” golden scripts. Need at least 3 servers to test. ● Started with only Virtualbox kicking and snapshotting vms. ● Ended with Vagrant with multi machine environment -> glory.
- 21.
- 22. Real Use case:take 3 IT team supports almost 60 devs+qa. Everybody “needs” a sandbox environment to play with. ● Sandbox installation installs toooooo many things nginx, mysql,git,internal tools, log tools, the app, devs tools, qa tools, etc…. ● Solution: Vagrantify environment, this is still a work in progress as the use case is “complex”.
- 23. (my) Success keysto deploy vagrant ● dogfooding is critical (sell what you use) ● get support from management (hard one) ● rock solid images (users does not like bugs, neither do we) ● prepare images and configs to suit all use cases!!!! ● detect early adopters to help you push changes in the teams
- 24.
- 25. Provisioning like aboss - Shell - Ansible - CFEngine - Chef - Docker - Puppet - Salt
- 26.
- 27. multi envs withmulti vms. - The dynamic ip challenge. - Hostsmanager - moving that to libvirt with minimal changes: - network eth names - mem / cpu / other hypervisor parameters.
- 28. misc: kali -windows. - using gui=true. - winrm is available to do configs over windows hosts. - show modern.ie windows vms for everyone. (https://dev.modern.ie/)
- 29.
- 30.
- 31.
- 32.