1. Winter 2016
(c) Ian Davis

2. By Sanjeev Sharma Bernie Coyne
DevOps for Dummies By
Sanjeev Sharma
Bernie Coyne
Winter 2016
(c) Ian Davis

3. Available for free download
Google “DevOps for Dummies - IBM.com‎”
Winter 2016
(c) Ian Davis

4. The problem Software projects fail
Failure related to development/delivery
So development/delivery practice critical
IBM survey
Only 25% believe their teams are effective
Missing business opportunities
Winter 2016
(c) Ian Davis

5. Recent system transition
Old: Record based systems
Stable, static, boring mainframe implementations
New: Customer engagement systems
Mobile communications, web based, cloud etc.
Easy to use; high performance
Evolve to better reflect customers needs
Evolve to better reflect market forces
Focus on user experience, speed of delivery, agile
Winter 2016
(c) Ian Davis

6. Goal of DevOps “On the rise” – Gartner 2013
Buzz word → Risk ill-defined, overblown
Reduce time to market for new features
Specifically commit time to placing in system
While ensuring high quality of deliverable
Impacts
Team organisation
How systems are built
Structure of those systems
Winter 2016
(c) Ian Davis

7. DevOp Side Effects Enhanced customer experience
System responsive to customer feedback
Improved capacity to innovate
Though more efficient test strategies
Roll out better software
Recall worse software
Faster time to value
Tools and culture → speed, predictability, success
Winter 2016
(c) Ian Davis

8. Core Principles Develop & test against production-like systems
Involve operations earlier (shift-left)
Deploy with repeatable, reliable processes
Deploy incrementally and often
Monitor and validate operational quantities
Test non-functional attributes early
Amplify feedback loops
Need communication channels for all stakeholders
Winter 2016
(c) Ian Davis

9. Winter 2016
(c) Ian Davis

10. The DevOps Culture High degree of collaboration across roles
Focus on business (not departments)
Trust and reciprocal support
Value placed on learning through experiment
Lean agile transformation practices
Scaled Agile Framework (SAFe)
Disciplined Agile Delivery (DAD)
Scrum, etc.
Winter 2016
(c) Ian Davis

11. The challenge Development Operations
Rewarded for more improvements delivered faster
Quality suffers
Operations
Rewarded for system uptime and stability
So opposed to software changes
Solution: share both responsibilities
Improve visibility of tasks/actions/problems
Winter 2016
(c) Ian Davis

12. The cloud Provisioning and configuration As needed When needed
For the version needed
Simulation of test environments
Eases deployment to production
Winter 2016
(c) Ian Davis

13. Winter 2016
(c) Ian Davis

14. Cloud Service Models Software as a Service (SaaS)
, online games, customer relations, virtual desktops (human view of what a service is)
Platform as a Service (PaaS)
Web servers, database, development tools, etc. (software view of what a service is)
Infrastructure as a Service (IaaS)
Virtual machines, storage, load balances, networks (virtual OS view)
Winter 2016
(c) Ian Davis

15. Software as a service Eureqa Leveraging the power of Amazon Cloud
Permits machine learning
Using provided models
Leveraging the power of Amazon Cloud
Winter 2016
(c) Ian Davis

16. Platform as a service WordPress
End user interacts with software on cloud
End user configures software on cloud
Winter 2016
(c) Ian Davis

17. Infrastructure as a Service
Virtual OS
Can support different OS’s
Permits testing across OS’s
OS image loaded, and saveable
Permits sharing of images
Easy later configuration of system
Behaves like a remote desktop
Optimises CPU usage across machines
Winter 2016
(c) Ian Davis

18. Hybrid Cloud Problems Combination of cloud and physical systems
Can’t virtualise everything
On and off premises cloud systems
Can’t run everything anywhere
Combination of IaaS and PaaS
Not one release strategy
Portability across more than one cloud provider
To avoid risk of vendor lock-in (or to exploit choice)
Winter 2016
(c) Ian Davis

19. 10 Myths about DevOps Is only for “born on the web” shops
Is operations learning how to code
Is just for development and operations
Isn’t for ITIL (standards compliance)
Isn’t for regulated industries
Winter 2016
(c) Ian Davis

20. Myths continued Isn’t for out sourced development
No cloud means no DevOps
Not for large complex systems
Is only about communications
Involves continuous change deployment
Winter 2016
(c) Ian Davis