DevOpsDays Ignite - Immutable infrastructure - Amsterdam 24-5-2015
•Télécharger en tant que PPTX, PDF•
0 j'aime•371 vues
This ignite talk was delivered at DevOpsDays Amsterdam 2015. The talk goes in short over immutable infrastructure - why it is beneficial in the modern software development and how to start using it.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (10)
Similaire à DevOpsDays Ignite - Immutable infrastructure - Amsterdam 24-5-2015
Similaire à DevOpsDays Ignite - Immutable infrastructure - Amsterdam 24-5-2015 (20)
Plus de Pavel Chunyayev
Plus de Pavel Chunyayev (11)
Dernier
Dernier (20)
DevOpsDays Ignite - Immutable infrastructure - Amsterdam 24-5-2015
- 1. Immutable infrastructure Pavel Chunyayev DevOpsDays Amsterdam 25-05-2015
- 2. Modern approach to manage infrastructure
- 3. Good old world of physical servers Those were the days
- 4. Apply the golden image And pray
- 5. Configuration mgmt to save us all Or at least to try
- 6. Deployments that everyone hates Or is it just me?
- 7. But we want more deployments! MOAR!
- 8. Get yourself a process Repeat, repeat, repeat
- 9. Never change your server again! Nothing personal
- 10. Sysadmins become developers And not using Perl this time
- 11. Real infrastructure as a code Shit just got real
- 14. Immutable nature of containters
- 15. Where to store data? Somewhere else
- 16. But what about logs and metrics? #monitoringsucks
- 17. Continuous Delivery at its best Fully automated and repeatable
- 18. Prefabricated, prebuilt, prebaked, phoenix, disposable, immutable Just choose any already
- 19. Immutable infrastructure The most ambiguous name
- 20. Embrace the change And relax
Notes de l'éditeur
- New cloud world requires new ideas DevOps, Continuous Delivery, Automation Especially valuable for microservices
- All historic experience Servers number - small Situation - manageable As the number grows, the task gets harder Compliance Updates
- And the concept of golden image appeared Provision from approved state Issues: Waiting for sysadmin to create and configure infra How to deal with already provisioned instances Managing live instances is the same as previously
- Infrastructure as a code Issues: Still infrastructure is re-used DSL (sometimes hard to learn) Compliant only in areas covered by code
- Deploying to stateful server is hard Edge-cases Serial deployment: handle exceptions manually Still not fun
- Need to deploy more frequently => repetition Easier when rebuilt from the scratch Repetition leads to mastery Fire drills are part of everyday life now! You infra is self-healing
- Continuous Delivery Lean Software Development Know exact MTTR Reduce Inconsistencies variability waste
- Never change – recreate! Server state is not saved Not like in functional programming language
- Sysadmins are developers now Code everything!
- API is the key You can program infrastructure life cycle Create Configure Deploy Operate Dispose Deployments suddenly get a lot easier
- Create duplicate infrastructure Test everything Make the switch Can be done with reusable infrastructure too Slower
- Deploy new version alongside Gradually increase amount of traffic Monitor constantly If anything’s wrong – quickly revert When reach 100% - dispose older version
- Immutable Copy-on-write allows to easily revert to known-state Pass containers around and start without any data Dockerfile is essentially a bash file Is applied only once
- Somewhere else persistency layer/database Stateless application
- Send to remote host Push instead of pull
- Continuous Delivery at its best Continuous Deployments Fully automated and repeatable Package application only once – and then never change it Quick feedback if anything fails Testing in production!
- New paradigm for the cloud era and microservices architecture.
- Make your life easier if you are operations – think as a developer If you are a developer - take responsibility for environment where your application is running. It’s a lot easier than before If you are a manager – embrace the future: Disposable infrastructure on-demand exactly when it’s needed.