JOURNEY TO AS A SERVICE

Transcription

1 JOURNEY TO AS A SERVICE CONTAINERIZATION JULY 2017

2 THE DIGITAL ERA EVOLVED IT TO BUSINESS STRATEGY Siloed, legacy, de-centralized, multi vendor setup. IT product focused. AO Operations IO Operations Wall of Confusion Wall of Confusion AO Innovation IO Innovation Wall of Confusion Business Process Application Middleware Data OS Virtualization Servers Storage Network Security limited integrated AO Operations IO Operations Wall of Confusion Wall of Confusion AO Innovation IO Innovation Wall of Confusion Business Process Application Middleware Data OS Virtualization Servers Storage Network Security limited integrated to a shared, harmonized, cloud-based, everything as a service, customer centric Proactively drive business innovation supported by new technologies. Business Agile/DevOps Business Process as a Service Software as a Service Business Process as a Service Software as a Service Platform as a Service Private Cloud Hybrid Cloud Public Cloud Infrastructure as a Service Maximize Business Value Drivers Facilities Facilities Infrastructure pressure drivers Copyright 2017 Accenture All rights reserved.

3 CLOUD & AGILITY IS ASSUMED: IT S NOT A QUESTION OF IF, BUT WHEN 30 % OF ALL APPLICATIONS will be migrated to Public Cloud by 2018 BY % OF COMPANIES will be using public cloud PUBLIC CLOUD GROWTH $173B MORE THAN 2016$38B 2026 of enterprises will have at least half of their infrastructure on cloud- 60 % based platforms by 2018 CLOUD WORKLOADS 44 % 8.9 % Growth for on-premise Annual Public Cloud Growth Copyright 2017 Accenture All rights reserved. 3

4 BUT CHALLENGES EXIST FOR ENTERPRISES LACK OF CLOUD PROVIDER TRANSPARENCY OF WORKLOADS making it difficult to manage consumption NEED TO BE agile and flexible DEMANDS ON IT RESOURCE ARE DOUBLING but budgets remain flat DRIVE DOWN costs SHIFT TO EVERYTHING as-a-service MANAGE INCREASED CUSTOMER needs and expectations MAINTAIN A BLIZZARD OF separate accounts INNOVATE faster CREATE A HYPER SCALE always on, available everywhere environment Copyright 2017 Accenture All rights reserved. 4

5 WHAT IS A CONTAINER Container allows to easily create lightweight, portable, self-sufficient containers from any application, and which are independent of hardware, language, framework, packaging system and hosting provider Based on OS-level virtualization Containers start in milliseconds Independent of hardware, language, framework, packaging system and hosting provider Isolated from other containers but sharing the host s resources Easy distribution of ready-made containers via the a registry Lpar 1 einfra Platform + Lpar 2 Lpar 3 Cont. 1 Cont. 2 Cont. 3 App 1 App 2 App 3 Java 6 Java 6 Java 6 Web Logic 5 Web Logic 5 Web Logic 5 Guest OS Guest OS Guest OS CPU 1 CPU 2 CPU 3 App 1 App 2 App 3 Java 8 Java 8 Java 8 JBoss EAP 7 JBoss EAP 7 Container Engine JBoss EAP 7 Hypervisor Server (on premises) Host OS (RHEL) Server (AWS) Copyright 2017 Accenture All rights reserved. 5

6 CONTAINERIZATION VALUE PROPOSITION FOR DIFFERENT STAKEHOLDERS Developers Self-service; concentrate on building applications Use any technology stack or application framework Create and run any containers in self-defined environments (dev, prod, CI/CD, test, acceptance, performance) IT Management Run on any infrastructure, private, hybrid or public Increase resource usage and control infrastructure spend Centrally manage users, resource constraints and allocations Enable standardized practices and patterns, e.g. secrets management, load balancing, deployments Business Faster time to market for new services and products Lower IT costs Reduce deployment failure Copyright 2017 Accenture All rights reserved. 6

7 DRIVEN BY BUSINESS VALUE ENTERPRISES ARE TURNING TOWARDS CONTAINER-BASED INFRASTRUCTURES Enablers Legacy workloads Cloud Infrastructure Containers Analytics and Big Data New Application Architectures Orchestration Microservices Speed Agility Scale Resiliency Flexibility Cost Version Control Isolated apps Drivers Copyright 2017 Accenture All rights reserved. 7

8 DEVOPS AUTOMATION Terminology CI/CD pipeline Capability model CI/CD running pipeline 1. Creating the Application Dev Team (Clear Basic, Fusion, Java, etc.) Work Management Process Check-in, Store in Git Code Review SCM Identify code changes, Compile & Package Libraries App Asset Mgmt Automation orchestration Test Data Scr Environment Configuration Tailor to Env App 2. Deploying the application Deployment Persistent Envs Dev Test Prod Automated Test 3. Testing the application Copyright 2017 Accenture All rights reserved. 4. Visualisation of Delivery 8

9 EVOLVING DEVOPS AUTOMATION Increased Speed of delivery only limited by infrastructure and automation Reliable delivery through continuous evaluation of delivery progress and removal of manual errors through automation Increased Developer Productivity by: 24/7 Model A Continuous delivery: Automated Application Deployment into longlived Environments Faster feedback from quality assessments Removal of non-development activities Reduction of noise from non-developer caused defects Increased Transparency of quality & delivery progress Increased Speed of delivery only limited of automation for environment setup and deployment. Reliable delivery through continuous evaluation, removal of manual work and environment variability Model B - Automated environment provisioning: Cloud provisioning of Environments is part of the Deployment process achieving zero-downtime deployments Increased Developer Productivity by focus on development only Increased Transparency of quality and delivery progress Production releases with minimised downtime and recovery time from failure Elasticity in environments improving performance & availability Increased Speed of delivery only constrained by development capacity Releases to production are completely non-invasive Elasticity in environments addressed performance and availability concerns and ability to move around within cloud constraints Model C Container-based Deployment: Container-based deployment of Microservice based application services Copyright 2017 Accenture All rights reserved. Deployment speed is at OS process level instead of VM level for model B 9

10 CONTAINER PLATFORM AS A SERVICE Cloud Infrastructure Copyright 2017 Accenture All rights reserved. 10

11 CONTAINER PLATFORM AS A SERVICE Cloud Infrastructure OpenShift v3 is an example of a PaaS in development that uses Kubernetes in its core, offering additional services such as: build/deployment, monitoring/reporting, tools/templates, etc. Traditional PaaS Services Monitoring/Reporting Development tools Middleware (languages, app servers, databases) Team/Management Build to Deployment Templating Scheduling Scaling/Provisioning Service Discovery Load Balancing Portability Container Services Container platform like OpenShift Container platform like OpenShift Container platform like OpenShift Container platform like OpenShift Container platform like OpenShift Container platform like OpenShift Kubernetes master component Replication Controller Labels used by Replication Controller Kubernetes Services Hosted/hybrid/private Operating System - Copyright 2017 Accenture All rights reserved. 11

12 THE BENEFITS OF MODERNIZING LEGACY WORKLOADS WITH CONTAINERS DEPLOY AND SCALE IN MINUTES Accelerate deployment times Seamless scalability IT efficiency APP PORTABILITY IN MINUTES No changes to existing environment Frictionless dev to prod workflow Cloud portability OPEX AND CAPEX SAVINGS Infrastructure optimization and consolidation Reduce VMs and OS licensing costs Accelerated path to cloud SECURE APPS AT SCALE Secure app isolation Application trust across the lifecycle Vulnerability and thread scanning CAPITAL AND OPERATIONAL EFFIENCY DRIVEN ROI Copyright 2017 Accenture All rights reserved.

13 STRUCTURED CONTAINER MIGRATION CONTAINER STRATEGY AND IMPLEMENTATION QUALIFICATION AND ASSESSMENT MIGRATION & ROLLOUT DEFINE OVERALL CONTAINER STATEGY AND IMPLEMENT A CONTAINER PLATFORM Defines how to integrate containers in the existing infrastructure, DevOps process, teams and application lifecycle practices. Assess and select a suitable container platform/caas and implement it according to the container strategy and architecture This is an optional step, if the client already has a CaaS platform in place IDENTIFY APPLICATIONS IN SCOPE, PRIORITIZE AND ESTIMATE MIGRATION EFFORT Create an inventory of the applications in scope for the migration, and assess their migration readiness Leverage Accenture assets to support the qualification and prioritization, as well as the effort estimation EXECUTE MIGRATION AND ROLL OUT APPPLICATIONS Factory team migrates applications Leverage reference architecture and container best practices as well as previous experience in a repetable and consistent manner Copyright 2017 Accenture All rights reserved.

14 APPENDIX 14

15 ACCENTURE DEVOPS PLATFORM CONTAINER BASED Cloud Infrastructure Copyright 2017 Accenture All rights reserved.

16 Copyright 2017 Accenture All rights reserved.