Download as PDF, PPTX
Uploaded bycontinuousphp
Let's Code our Infrastructure!
The document discusses infrastructure coding and management using Chef, an open-source tool for automating and versioning resources within cloud environments. It emphasizes the principles of infrastructure as code, continuous delivery, and maintaining a collaborative culture among development teams. The text details the process of creating and testing cookbooks, which contain configurations and recipes for various roles in an organization's infrastructure.
![[Jun AWS 201] Elastic Beanstalk for Startups](https://cdn.slidesharecdn.com/ss_thumbnails/aws201elasticbeanstalkforstartups-130708040156-phpapp02-thumbnail.jpg?width=640&height=640&fit=bounds)
Let's Code our Infrastructure!
- 1. Let’s Code ourInfrastructure
- 2. Who I am ●Oswald De Riemaecker ● Continuous S.A. CEO & Co-Founder o Agile Delivery specialist o Editor of the continuousphp PaaS ● « Agilist », Cloud Architect
- 3. Agile Culture ● Improvementin the development team o Better collaboration o Continuous improvement o All skills / No silos o Testing Framework and continuous integration ● Improvement in Agile product management o Iterative development o Features driven o Maximizing Value o MVP/Lean Startup
- 4. DevOps Culture ● Agile+ Operation ● 3 main pillars: o Infrastructure as Code (IaC) o Continuous Delivery / Deployment o Culture of cooperation
- 5. Infrastructure as Code ●Coding machines resources of the infrastructure ● Coding and versioning the infrastructure ● Testing both resources and infrastructure ● On demand rebuilding machines and infrastructure
- 6. Organization My Infrastructure YourInfrastructure Their Infrastructure
- 7.
- 8. Roles Load Balancer Application Servers IndexesServers Databases Servers
- 9. Resources ● A resourceis a part of the system and its configuration Apache MySQL Solr
- 10. Complexity ● Maintaining infrastructureis complex ● It lives and evolves, so you have to o Add new resources o Update resources o Apply Security Patches o Change/Update OS o ...
- 11. Tools ● The answerto this:
- 12. Chef ● Chef isan open-source tool ● Management of automation systems and infrastructure ● Chef is based on Ruby
- 13. Chef ● Nodes representthe servers within your infrastructure ● Nodes can be: o physical servers o virtual servers o instances in the cloud ● Each node belongs to: o an organization o an environment o has one or more role(s) Node NodeNodeNode Node Node
- 14. Chef Client /Server Node NodeNodeNode Node Node Chef Server chef-client Resources
- 15. Chef Cookbooks ● Thecookbooks contain artifacts of our resources Recipes Templates Files Attributes State of the resources
- 16. Chef Cookbooks ● Thecookbooks contain artifacts of our resources Recipes Templates Files Attributes State of the resources Installation / configuration of resources
- 17. Chef Cookbooks ● Thecookbooks contain artifacts of our resources Recipes Templates Files Attributes State of the resources Installation / configuration of resources Configuration templates
- 18. Chef Cookbooks ● Thecookbooks contain artifacts of our resources Recipes Templates Files Attributes State of the resources Installation / configuration of resources Configuration templates Configuration/script files
- 19.
- 20. Role Provisioning Node Role: Database Chef Server Hey, Iam role “Database” and my environment is “Development” Chef clientRecipes Templates Attributes Files Cookbook Recipes Templates Attributes Files Cookbook
- 21. Infrastructure Example ● WebServer - Apache 2.4/PHP-5.5 ● Database Server - MySQL ● Index Server - Solr Web Server Solr MySQL
- 22.
- 23. Apache Cookbook Analysis ●Support many platforms ● Support different Apache versions ● Attributes: o dir, docroot_dir o log_dir, error_log, access_log o default_modules o version o ...
- 24. Cookbook support anddependencies Recipes Templates Attributs Files Metadata Dependancies
- 25.
- 26. The recipes Recipes Templates Attributes Files Metadata cd recipes ls-l default.rb iptables.rb logrotate.rb mpm_prefork.rb mpm_worker.rb mod_php5.rb mod_*.rb
- 27.
- 28. The Files Recipes Templates Attributes Files Metadata cd files/default/ ls-l apache2_module_conf_generate.pl
- 29. Let’s code ourcookbooks
- 30. Role: Web Server/ Env: Production Apache / php-5.5 Recipes Templates Attributes Files Metadata Apache2 Recipes Templates Attributes Files Metadata iptables Recipes Templates Attributes Files Metadata logrotate PRODUCTION: Replacement Attributes Node Role: WebServer R O L E
- 31. Chef Development Kit ●Installation of chef-dk o Berkself o Knife o ChefSpec o Test-Kitchen o Serverspec o Foodcritic
- 32. ● knife cookbookcreate mon_org-webserver Creating our web server cookbook
- 33.
- 34. ● berks init Initializationwith Berkshelf
- 35. ● berks install Downloadingdependencies
- 36. ● vi attributes/defaults.rb TheAttributes
- 37.
- 38. Testing our cookbook ●kitchen list
- 39. Testing our cookbook ●kitchen verify default-ubuntu-1404
- 40. ● knife cookbookupload mon_org-webserver Versioning and uploading our cookbook
- 41. Repeating the exercisefor database and indexes roles
- 42.
- 43. Role: Sandbox /Environment: Dev mon_org-webserver mon_org-index mon_org-database Composer NodeJs Recipes Templates Attributs Files Metadata Recipes Templates Attributs Files Metadata Recipes Templates Attributs Files Metadata Recipes Templates Attributs Files Metadata Recipes Templates Attributs Files Metadata mon_org-webserver mon_org-Index mon_org-database composer nodejs DEVELOPMENT: Replacement of Attributs Node Role: Sandbox R O L E
- 44. Creating our sandboxcookbook ● knife cookbook create mon_org-sanbox
- 45.
- 46.
- 47. The Recipes ● virecipes/default.rb
- 48. ● vi attributes/default.rb Theattributes Attributs
- 49.
- 50. ● Cookbooks byrole of our infrastructure ● Specific Cookbook for our development environment o uses the cookbooks of our infrastructure roles ● We can reliably reproduce our infrastructure roles, it is: o Coded o Versioned o Tested o Deployed Provisioning Summary
- 51. Let’s create ourenvironments
- 52. Local Creating our developmentenvironment Development
- 53. Vagrant ● Create andset up development environments ● Providers (Drivers) o Virtualbox/VMWare o Docker o Instance EC2 ● Provisioning with: o Chef Client/Solo o Docker o Puppet Agent o …
- 54.
- 55.
- 56.
- 57. Immutable Infrastructure ● Benefits: oSaving time when supplying o No more maintenance of the servers => Replacement o Static machine Image pre-built and tested o Easy rollback to a previous version V1 V2 V3 Data
- 58. Packer ● Packer o Builders(Amazon AMI, Microsoft Azure, DigitalOcean, Docker, Google Compute Engine, …) o Provisioners (Shell script, Chef client, Ansible, Puppet, Salt, …) o Post-processor (Docker-push, Vagrant, Atlas, …)
- 59.
- 60.
- 61. ● packer buildpacker.json Creating our image
- 62.
- 63. Repeating the exercisefor the index role
- 64. Creating our Production/Stagingenvironment
- 65. AWS CloudFormation ● Easyway to create and manage an AWS resource ● CloudFormation takes care of dependencies ● Once the resources are deployed, you can edit and update in a predictable and controlled manner ● AWS CloudFormation supports the following resources: o Auto Scaling/Elastic Load Balancing o VPC o EC2 o RDS o IAM o …
- 66. VPC Private Subnet Public Subnet JSON Autoscale WebWeb Web Autoscale Index Index Index
- 67.
- 68.
- 69.
- 70.
- 71.
- 72.
- 73. Creating our webserver stack
- 74. Creating our webserver stack
- 75. Creating our webserver stack
- 76. Creating our webserver stack
- 77. ● Machines Provisioning ●Immutable Infrastructure o Static Machine Images ● Using Machine Images in AWS Cloud Formation ● Cloud Formation environment parameters ● We can now use our artifacts to build our different environments Infrastructure Summary
- 78. Orchestrating our infrastructure Testing Development Vagrant Featurebranch develop branch revision branch Staging Production CI/CD prepare test package prepare test package prepare test package
- 79.
- 80.