Upload
others
View
7
Download
0
Embed Size (px)
Citation preview
Accelerating Digital Innovation with DevOps & App Modernization
Principal DevOps Consultant Principal App Mod Consultant VP, Digital Innovation Group
Brian Minisi Anthony Rizzo Brendon Birdoes
[email protected] [email protected] [email protected]
Our Presenters
About Us
Our Profile• 17-year MSFT Partner• 12 offices nationwide, 3 in
India• 900+ consultants• 700+ clients• 2000+ engagements
Our Strategic and Technical Offerings• Artificial intelligence• Data and analytics• Cloud infrastructure, migration and strategy• Custom application development• Continuous Delivery and DevOps• CRM and digital workplace• Business advisory services• Managed services• And more!
National Clients
OUR VISION
vision.neudesic.com
11:30 AM
12:30 PM
1:30 PM
2:00 PM
Today’s Agenda
Registration & Check-in
Lunch and Session One
• DevOps and the Hybrid Cloud Approach to IT Modernization
• How DevOps accelerates software delivery, with key principles and patterns
• Taking a broad view to address data, apps, infrastructure and people challenges
• Understanding and applying the six Rs of app modernization:Retiring, replacing, remediating, re-architecting, re-platforming, and re-building
Session Two and Moderated Panel App modernization strategies and mistakes
• Laying the cultural foundation for DevOps• Real world use cases about the hybrid cloud roadmap
Q&A
1. Is your org implementing DevOps?
2. How well is it going?
3. Is your org using the cloud?
4. Does your org have expensive and clunky legacy apps?
QUESTIONS
Continuous Delivery and DevOps
Application Modernization
Cloud Migration Strategy
OUR WORKSHOPS
App Modernizationand Cloud Migration
80% IT BudgetSpent on maintenance and upkeep
Application Changesbecome too complex, difficult,and/or costly to implement
Stuck Keeping the Lights Onmaking it difficult to keep up with
accelerated standards
Application Modernization focuses on improving the value proposition of our technology.
It re-positions IT as an asset, not a cost-center.
Improving the way value is delivered
Improving the way value is designed
Improving the way value is built
Improving the way value is run
1. Process 2. Architecture 3. Technology 4. Infrastructure
Components of Application Modernization
App Modernization with Cloud Migration
Existing Application
APP
ContainersContainer Platform
On-PremisesInfrastructure
Platform
PaaSApplication Platform
ServerlessIaaSInfrastructure Platform
“lift & shift”
Modern Infrastructure
Re-platform to modern cloud
ContainerizeApplications
Re-architect apps for scale with
containers
ModernMicroservices
Add new services or start peeling off
services from monolithic code
What happens if we modernize, but don’t migrate?
Critical Thinking Time…
What happens if we migrate but don’t modernize?
Critical Thinking Time…
What benefits do we get from a holistic modernization and migration strategy?
Critical Thinking Time…
RetireRemove the application or platform completely.
ReplaceReplace the application or platform with a new version or competing solution.
RemediateInvest in extending the lifeline of the application or platform.
Re-ArchitectRedesign the application or platform to meet demands.
Re-PlatformRedesign the application to run on different infrastructure.
RebuildRewrite the application to remove overwhelming technical debt or change the implementation.
Modernization and Migration Strategies
• Establish migration objectives
• Utilize Tools to understand dependencies
• Create Move Groups
• Create Backlog and Order
• Disposition of Components
• Initial Cloud cost estimate
• Initial Architect & Design
• Domain deployment
• Integration
• Data Migration
• Performance Objectives
• Quality Objectives
• User Acceptance
• Failover Testing
DiscoveryDevelop our migration plan
MigrateMove to the Cloud
ValidateQuality and Performance
• Go/Live Support
• Governance and Cost Control
OperationalizeThe Cloud platform
Establish FoundationsFor a successful cloud journey
• Governance
• Communication and Network
• Implement Architecture & Design
• Subscription Establishment
• Roles and Responsibilities
• Organizational Readiness
The Modern Datacenter
• Communication/Availability
• Security/Identity
• Services/Operations
What Makes Up The Modern Datacenter?
IT BUSINESS FOUNDATIONS• Business Strategy for Cloud
• IT Strategy for Cloud
• Financial Governance
• Organizational Adoption
OPERATIONALFOUNDATIONS• Governance Control Gate
• Subscription Management
• Performance Management
• Administrative & Maintenance
• Management and Monitoring
TECHNOLOGYFOUNDATIONS• Workloads• Platform & Infrastructure• Security & Dev/Ops• Change Management• Staff Readiness
Cloud Governance Framework
SHARED SERVICES• Defined catalog of services • Consistent operational
reporting against the entire Modern Datacenter
• Definable metrics and OLA’s to adhere to
DEFINED ARCHITECTURE (COE)
• Patterns and practices • Change procedures
• Automated process control
MANAGE SERVICES• Systems should be self healing • Runbooks and playbooks • Root cause and remediation
to automation • SLA’s
How to Manage The Modern Datacenter
Modern DatacenterManaged Services
Service and Operations is the path to realizing the full ROI of Modern Data Center.
Service and Operations will help standardize & solidify processes while also making processes and systems scalable.
Through benchmarking these processes an organization begins to realize the full ROI of the Modern Data Center.
The Modern Data Center also comes with modernized processes that streamline tasks saving time and money.
Service and Operations – Why?
• Provides operational agility and efficiency
• Increase business performance by continually evolving processes in ways that increase responsiveness and innovation
• Streamlining operations through automation
• Governance for control and maintaining operational efficacy
• Delivering standardized processes and procedures
• Security best practices
• Cost Containment which are built into the processes through proper governance
Service and Operations
Continuous Delivery
Continuous Delivery – 3 Ways
Flow Feedback Experiment
Limit work-in-process
Make work visible
Reduce batch size
Identify and elevate constraints
Eliminate hardships and waste
Reduce handoffs
Flow
See problems as they occur
Work safely in a complex system
Swarm and solve problems to build knowledge
Enable optimization for downstream
Keep pushing quality close to the sourceFeedback
Create a safety culture
Enable continuous learning
Institutionalize continuous improvement
Inject resilience into daily work
Leaders reinforce learning culture
Transform local discoveries to global knowledge
Experiment
Continuous Integration
Continuous Delivery
Continuous Learning
Continuous Improvement
Automation & Collaboration
The ”Continuous” Continuum
CI/CD Pipeline Overview
Production Feedback
VersionControl
Build UnitTest
Deploy Deploy toProduction
Measure &Validate
Version Control
Trunk-based Development
Commit to pushing changesto trunk
Commit Early & Often
Push changes to trunk several times throughout the workday.
Minimize Branching
Branches should be fewand short lived
Everything in Source
Everything goes in source control-code, database scripts, configuration, infrastructure
Build
Every Change Triggersa Build
Commit should build the codebase to ensure code can integrate.
Independent Build
Build the changes outside of developer tools with scripts
Notify on Failure
All team members are notified when builds fail
Visible Dashboards
Internal team members and external stakeholders can see the history of build quality
Test
Automate Tests
Every build should run baseline tests and code analysis
Threshold Failure
Fail if test coverage or code analysis are under threshold
Test Coverage
The amount of code coveredby tests should be trackedand managed
Visible Dashboards
Internal team members and external stakeholders can see the history of test quality
Deploy
Automate Deployment
All deployments are scripted automated
Test the Deployment
A series of verification tests should quickly verify the build
Realize from Build
The build process triggersthe release process
Visible Dashboards
Internal team members and external stakeholders can see the release history
Q&A