Upload
others
View
4
Download
0
Embed Size (px)
Citation preview
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Using DevOps to Drive Integration Projects from Microservices to the Cloud Expert Panel
Experts: Joe Kardamis – Sherwin Williams Suresh Poopandi – Multiplan Xander van Rooijen – Rabobank Matt Wright – Rubicon Red Moderator: Robert Wunderlich - Oracle September 22, 2016
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Program Agenda
Welcome and Meet the Experts
Opening Thoughts
Questions and Answers
1
2
3
3
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Confidential – Oracle Internal/Restricted/Highly Restricted 4
Cloud Platform Services for All Enterprise Personas
ORACLE CLOUD PLATFORM
APPLICATION DEVELOPMENT
DATA MANAGEMENT
SYSTEMS MANAGEMENT
Architects and IT Ops
Developers and DevOps
INTEGRATION
Line of Business MOBILE
CONTENT AND PROCESS
BUSINESS ANALYTICS
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Joe Kardamis
• With Sherwin Williams for 5 years
– 3 years as the Services and Integrations Manager
– Grew the team
– Refined processes
– Formalized governance policies
– Integrated Agile and test-centric practices into traditional Service Orientation
5
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Suresh Poopandi
• With Multiplan for 15+ years
– SOA Architect for 5 years
– Propelled Multiplan to follow SOA principles
– Introduced Oracle Fusion Middleware (SOA, Service Bus, and BPM)
– Active member of Multiplan’s Architecture and SOA Governance boards
– Helped to transform Multiplan’s Software Development practices to use Agile Development Methodologies
– Promoted Continuous Integration and Delivery using Bamboo and Automated Quality Assurance Testing
6
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Xander van Rooijen
• With Rabobank for 4 years
– Business Architect for Integration and BPM architecture within CRM domain.
– Leads teams to deliver high quality integrations and stable supporting business processes
– Due to increased demand for faster delivery, Xander has completed extensive research on DevOps practices for Oracle Fusion Middleware implementations
– Pursuing the complete automation of Oracle Fusion Middleware from provisioning of infrastructure to deployment of services and services.
7
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Matt Wright
• CTO and Co-founder of Rubicon Red
– Globally recognized Oracle Platinum Partner
– Awarded thought leader in Oracle Middleware
–Matt is responsible for defining and implementing Rubicon Red’s DevOps and Cloud strategy. • Including MyST, the leading DevOps solution for Oracle Middleware
–Matt co-authored the highly acclaimed “Oracle SOA Suite Developer’s Guide”
8
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
“3 Ways” of DevOps
• The First Way: Systems Thinking emphasizes the performance of the entire system as opposed to the performance of a specific silo of work or department
• The Second Way is about creating and amplifying the right to left feedback loops
• The Third Way is about creating a culture that fosters both continual experimentation, taking risks and learning from failure; and understanding the repetition and practice is the prerequisite to mastery.
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Work in Small Batches Getting Feedback Fast – FAIL FAST
• Faster Feedback
– Validate assumptions
• Solve Problems Quickly
– Easier to find & fix defects
• Reduce Overhead –Organizations get better at things they
do frequently
• Reduce Risk
10
Release
Get Feedback
Improve
Release small chunks of functionality frequently
Get regular validation on the production readiness
of your application
Incorporate feedback rapidly. Fail fast and learn
fast
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
DevOps vs Continuous Delivery
11
Code Build Integrate Test Release Deploy Operate
Agile Development
Continuous Integration
Continuous Delivery
Continuous Deployment
DevOps
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Breaking the Bottlenecks In The Flow
1. Environment Creation
2. Code Deployment
3. Test setup and run
4. Overly tight architecture
5. Development
6. Product Management
Leading A DevOps Transformation: Lessons Learned – Gene Kim
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Technical Debt
Every time we take a “short cut” we create technical debt:
• Manually configure an environment
• Create code without automated tests
• Manually do deployment
Technical debt is what you feel the next time you want to make a change Gene Kim – Author The Phoenix Project
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Relevant Tests should be Applied to Ensure Quality of Assets Early
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Relevant Tests should be Applied to Ensure Quality of Assets Early
1. Make Relevant Tests
– This requires ability to target specific use cases (and not others).
– Challenge: Dependency Management • Replacing them is best, but expensive (Test Data Management, Service Virtualization,
Containerization)
• Accepting them is easy, but weak (results in brittle tests - can you trust them?)
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Relevant Tests should be Applied to Ensure Quality of Assets Early
2. Apply the Tests
– Requires tests are codified in an automatable way
– Test Runners: SoapUI, JUnit, SOA Suite unit tests
3. Use the Tests to Ensure Quality Early – Run on a timer (e.g. cron)
– Run upon check-in (Version Control)
– Run as part of deployment process (Release Orchestration, WLST, Containerization)
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
DevOps at MultiPlan, Inc.
Oracle OpenWorld 2016
Suresh Poopandi
Lead Architect, MultiPlan, Inc.
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Who We Are
• Multiplan is a cost containment company in healthcare space
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Agile Development
• 2 week sprint • 5 sprints in a release cycle • Multiple Agile teams • Twice a day deployment to SQA • 2 weeks of UAT testing • Initiated 4 years ago • Realized the gains associated with Agile development
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
DEV
SQA REG
UAT
PROD
� Build and deploy triggered based on source code
check-in
� Junit, OBR Test Suite, SoapUI Test Suite, SOA Suite
Test
� Artifacts are pushed to Maven repo with snapshot
versioning
� Artifacts are deployed to weblogic, OSB , SOA and
BPM servers
� Fully automated
� Some manual testing
� Automated Service Level testing - SoapUI
� Automated Portal level testing - selenium
� Hard build during hardening sprint
� Automated Regression Testing
� Test Data Warehouse
� User perspective
manual testing
� SoapUI smoke testing
� Selenium based probs
� Some manual checkout
Continuous Integration & Delivery & Deployment
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Continuous Delivery Maturity Model
The Continuous Delivery Maturity Model
Article on InfoQ website
Andreas Rehn, Tobias Palmborg, Patrik Boström
InfoQ website
Build & Deploy
� Currently Intermediate
� Moving towards Advanced by doing
automated database changes
Test & Verification
� Currently Intermediate
� Moving towards automated by doing fully
automated acceptance testing
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Xander van Rooijen – Sept 2016
DevOps at Rabobank
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Deploy = software + infrastructure
23
• Ops responsible for all infrastructure
• Dev responsible for software
• Dev responsible for infrastructure in UAT (Ops as Advisor)
• Ops focusses on monitoring
Present Future
• Causing:
• Configuration issues and failures
• Unpredictable test output
• No trust
• Resulting in:
• Same configuration everywhere
• Predictable test ouput
• No more blaming
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Production issue? Re-install!
24
• Lengthy troubleshooting process
– Due to complex environments
• Much expertise needed to fix
• Automated re-install of failing component
• Troubleshooting afterwards
Present Future
• Causing:
• Long outages with business impact
• Frustration
• Resulting in:
• Focus on resuming service as fast as possible
• Due to automation, decreased need of expertise
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Version control of the environment is more important than version control of code!
25
• Multi-Domain SOA Platform to meet needs of multiple Lines of Business
• Manage Oracle Middleware Infrastructure as code
• MyST Platform Blueprints define Oracle Middleware desired state.
• MyST used to provision multi-domain SOA env. From 30+ days to 2 hours.
• Platform Blueprints version controlled
• Blueprints updated to make configuration changes, MyST then applies required changes.
• 300% ROI over first 2 years
Software defined environments let you treat Oracle Middleware Infrastructure as Code.
So you can easily version control, review, test, promote and deploy your configurations across all your environments.
“Configuration drift and unauthorized configuration
changes account for nearly 80% of all IT service outages” source: Gartner Research
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Re-Provision Non-Prod Environments before each code release
26
Increasing Confidence in release process
PROD PRE TEST CI
Increasing Confidence in build’s production readiness
• Migration of 500-1000 services from JCAPS to Oracle SOA, OSB, MFT & B2B
• Automated provisioning of 65 domains on Exalogic, across dual sites.
• Provisioned initial environments in 30 days with MyST vs 650 days manually.
• 60 Minutes to Re-Provision production equivalent environments.
• Automated build and deployment slashed release time to 15 minutes.
• Approx. 1300+ Releases per year
• 90%+ reduction in defects caused by configuration issues.
• Automated provisioning means we can create new environments in minutes
• Re-provision Non-Prod to eliminate configuration drift – ensures consistency with Production
• Encourages “right” behaviour – i.e. stops manual configuration changes as they will be blown away
• Significantly reduces likelihood of issue deploying to Prod
Issues caused by Configuration Drift are often the most difficult to diagnose and result in many wasted months of man effort to resolve.
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Re-Provision Production for each major code release
27
• Deploy 15 Environments per Major Release, upto 100 servers in PROD
• Approx. 500 servers, split across 15 environments
• From 2-4 months to 5-6 hours to provision a 50 server environment
• 25% reduction in software delivery lifecycle
• Major Release every 3-6 months.
• Zero down time for each major release with Blue Green deployments
• 90%+ reduction in defects caused by configuration drift
Blue Environment
Release N
Router
Green Environment
Release N+1
• Allows time to validate new release is behaving as expected before go-live
• Zero down-time for go-live.
• Makes rollback very simple
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Confidential – Oracle Internal/Restricted/Highly Restricted 28