200 likes | 695 Views
DevOps for Dummies. By Sanjeev Sharma Bernie Coyne. Available for free download. Google “ DevOps for Dummies - IBM.com”
E N D
DevOps for Dummies By Sanjeev Sharma Bernie Coyne (c) Ian Davis
Available for free download • Google “DevOps for Dummies - IBM.com” • https://www-01.ibm.com/marketing/iwm/iwm/web/signup.do?source=swg-rtl-sd-wp&S_PKG=ov18162&S_TACT=C42807PW&iio=bcloud&cmp=na_ca_en|pm_cloud|google_sn_ever_present_devops_-_devops_for_dummies_un&ct=c42807pw&cr=google&cm=k&csot=eb&ccy=ca-en&cpb=cloud&cd=-&ck=devops&cs=exact&cot=l&cpg=pcld (c) Ian Davis
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 (c) Ian Davis
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 (c) Ian Davis
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 (c) Ian Davis
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 (c) Ian Davis
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 (c) Ian Davis
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. (c) Ian Davis
The challenge • Development • 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 (c) Ian Davis
The cloud • Provisioning and configuration • As needed • When needed • For the version needed • Simulation of test environments • Eases deployment to production (c) Ian Davis
Cloud Service Models • Software as a Service (SaaS) • Email, 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) (c) Ian Davis
Software as a service • Eureqa • Permits machine learning • Using provided models • http://www.nutonian.com • Leveraging the power of Amazon Cloud • http://formulize.nutonian.com/documentation/eureqa/user-guide/use-the-cloud (c) Ian Davis
Platform as a service • WordPress • End user interacts with software on cloud • End user configures software on cloud (c) Ian Davis
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 (c) Ian Davis
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) (c) Ian Davis
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 (c) Ian Davis
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 (c) Ian Davis