Understanding DevOps
- 1. Understanding DevOps And everything you need to know to succeed as a DevOps Engineer This deck has initially been used during a talk to computer sciences students at EPITA Engineering School by Mathieu Mailhos, DevOps at CloudScreener, on 18/01/2017
- 2. French startup founded in 2012 by Anthony Sollinger & Nicolas Drouet Part of The Refiners Fleet #2, San Francisco (2017) Aiming at bringing expertise and demystifying shadows in the Cloud Industry. Helping in decision-making processes. Trusted by Who we are
- 3. Meet Cloud Decision Engine Free for 14 days on: www.cloudscreener.com
- 4. Initial problem: 3 different teams and processes: Dev, QA & OPS Having 3 distinct teams makes communication harder With potentially 3+ different environments Devs are getting lazy and let QA debug for them Devs have no idea about what does production looks like QA and Ops are delivering features without knowing their purpose Ops are pushing code they did not write making badly monitored code Devs brings change: Reactivity, Ops wants reliability: Stability Above is what you want to avoid
- 5. DevOps Ideology Overall, we are in the same team We need business continuity, fast Go-To-Market time So let’s just bridge the gap between teams Different way of thinking: work based on collaboration Be open, no finger-pointing, communicate, ask questions… DevOps implementation always depends on the use case but the ideology remains the same
- 6. Automate to reduce intermediaries Bridging gaps between developers and end-user: need of a fully automated chain to remove obstacles and deploy more often to get more user feedbacks Provisioning Prepare your instances to be ready to use Chef, Ansible, Puppet, Docker Deployment Put your new application on a prepared instance Capistrano, Mina Orchestration Coordinating multiple systems Kubernetes, Mesos, Swarm Below 3 main steps of sending a server to production. Depending on the use case, some can be optional and other technologies can be used
- 7. Continuous Deployment docker.com Another example of an automated chain: the CI/CD Pipeline; which implies, at a minimum, that each developer is writing its own tests per feature
- 8. But wait, a DevOps Engineer has much more to manage Infrastructure Design Logging Monitoring Metrics Alerting Self-Healing Systems Disaster Recovery Security Infrastructure As Code
- 9. Appreciated skills and state of mind Always be learning, be passionate Be creative to find clever solutions Great systems & networks skills Fluent in development Stay humble, Receive advice Take initiatives
- 10. Just getting started? Your stack is your showcase Get at least an experience in each of the following topics Cloud AWS, GCP, Azure, Openstack Database MongoDB, MySQL, PostgreSQL, Redis Tools Git, Docker CI/CD TravisCI, Jenkins, Bamboo, CircleCI Development Ruby, Python, Bash or NodeJS, Go Provisionning Ansible, Chef, Puppet
- 11. Benefits There is no such thing as a typical day A wide range of technologies to discover and master Future is exciting: Serverless Infrastructures, powerful orchestration tools…. You are the Swiss knife everyone needs: it’s your chance to grow with a startup! So, what exactly are you waiting for?
- 12. Thanks! Question Time Talk to us, request a demo of Cloud Decision Engine: contact@cloudscreener.com Mathieu Mailhos