Bare-bone structure of DevOps:
1. Values - CAMS
i. Culture
ii. Automation
iii. Management
iv. Sharing
2. Principles
i. Systems Thinking - Dev to Ops - Overall System
ii. Amplifying Feedback Loops
iii. Continuous Experimentation and Learning
3. Methods
i. People Over Process Over Tools
ii. Continuous Delivery
iii. Lean Management
iv. Visible Ops Change Control
v. Infrastructure as Code
4. Practices
i. Incident Command System
ii. Developers on Call
iii. Status Pages
iv. Blameless Postmortems
v. Embedded Teams (Ops person working with the developers)
vi. The Cloud (API driven so can work on Infra as code)
vii. Andon Cords (To notify and stop a buggy code from going into prod)
viii. Dependency Injection (Inversion of Control - Web Framework model)
ix. Blue/Green Deployment
x. Chaos Monkey (Remember NetFlix)
5. Tools
i. Programmable (Not just UI driven)
ii. Verifiable
iii. Well Behaved
References & Resources to explore the subject further:
1. https://devops-research.com/
2. https://puppet.com/solutions/devops
3. https://puppet.com/blog/what-is-devops
4. https://puppet.com/resources/ebook/devops-and-you-advice-for-building-your-career
5. https://puppet.com/blog/devops-tools-support-your-devops-initiatives
6. https://puppet.com/blog/what-a-devops-engineer
7. http://www.amazon.in/Devops-Handbook-World-Class-Reliability-Organizations/dp/1942788002
8. https://martinfowler.com/bliki/DevOpsCulture.html
9. https://martinfowler.com/bliki/ContinuousDelivery.html
10.https://www.ibm.com/developerworks/community/blogs/c914709e-8097-4537-92ef-8982fc416138/entry/devops_in_practice_best_practices_for_adopting_continuous_delivery?lang=en
1. Values - CAMS
i. Culture
ii. Automation
iii. Management
iv. Sharing
2. Principles
i. Systems Thinking - Dev to Ops - Overall System
ii. Amplifying Feedback Loops
iii. Continuous Experimentation and Learning
3. Methods
i. People Over Process Over Tools
ii. Continuous Delivery
iii. Lean Management
iv. Visible Ops Change Control
v. Infrastructure as Code
4. Practices
i. Incident Command System
ii. Developers on Call
iii. Status Pages
iv. Blameless Postmortems
v. Embedded Teams (Ops person working with the developers)
vi. The Cloud (API driven so can work on Infra as code)
vii. Andon Cords (To notify and stop a buggy code from going into prod)
viii. Dependency Injection (Inversion of Control - Web Framework model)
ix. Blue/Green Deployment
x. Chaos Monkey (Remember NetFlix)
5. Tools
i. Programmable (Not just UI driven)
ii. Verifiable
iii. Well Behaved
References & Resources to explore the subject further:
1. https://devops-research.com/
2. https://puppet.com/solutions/devops
3. https://puppet.com/blog/what-is-devops
4. https://puppet.com/resources/ebook/devops-and-you-advice-for-building-your-career
5. https://puppet.com/blog/devops-tools-support-your-devops-initiatives
6. https://puppet.com/blog/what-a-devops-engineer
7. http://www.amazon.in/Devops-Handbook-World-Class-Reliability-Organizations/dp/1942788002
8. https://martinfowler.com/bliki/DevOpsCulture.html
9. https://martinfowler.com/bliki/ContinuousDelivery.html
10.https://www.ibm.com/developerworks/community/blogs/c914709e-8097-4537-92ef-8982fc416138/entry/devops_in_practice_best_practices_for_adopting_continuous_delivery?lang=en
No comments:
Post a Comment