Provisioning Environments, a simplistic approach
Download as PPTX, PDF0 likes350 views
This document discusses provisioning development environments using tools like Vagrant and Puppet. It begins with an agenda that includes DevOps, Vagrant, Puppet and providing a real example. It then defines DevOps as anything that improves interactions between development and operations. Vagrant is introduced as a simple tool for creating virtualized environments. Puppet is described as an automation tool that defines and enforces infrastructure state using a language and manifest files. The document concludes by providing a link to a real example GitHub project that demonstrates how to set up an application server cluster with load balancing using these tools.
Provisioning Environments, a simplistic approach
- 1. Provisioning Environments A simplistic approach
- 3. Agenda ● Devops ● Vagrant ● Puppet ● A real example ● Questions?
- 4. What this presentation is not about? ● Configuring nginx or other servers ● Loadbalancing ● Configuring MongoDB or other DB's ● MongoDB replicaset
- 5. Devops Anything that makes interactions between development and operations, better. "Thomas Limoncelli"
- 7. Devops = Agility + Cooperation
- 8. Problem #1 (Deploy) More Changes More Commits More Deploys Less time
- 9. Interactions between devs and ops, why?
- 10. Interactions between devs and ops, why?
- 11. Problem #2 (New dev comes) Creating an environment Install Java Install Tomcat Install DB Start to code
- 13. What is Vagrant? Simple way to create virtualized environment… Yes, it’s a tool. It started in January 2010 by Mitchell Hashimoto https://www.vagrantup.com/
- 14. What problems are solved? ● Reproducible ● Portable ● Agility ● Automation ● no more "works on my machine"
- 15. Compatibility
- 16. How does it works?
- 17. All starts in a Vagrantfile
- 18. All starts in a Vagrantfile $ vagrant up $ vagrant ssh database Trust, that's all...
- 19. Is it just this?
- 20. No, we have more... Just an environment won't help you... Puppet
- 21. What is Puppet? Puppet is IT automation software that defines and enforces the state of your infrastructure. ● Is a language ● Is an infrastructure manager
- 22. Whaaaat!!!
- 24. Puppet flexibility If you have an available environment, you will probably installs some apps/services on it.
- 26. You need a manifest file Puppet language files are called "manifests" manifests/config.pp
- 27. Modules and Puppet community ● You don't need to make all by yourself ● Use modules available by community https://forge.puppetlabs.com/
- 28. Using a module
- 29. A real example APP SERVER 1 APP SERVER 2 APP SERVER 3 NGINX REPLICA SET MONGO 3 MONGO 1 MONGO 2 DRIVER DRIVER DRIVER LB https://github.com/EderRoger/nginx_loadbalancer
Editor's Notes
- #16: About VMWare.. http://www.vagrantup.com/vmware Price: $79 per seat. A single seat can be used on two computers (such as a desktop and a laptop) for a single person.
- #22: When you use Puppet, you are modeling your infrastructure as code
- #23: “Puppet” really refers to two different things: the language in which code is written, and the platform that manages infrastructure.
- #27: The foundation of the Puppet language is its declaration of resources. Each resource describes a component of a system, such as a service that must be running, or a package that must be installed. Some other examples of resources: A user account A specific file A directory of files Any software package Any running service
- #30: Session Persistence (REDIS)