Mini training - Infrastructure as Code

Transcript

1. Infrastructure as Code Build, repeat and test your configurations
2. What is Infrastructure? Resources (network, file, computer, ...) acting together to provide some services
3. What is Code? Text representing instructions which have to be executed to produce an output
4. And IAC??? View infrastructure like an artifact Artifact are produced from code A try to apply software techniques (versionning, testing, automation...) to infrastructure requests
5. But... We are using VM images. How are you building VM images? We have a lot of world documentation. How do you maintain and version documentation? We have some custom scripts. Can you easily and quickly handle change?
6. Step one : Configuration management Process of standardizing resource configurations and enforcing their state across IT infrastructure in an automated yet agile manner
7. We have good tools to start
8. Why use it? • Bring abstraction layer • Declarative code is also kind of documentation • Easy to rollback, release, and track in CVS • Provide repeatability and idempotence • Scale easyly
9. Configuration management with Chef include_recipe "apache2" apache_site "default" do enable true end
10. Step two : Create and stock artifacts Assembly Container Virtual Machine
11. Step three : Provisionning Set of actions to make a infrastructure resource available and make it ready for network operation.
12. Provision on Azure azure vm create my-vm-name mi_name_{{timestamp}} username --location "West US" –r
13. Step four: Test, test and test Ensure that infrastructure meets the requirements and performs its functions.
14. Testing strategy Test every change Get fast feedback Run code against short lived virtual machines
15. ServerSpec Based on RSpec, ServerSpec tests for your servers configured by CFEngine, Puppet, Ansible or anything else.
16. Test with RSpec describe 'apache' do describe 'Installation' do it { should contain_package('apache') .with_ensure('present') } end end
17. What about load testing ? • JMeter • Gatling • Grinder • Tsung • ...
18. Step five: Improve your dev with Vagrant • Provide easy to configure, reproductible and portable development environments • Provider on top of VirtualBox, Vmware, Custom provider • Provision on top of Shell, Puppet, Chef
19. What's next? • Datacenter like a single pool of resources • Infrastructure pipeline • Immutable servers • Continuous integration to continuous deployment
20. Thank you Any question?