Continuous operations in AWS
2 likes121 views
This document outlines best practices for continuous operations in DevOps. It discusses challenges with traditional system administration approaches being slower than development teams. The document recommends a DevOps approach where system administrators have development skills and focus on automation to deploy code within minutes. It provides an overview of continuous integration/delivery pipelines and infrastructure as code using AWS Elastic Beanstalk as an example. The document concludes by offering additional DevOps training.
Continuous operations in AWS
- 2. 9 years in IT 5 years as a trainer 20+ certificates Dmitriy Kagarlickij DevOps Architect
- 3. Developers & testers DevOps Responsibility scope SysAdmin Conflicts DEPLOY OPERATETESTBUILDCODEPLAN
- 4. 1. Check datacenters availability 2. Check server hardware capacity 3. Check network & virtualization 4. Install OS & updates 5. Install web & db clusters 6. Setup monitoring 7. Setup scaling 8. Deploy code 9. Check that code works 10. ... Problem: SysAdmins are slower than Devs Estimated time: 1 day - 1 week Risks: ➔ Availability ➔ Scalability ➔ Security
- 5. SysAdmin knowledge ● Networking ● Linux / Windows ● Web & Databases ● Monitoring ● ITSM workflows
- 6. DevOps basics ● OOP essentials ● VCS ● Cloud ● APP-V ● Agile workflows
- 7. Size is a challenge:
- 8. General stuff to care ● Relations ● Risks ● Documentation ● Compliance ● Communications
- 9. What does Agile mean?
- 10. What does Agile mean for DevOps? ● Do only what is required now ● Do only what brings maximum effect ● Use the simplest approach solving the problem
- 11. DevOps requirements are growing!
- 14. ● Release to dev env: every 15-30 minutes ● Release to prod env: 3-5 times a day ● CI & CD time: 5 - 15 minutes ● Scaling pale: up to 10 times in 10 minutes ● Env provisioning time: up to 15 minutes ● Develop & implement CO time: one sprint
- 20. Configuration options: PRIORITY ● GUI ● Saved configurations ● Configuration Files ● Default options
- 21. config.yml to skip eb init
- 22. CLI options:
- 27. DEMO
- 28. Back to the Earth
- 29. Full training considers: 1. Real applications examples, not just “Hello World” 2. Not only AWS services 3. Multi-environment operations 4. 100% custom CI/CD from scratch, not Jenkins 5. Scripting best practices 6. Custom deployment policies 7. Hands-on lab 8. How-to start guide 9. Live discussion of your cases 10. … and some more!
- 30. What to do next? 1. Fork: https://github.com/kagarlickij/continuousoperations-demo 2. Ask me for help: dmitriy@kagarlickij.com 3. Watch me in LinkedIn: https://ua.linkedin.com/in/kagarlickij 4. Checkout DevOps posts: http://kagarlickij.com/ 5. Apply for a job: dmitriy@kagarlickij.com 6. Provide feedback to training center 7. Invite me as DevOps architect (part-time)