Agile, ITITL, Cloud
How DevOps brings it all together
Robert Michel
+49 (0)170 6347249
michel@de.ibm.com
© 2013 IBM Corporation2
Agenda
• DevOps
– Challenges
– Principles
– Solution
• Q&A
Collaborative Development &
Operations
Delivery challenges &Typical root causes
© 2013 IBM Corporation4
Why do we need DevOps? – 2 Examples
Customer 1 Customer 2
Situation
• Complex J2E environment
• Many interdependent components
• New release every 1-2 months
Challenges
• Change window on weekend too short
• Each production deployment fails and
takes 1 week to get it running
• Different deployment approaches:
• Test: fresh install
• Production: upgrade install
Situation
• 5+ test environments with
• Different OS versions
• Different platforms (Linux, AIX)
• Different J2E versions
Challenges
• Time consuming defect determination
• Performance test takes 2 months
• No production relevant test results
• Can’t test N-1
© 2013 IBM Corporation5
Typical question within complex IT-Organisations
• We are using agile development practices. Why does it still take months to
release new applications?
• Why is there so much rework to do for every new release?
• Virtualization and Cloud are part of our infrastructure. Why does it still take
so much time to provide a proper test environment?
• Why do we still have significant quality issues despite our testing guidelines
and processes?
© 2013 IBM Corporation6
Code BuildRequirements
Reasons for issues
Design
Deploy Test
Change & Configuration Management
Deploy Test
Deploy Test
Deploy Test
System Test
Integration Test
Acceptance Test
Component Test
Production
• Staging and Testing require time and
resources
• Approx. 1/3 to 2/3 of time is spent for
setup and configuration
• Often different processes are used
• No consistent Configuration
Management throughout different
environments
• Knowledge kept within few individuals
Collaborative Development &
Operations
Agile development and DevOps
DevOps principles
© 2013 IBM Corporation8
People
Process
Information
DevOps Principles & Values
• Collaborate across disciplines
• Develop and test against a production-
like system
• Deploy frequently using repeatable
and reliable processes
• Continuously validate operational
quality characteristics
© 2013 IBM Corporation9
Continuous Feedback
 “Shift-Left” – shifting operational
concerns and processes earlier in
the development lifecycle
 Collaborate on the creation of
reusable test environment patterns
 Common tools for planning,
tracking, and reporting application
and infrastructure changes
IMPACT
Predictable and accelerated software delivery
optimized around a production-like delivery pipe
Takes minutes / hours to deliver changes versus
weeks/months
Agile
Dev
Design
Prioritize
Build
Test
Agile
OpsTest
Monitor
Publish
Deploy
Collaboration between Development & Operation
© 2013 IBM Corporation10
Delivery Pipeline
Code Build
Requirement
Management
DevOps Focus – Delivery Pipeline
Design Deploy Test
Change & Configuration Management
• Complete Automation based on results of the previous
steps
• Sourcecode
• „Infrastructure as Code“
• Patterns
• Platform Configuration
• Build Definitions
• PackagingDeployment
Patterns
Configuration
Automation Delivery
Pipeline
Collaborative Development &
Operations
Concepts and Solutions
© 2013 IBM Corporation12
Build Automation Deployment Automation Test Automation
Standardized, repeatable and automated „Delivery Pipeline“
Release Automation
Continuous Integration of
source code Integrated Deployment Model Continuous Testing
Application ConfigurationEnvironment
Cloud = continuous provisioning and deprovisioning of test stages
dependent on application versions to test.
Artefact Repository
DevOps – Capability View
© 2013 IBM Corporation13
DevOps – What do I need a Cloud for?
Layer Change Frequency
Application Config
Application
Middleware Config
Middleware
OS Config
OS
Hardware
Cloud Benefits
• Deploy often
• Control everything
• Recreate n-1 easily
• Provide standardized
deployment patterns
Cloud
Automation
Deployment
Automation
© 2013 IBM Corporation14
ITILAgile
DevOps – Process View
OperateDevelop Test
OperateDevelop Test
Agile
ITIL
• Separation of duty in silos
• No end-2-end visibility
• Limited information exchange & process
interfaces
• Extend scope of agile principles and ITIL
processes
• Linked data vs. Integrated data &
processes
• Limited process changes necessary
• Restructured Roles & Responsibilities
(How do ITIL and Agile fit together?)
© 2013 IBM Corporation15
Benefits
– Faster implementation of business requirements
• Shorter test cycles
• Keep up with the dynamic of agile development
– Higher software quality
– Cleaner transition from development to production
• repeatable
• automated
• auditable
Thank you!
Backup
© 2013 IBM Corporation18
Line of
Business
DevOps – Related Themes and Tasks
Plan and Measure
Develop and Test
Release and Deploy
Monitor and Optimize
© 2013 IBM Corporation19
Line of
Business
DevOps – Modular & Integrated Solutions
Rational Quality Manager
Rational Test Workbench
Rational Test Virtualization Server
SmartCloud Control Desk
SmartCloud
Application Performance Management
Rational Team Concert Jenkins
Rational Build Forge
uBuild
Rational Focal Point
Rational Requirements Composer
© 2013 IBM Corporation20
Agile Development and DevOps
Functional
Testing
Acceptance
Testing
Production
Gap
Development
Code
Operations
Business
Services
Customers
Desire for fast
and continuous
innovation
Line of
Business
Requirements

Agile, ITIL, Cloud – Mit DevOps in die Zukunft

  • 1.
    Agile, ITITL, Cloud HowDevOps brings it all together Robert Michel +49 (0)170 6347249 michel@de.ibm.com
  • 2.
    © 2013 IBMCorporation2 Agenda • DevOps – Challenges – Principles – Solution • Q&A
  • 3.
    Collaborative Development & Operations Deliverychallenges &Typical root causes
  • 4.
    © 2013 IBMCorporation4 Why do we need DevOps? – 2 Examples Customer 1 Customer 2 Situation • Complex J2E environment • Many interdependent components • New release every 1-2 months Challenges • Change window on weekend too short • Each production deployment fails and takes 1 week to get it running • Different deployment approaches: • Test: fresh install • Production: upgrade install Situation • 5+ test environments with • Different OS versions • Different platforms (Linux, AIX) • Different J2E versions Challenges • Time consuming defect determination • Performance test takes 2 months • No production relevant test results • Can’t test N-1
  • 5.
    © 2013 IBMCorporation5 Typical question within complex IT-Organisations • We are using agile development practices. Why does it still take months to release new applications? • Why is there so much rework to do for every new release? • Virtualization and Cloud are part of our infrastructure. Why does it still take so much time to provide a proper test environment? • Why do we still have significant quality issues despite our testing guidelines and processes?
  • 6.
    © 2013 IBMCorporation6 Code BuildRequirements Reasons for issues Design Deploy Test Change & Configuration Management Deploy Test Deploy Test Deploy Test System Test Integration Test Acceptance Test Component Test Production • Staging and Testing require time and resources • Approx. 1/3 to 2/3 of time is spent for setup and configuration • Often different processes are used • No consistent Configuration Management throughout different environments • Knowledge kept within few individuals
  • 7.
    Collaborative Development & Operations Agiledevelopment and DevOps DevOps principles
  • 8.
    © 2013 IBMCorporation8 People Process Information DevOps Principles & Values • Collaborate across disciplines • Develop and test against a production- like system • Deploy frequently using repeatable and reliable processes • Continuously validate operational quality characteristics
  • 9.
    © 2013 IBMCorporation9 Continuous Feedback  “Shift-Left” – shifting operational concerns and processes earlier in the development lifecycle  Collaborate on the creation of reusable test environment patterns  Common tools for planning, tracking, and reporting application and infrastructure changes IMPACT Predictable and accelerated software delivery optimized around a production-like delivery pipe Takes minutes / hours to deliver changes versus weeks/months Agile Dev Design Prioritize Build Test Agile OpsTest Monitor Publish Deploy Collaboration between Development & Operation
  • 10.
    © 2013 IBMCorporation10 Delivery Pipeline Code Build Requirement Management DevOps Focus – Delivery Pipeline Design Deploy Test Change & Configuration Management • Complete Automation based on results of the previous steps • Sourcecode • „Infrastructure as Code“ • Patterns • Platform Configuration • Build Definitions • PackagingDeployment Patterns Configuration Automation Delivery Pipeline
  • 11.
  • 12.
    © 2013 IBMCorporation12 Build Automation Deployment Automation Test Automation Standardized, repeatable and automated „Delivery Pipeline“ Release Automation Continuous Integration of source code Integrated Deployment Model Continuous Testing Application ConfigurationEnvironment Cloud = continuous provisioning and deprovisioning of test stages dependent on application versions to test. Artefact Repository DevOps – Capability View
  • 13.
    © 2013 IBMCorporation13 DevOps – What do I need a Cloud for? Layer Change Frequency Application Config Application Middleware Config Middleware OS Config OS Hardware Cloud Benefits • Deploy often • Control everything • Recreate n-1 easily • Provide standardized deployment patterns Cloud Automation Deployment Automation
  • 14.
    © 2013 IBMCorporation14 ITILAgile DevOps – Process View OperateDevelop Test OperateDevelop Test Agile ITIL • Separation of duty in silos • No end-2-end visibility • Limited information exchange & process interfaces • Extend scope of agile principles and ITIL processes • Linked data vs. Integrated data & processes • Limited process changes necessary • Restructured Roles & Responsibilities (How do ITIL and Agile fit together?)
  • 15.
    © 2013 IBMCorporation15 Benefits – Faster implementation of business requirements • Shorter test cycles • Keep up with the dynamic of agile development – Higher software quality – Cleaner transition from development to production • repeatable • automated • auditable
  • 16.
  • 17.
  • 18.
    © 2013 IBMCorporation18 Line of Business DevOps – Related Themes and Tasks Plan and Measure Develop and Test Release and Deploy Monitor and Optimize
  • 19.
    © 2013 IBMCorporation19 Line of Business DevOps – Modular & Integrated Solutions Rational Quality Manager Rational Test Workbench Rational Test Virtualization Server SmartCloud Control Desk SmartCloud Application Performance Management Rational Team Concert Jenkins Rational Build Forge uBuild Rational Focal Point Rational Requirements Composer
  • 20.
    © 2013 IBMCorporation20 Agile Development and DevOps Functional Testing Acceptance Testing Production Gap Development Code Operations Business Services Customers Desire for fast and continuous innovation Line of Business Requirements

Editor's Notes

  • #11 Green == Existing capabilitiesOrange == New capabilities