Confoo-Montreal-2016: Controlling Your Environments using Infrastructure as Code
1 like•490 views
The document discusses the importance of managing environments and utilizing Infrastructure as Code (IaC) to improve software delivery and agility. It emphasizes automating processes through DevOps practices such as Continuous Integration (CI) and Continuous Delivery (CD) to reduce manual steps and enhance release capabilities. The author shares insights from their extensive project experience and highlights best practices for integrating development and operations to produce effective software solutions.
![Ex: See how using the Vagrant
file, we can provision the
platform
config.vm.box = “hashicorp/precise64"
config.vm.network :forwarded_port, guest: 80, host: 4567
config.vm.provision :shell, path: “bootstrap.sh"
#!/usr/bin/env bash
apt-get update
apt-get install -y apache2
if ! [ -L /var/www ]; then
rm -rf /var/www
ln -fs /vagrant /var/www
fi
apt-get install -y python3](https://image.slidesharecdn.com/confoofeb2016-controllingyourenvironmentsusingiac-160226131921/85/Confoo-Montreal-2016-Controlling-Your-Environments-using-Infrastructure-as-Code-51-320.jpg)
Confoo-Montreal-2016: Controlling Your Environments using Infrastructure as Code
- 1. Controlling Your Environments using Infrastructure As Code ConFoo Montréal - February 2016 Steve Mercier Copyright Software That Matters… Done Right! Inc. 2016
- 2. Who am I? I participated in multiple software development projects: • from very small (<10 person) to large (~400 persons) • from a long time ago (>20 years) up to now • from different angles/roles: Developer, Architect, PM, DevOps/ BuildMaster, Software Release Manager • I have seen software methods/processes come and go: Waterfall, RUP, OpenUP, XP, Scrum, Scaled Agile, etc. But the essential remains: I believe that to produce good software, it takes good people + resources AND discipline/professionalism/focus!
- 3. Are You Agile? Agile is not easy… and is not only about ceremonies + tools!
- 5. Nothing on the previous slide concerning software context, where is the code delivered, running, performing… Agile typically deals with this with the Definition Of Done concept, sadly overlooked way too often…
- 6. What would be a good measure of Agility anyway?
- 7. Suggestion #1: The capability to release (aka) The frequency at which you are delivering software updates that add business value to your clients without breaking any previously delivered business value that you want to retain
- 8. Suggestion #2: The time to release (aka) The time it takes you to deliver the smallest change/fix to your software in production
- 9. Given that: What prevents true agility?
- 10. What prevents you to release? What prevents you to release fast?
- 11. From my point of view: Lack of environments’ management True for all types of environments: DEV, QA, Staging, Production
- 12. Platform dependencies? Do you manage them? ex: Frameworks dependencies, external libraries dependencies, etc. Are they either never updated or are they continuously creating problem when you upgrade them?
- 13. OS dependencies? Do you manage them? How is the OS changed on your platform? Does it break your applications sometimes? Any logs/traces of those changes? Can they be rolled back in case of problems?
- 14. Hardware/VM specs dependencies? Do you manage them? What happens if available RAM/Disk/Network gets below what your applications need? Do you know what they need?
- 15. If you manage your environments, do you manage them manually?
- 16. Everything not automated reduces your Agility
- 17. Manual triggers can take a long time Manual = Time++;
- 18. As your manager might say Time == Money();
- 19. What techniques can reduce manual steps? You could consider using DevOps: CI server, CD server, Infrastructure as Code to automate as mush as possible your release process DevOps Client PO Team Delivery
- 20. What techniques can reduce manual steps? Continuous Integration
- 21. What techniques can reduce manual steps? Continuous Delivery/Deployment
- 22. What techniques can reduce manual steps? Infrastructure As Code
- 23. Are your Agile Demos done from unreleased software (aka Works at my desk)
- 24. Your software must have it!
- 25. Demos from unreleased software / Difficulty to release in production Involve Ops people in sprints Releasing in prod should be doable by anyone, anytime, using a single click (rollback is obviously a feature you will want!)
- 27. Continuous Delivery/Deployment Always have a shippable version available for your customers Ex: GO CD (from Thoughtworks - now Open Source) You can integrate your CI servers (Jenkins) with a CD server
- 28. Continuous Delivery/Deployment A good practice to deploy gradually using cascaded environments: • (Development) • Test • Less resources, used mostly to validate business logic • Staging/Pre-Production • More representative of the production environment. Can be used for load/performance testing. Typically uses a data set that is a copy of the Production data set. • Production
- 30. Infrastructure as Code Your code is under CM, but your infrastructure is typically not! It also needs to be versioned, tracked and automated!
- 31. There are so many tools available. But essentially, keep ALL under source control, including what it takes to reproduce your production environment from ZERO Infrastructure as Code • How to restart a hardware environment/virtual machines • How to install the platform on the machines • How to install the applications on the platforms • How to configure the whole stack • The databases schemas and content • Everything!
- 32. If you are not convinced, think about your disaster recovery plan (you have one, right?) Infrastructure as Code What if your server room is destroyed by water/ fire? (or the one from your cheap cloud provider…) With IaC at least, the software part is covered in case of disaster
- 33. DevOps
- 34. DevOps • A Good app without an infrastructure to run it is useless… • A superb, scalable infrastructure without an app adding business value to a customer is also useless… • You need both! • DevOps should not be a separate team! It serves to bridge the gap between development and operations teams. • And if you are not convinced that DevOps cannot typically be a single person’s responsibility…
- 36. What could be potential solutions to deliver and faster?
- 37. 1- Testing (TDD, BDD) 2- CI 3- CD 4- IaC
- 38. DEMO
- 39. Demo content • GO CD presentation • Application build pipeline • connected to GitHub for app code • running unit tests • Triggering Staging pipeline on success • using Vagrant + VirtualBox + Ansible to provision production like environment for system tests • connected to GitHub for IaC code • Triggering Deployment pipeline on success • using Ansible (Tower) to provision non VM production multiple environments
- 40. Application Build/Unit tests Continuous Integration pipeline Triggered on code changes
- 41. Staging pipeline For deployment + system testing Triggered on new application integration OR new IaC code
- 42. Deployment pipelines Used to actually deploy the application into production triggered on successful staging pipelines OR manually when needed
- 43. Discussion How do you do it?
- 44. Agile Values vs. Agile Practices
- 45. Agility is more than Agile values and ceremonies It is acting as per the Agile values and producing software with related best practices
- 46. But where to start? Every Agile cycle, try to improve on those issues, trying to automate everything you can, while having the conversation with your key stakeholders
- 48. Thanks! softwarethatmattersdoneright.com + http://ca.linkedin.com/in/stevemercier Copyright Software That Matters… Done Right! Inc. 2016
- 49. Backup
- 50. Install provisioning tools Ex: Vagrant + VirtualBox - vagrant init hashicorp/precise64 - vagrant up - vagrant ssh - vagrant destroy
- 51. Ex: See how using the Vagrant file, we can provision the platform config.vm.box = “hashicorp/precise64" config.vm.network :forwarded_port, guest: 80, host: 4567 config.vm.provision :shell, path: “bootstrap.sh" #!/usr/bin/env bash apt-get update apt-get install -y apache2 if ! [ -L /var/www ]; then rm -rf /var/www ln -fs /vagrant /var/www fi apt-get install -y python3
- 52. How to install the applications on the platforms Ex: We can simply reuse the GIT clone using a shared folder between host and guest VM or use similar platform provisioning technique to perform a git clone in the VM after provisioning