IT automation: Make the server great again - toulouse devops fev 2017
Download as PPTX, PDF1 like266 views
This document discusses IT automation and infrastructure management. It advocates splitting applications into stateless components and immutable infrastructure to improve scalability, reliability and security. Key points emphasized include automating server provisioning, treating servers as ephemeral resources, separating data and code onto different layers, and monitoring systems to ensure consistency and predictability.
IT automation: Make the server great again - toulouse devops fev 2017
- 1. IT AUTOMATION : MAKE THE SERVER GREAT AGAIN @WAXZCE QUENTIN ADAM AT TOULOUSE DEVOPS
- 2. Quentin ADAM from the Clever Cloud @waxzce on twitter – github- soundcloud – instagram …. WHO AM I ?
- 3. MY DAY TO DAY WORK : CLEVER CLOUD, THE IT AUTOMATION COMPANY
- 4. KEEP YOUR APPS ONLINE. MADE WITH NODE.JS, SCALA, JAVA, RUBY, PHP, PYTHON, GO… Cloud & on premise ;-)
- 5. AND LEARN A LOT OF THINGS ABOUT YOUR CODE, APPS, AND GOOD/BAD DESIGN…
- 6. GIVE BACK TO THE COMMUNITY NEVER GONNA LET YOU DOWN clever-cloud.com
- 8. 40 times in 5 years price drop of AWS SERVERS COSTS ARE GOING DOWN
- 9. Google I/O 2015 “RACE TO ZERO” I.E THE SERVER IS FREE
- 10. In fact, all you have is… COOL. YOU HAVE A SERVER.
- 11. HOSTING Backup Updates Certification Agreement Process Provisioning Security Hardware maintenance
- 13. ONCE UPON A TIME, MY BELOVED SERVERS
- 15. CREATE HISTORY
- 16. DOCUMENTATION
- 17. SPECIFIC
- 18. TAYLOR MADE
- 19. NOT ABLE TO SCALE
- 21. Automate SPLIT COMPLEX PROBLEMS INTO A COLLECTION OF SMALL ONES
- 22. POSSIBLE SERVERS STATES … Updated to V43 New configuration files Install new service History …
- 23. AVOID HISTORY
- 24. FIX STATE OF THE DATA TO ENSURE ACCESSIBILITY
- 25. POSSIBLE STATE IN AN IMMUTABLE STATE working Not working Very simple to predicate
- 26. FIX THE HISTORY IN A IMMUTABLE STATE
- 27. BTW, REAL WORLD INSIGHT “WE LIVE IN A MUTABLE WORLD, DEAL WITH IT”
- 30. PET != CATTLE
- 32. NO MORE OLYMPIC CONTEST ON UPTIME
- 33. And why it’s a problem to manage technical product and decision with book keepers point of view https://www.youtube.com/watch?v=0ip1FoBsLB4 (AWS PRICING HYPOCRISY LEAD TO BAD PRACTICE) Summon Yog-Sothoth
- 35. PRODUCTION HAS TO BE PERFECT
- 36. PEOPLE ARE NOT PERFECT
- 37. PEOPLE HAVE NOTHING TO DO ON PRODUCTION STUFF
- 38. AT CLEVER CLOUD SSH CONNECTION IS A RED ALERT
- 40. SPLIT PROCESS AND STORAGE Storage • Databases • Files • Sessions • Events • … Code • Can be replicated • Stateless • Process
- 42. VM, docker, kubernetes, puppet, ansible, vmware… This is not the problem TECHNOLOGIES?
- 43. Search youtube quentin adam docker DOCKER
- 44. THERE IS ONE PROCESS: BUILD
- 45. THEN, REGISTER
- 46. AND LIVE WITHOUT DATA
- 47. AND DIE WHEN MORE UPDATED VERSION IS THERE
- 49. FULLY AUTOMATED HOSTING FACTORY
- 50. AN INSTANCE IS DEAD OR ALIVE AND THAT’S ALL
- 55. Picking one instance or another doesn’t matter STATELESSNESS IS THE KEY
- 56. BECAUSE YOU WILL NOT RELY ON A SERVER ANYMORE
- 57. CREATE A FACTORY OF INSTANCE
- 59. Consul, etcd, Clever Cloud service dependencies SERVICE DISCOVERY
- 61. HOW TO MANAGE DATA?
- 62. SPLIT DATA AND PROCESS: FS COMPOSITION Runtime • local • replicable • updated Data • file system • block storage • replicated • copy on write?
- 64. Not part of this list DATABASE (ACID OR NOT, SQL OR NOT)
- 65. FILE SYSTEM
- 66. BLOC STORAGE
- 67. OBJECT STORAGE
- 68. (COPY ON WRITE)
- 69. (COPY ON WRITE)
- 70. DATA MANAGEMENT IS BIND TO DB NEEDS
- 71. ACID : DUPLICATE & DATA EVOLUTION
- 72. INSTANCE FOR ONE ORGANIZATION ACID • Atomicity • Consistency • Isolation • Durability Powerful data management • Transaction • User management • One above one Take advantage of ACID database
- 73. BUT IT DESIGNS A BOTTLENECK
- 74. EXAMPLE : E-SHOP ON CLASSIC MODE
- 75. EXAMPLE : E-SHOP ON CLASSIC MODE User A buy a hdd Database Transaction : • Stock management • Order management • Invoice generation • Customer Account reward • … Transaction user A is processed Stock & Order are just perfectly synchronize
- 76. EXAMPLE : E-SHOP ON CLASSIC MODE User A buy a hdd Database Transaction : • Stock management • Order management • Invoice generation • Customer Account reward • … Transaction user A is processed Stock & Order are just perfectly synchronize User B buy a hdd Transaction user B is processed then
- 77. EXAMPLE : E-SHOP ON MULTI-TENANT MODE i.e. : Multiple shop of various sellers on the same instance
- 78. EXAMPLE : E-SHOP ON MULTI-TENANT MODE User A buy a hdd on seller A Database Transaction : • Stock management • Order management • Invoice generation • Customer Account reward • … Transaction user A is processed Stock & Order are just perfectly synchronize User B buy a book on seller B Transaction user B is processed then
- 81. FORGET THE SAN, GO FULL DISTRIBUTED
- 83. BE CONSISTENT AND PREDICTABLE
- 85. EXPOSE METRICS
- 86. IMMUTABILITY AS A PATTERN ANOTHER TALK FROM ME ;-) FR version : https://www.youtube.com/watch?v=y1BR7Rh7FSY&t=15s
- 93. F*CK 12 FACTORS?
- 95. I’m on twitter : @waxzce quentin.adam@clever-cloud.com THANK YOU ! ANY QUESTIONS ? Clever Cloud gift coupon: toulouseDEVOPS17
Editor's Notes
- #12: Integrating a new technical stack can take months Installing new software is just a tiny part of the work