Enterprise Transformation

Transcription

1 Enterprise Transformation Accelerare facendo leva su un programma di migrazione massiva Angelo Crippa EMEA Enterprise Transformation Milan, 14 th of April , Amazon Web Services, Inc. or its Affiliates. All rights reserved.

2 What to expect from this session The Enterprises and the Transformation journey Business triggers for a Mass Migration initiatives A real case - Pirelli A quick deep dive Lesson learned and useful tips

3 The Transformation journey

4 Transformation principles Transformation, what is it? A common and well accepted definition is a whole scale change to the foundational components of a business, from its operating model to its infrastructure What are the main drivers of Transformation? Changing consumer demand, changing technology and changing competition

5 Today Cloud is the booster of the Transformation Today most of the IT organizations have realized that: Cloud is a game changer, now IT department can focus on creating innovative solutions rather than firefighting everyday problems The ability to innovate has never been more possible and has never happened faster And most of the Business lines have realized that: Cloud enables speed, if something can be done it must be done now, if you don't do it someone else will Cloud is unfolding the ability to give customers the products and services they'd ask for, if they only knew what was possible

6 Customer Value Cloud Stages of Adoption Mass migration become a valuable option when Enterprises reach this level of cloud maturity Hybrid Scaling Cloud-First > > > The enterprise declares that they should be using cloud based solutions for most or all of their initiatives, and reverses the burden of proof for each of their projects from why cloud? to why not cloud?. This removes any limitations on the types of workloads the enterprise is willing to run everything on AWS (brown-field & legacy systems). > > > The enterprise makes investments to sustain long-term IT operations in the cloud. This includes activities such as creating a cloud center of excellence, redefining traditional IT roles, network architectures, security and governance practices, and so on. This will likely include the migration of existing mission-critical applications or data center to be the proof point for institutionalizing these operational capabilities (mass migration efforts) Project > > > AWS complements existing legacy systems and becomes an option for additional projects. This coincides with the customer setting up their hybrid architecture using VPC and Direct Connect, and possibly a deeper contractual relationship through enterprise support and/or an enterprise agreement > > > AWS is evaluated and vetted on a project-by-project basis to solve specific needs on a one-off basis Cloud Adoption Over Time

7 The Business triggers

8 The challenge become an opportunity Cloud adoption - initial steps (PoC, Pilots, non production or stand alone production workloads) In house IT??? Cloud IT But what about the majority of the apps? (typically thousand of workloads) And what about the time & cost constrain? And what about the other business drivers other than agility and innovation? Cloud native delivery (new custom apps, 3 rd parties packages) >>> the answer is to start a mass migration to the cloud project <<<

9 Mass Migration characteristics In house IT from 30-40% to 100% of Enterprise applications multi year project with detailed preparation phase specific non negotiable allocation of IT budget external support for migration assets and methodology one-of-the-kind project with highly automated phases specific governance model with specific roles Cloud IT Skills mapping (outside / inside) Redefine priorities Strong CxO sponsorship Cross-organization Business ownership Please note that mass migration is happening since decades but today Cloud represent a real option and there are some valid business triggers for starting this journey

10 Some business triggers for mass migration Trigger Termination of an outsourcing contract and / or Global SW vendor agreement Very old IT infra on premises Bold cost cutting initiative Rapid change in business direction Simplification / innovation of some mission critical applications (costly, risky and difficult to change) Description Due to multiple reasons (i.e. unsatisfactory delivery, savings not delivered, lack of flexibility from SW vendors) an Enterprise is obliged to migrate to cloud in order to rebuild a new data Center Sometimes an Enterprise has no chance / budget availability to refresh its own IT infra and the cloud is the natural answer to this problem Some Enterprises businesses are not performing so moving to cloud could represent a short term answer to shareholder and market influencers A leadership change (ie CIO, COO or CEO) can drive a new IT agenda, accelerating the cloud adoption through some bold steps, realigning IT spend with Business Goals The Enterprise reached an unmanageable level of complexity in many mission critical application, so the strategy is to simplify and innovate using more efficient / cost effective platform

11 A real case - Pirelli

12 A quick deep dive

13 A Migration Methodology is not an option For Mass Migration, a solid and proven methodology is a must It is a guide for both customer and supplier It is key for building an holistic view about the entire program It will enable asset reuse that reduces mistakes and wasting time It defines a set of effective quality gates and program check points It helps in defining the skill mapping needed for the program It define roles and responsibility during the program It enables efficiency improvement during the program It is a consistency insurance versus changes in the team

14 Assess the applications and define the move AWS Cloud Migration Framework

15 Assess the applications and define the move AWS Cloud Migration Framework

16 Assess the applications and define the move AWS Cloud Migration Framework

17 Define how to move the applications The migration patterns Manual Install Manual Config Rehosting (Lift and Shift) Automate Use Migration Tools Manual Deploy Determine Migration Path Modify underlying Infrastructure Transition Discover/Assess/Prioritize Applications Validation Production Retain / Not Moving Retire / Decommission Purchase COTS/ SaaS & licensing Manual Install & Setup Redesign Application/ Infrastructure Architecture App Code Development Full ALM / SDLC Integration

18 Application Modernization / Change Effort The migration patterns description Label Name Pattern Description Examples R1 Retire Application and host decommission on source No migration to target Application owner approvals needed Existing Decomm Program Scope SunOS, SCO; Clustered host for DR, alternative HA hosts R2 / R2a Retain Customer will keep host / application in their source environment Minimal analysis/validation of scope and application affinity Dependency on integrating service management Some host will need to be Re-hosted into target (i.e. Lift and Shift) Mainframe AIX host / applications Specific GEO locations (exceptions) R3 Re-Hosting Like for Like application migration to target cloud Minimal effort to make the application work on the target cloud infrastructure (Minimal application layout change) Storage migration will be needed (without conversion) UAT - Some level of application testing Simple to Medium V2V, P2V Storage: Local to DASD RHEL 6 above Win 2008 above Lift & shift R4 Re-Platform Up-Version of the OS and/or database onto the target cloud (same type) Storage migration will be needed (without conversion) Some level of application changes Application reinstallation on the target UAT is highly recommended W2K3 to Win 2012; Win 2008 below; RHEL below; Oracle 8 to 11; All databases New application releases All clusters (MS cluster, DR) MS SQL same technology (RDS) R5 Re-Factoring OS and/or database porting (changing OS or database type) Middleware and application change to cloudify an application Data conversion; Database to AWS RDS UAT required AIX to Linux Oracle to SQL; SQL to Aurora Middleware, IBM products R6 Re-Purchasing / Re-Architect Application architecture changes may also require Up-Version or Porting Middleware, data modernization; application consolidation / stacking UAT required; HPC Grid, No ITIL Any custom application chg Complex / Highly complex application migration

19 Application Modernization / Change Effort The migration scope (illustrative) Label Name Pattern Description Percentage over the total R1 Retire Application and host decommission on source No migration to target Application owner approvals needed 10% R2 / R2a Retain Customer will keep host / application in their source environment Minimal analysis/validation of scope and application affinity Dependency on integrating service management Some host will need to be Re-hosted into target (i.e. Lift and Shift) 5% R3 Re-Hosting Like for Like application migration to target cloud Minimal effort to make the application work on the target cloud infrastructure (Minimal application layout change) Storage migration will be needed (without conversion) UAT - Some level of application testing 40% R4 Re-Platform Up-Version of the OS and/or database onto the target cloud (same type) Storage migration will be needed (without conversion) Some level of application changes Application reinstallation on the target UAT is highly recommended 30% R5 Re-Factoring OS and/or database porting (changing OS or database type) Middleware and application change to cloudify an application Data conversion; Database to AWS RDS UAT required 10% R6 Re-Purchasing / Re-Architect Application architecture changes may also require Up-Version or Porting Middleware, data modernization; application consolidation / stacking UAT required; HPC Grid, No ITIL 5%

20 The migration complexity (illustrative) Very Low Basic workload, current/supported OS, known environment, no database, projected to migrate with basic tools. Few dependencies and can likely sustain a scheduled outage with minimal impact Low Basic workload, may require additional effort to determine environment, no database, may require re-platforming, can likely sustain a scheduled outage with minimal impact to business Medium No database, can sustain longer outage with some planning and advance notice, instances in prod or unknown may impact business applications if not available for an extended period High Workload may include database, or system may include greater than five disks. Requires some additional assessment and planning prior to migration. Greater potential to impact business There are additional factors that can influence the complexity and can be used for performing a weigh analysis: Is the application load balanced Does the application require re-platforming How critical to the business is the application Are there special application security concerns Does the application require a specific SLA What is the environment (Prod, Dev, Test) Very High Workload may include database or complex system configuration (e.g.: numerous disks). Many dependencies. Require advanced detailed assessment and planning. High-touch migration

21 Migration Factory For Mass Migration the migration factory is a mandatory step to implement

22 AWS Partners ecosystem Premier Consulting Partners

23 Partnering with Top Brand Software on AWS Enterprise Software to meet your business needs

24 Lessons learned and useful tips

25 Foundation for mass migration to Cloud Design and architecture of the cloud environment is important for realizing cloud benefits such as agility and cost savings - things to check / verify / build : Networking Security Governance Data mgmt Operations Convergence of on-premises and cloud IP scheme and addressing VPC and subnet Account configuration SSO Access policies Compliance Intrusion detection & prevention Logging Billing & cost management Service catalogs Configuration management SLA/SLO Retention policies Storage optimization Data quality Backup Disaster Recovery Notifications & alerting Application level awareness Service desk integration

26 Management reporting topics Mass migration initiative is a data intensive project and an iterative reporting system must be organized along (at least) the following streams Technical ie solution design and architecture Commercial - ie contractual track and change management Organizational ie GEO alignment and related roadblocks Finance ie amortization, write off, cash flow Legal and compliance People and related HR implications Security and privacy Marketing

27 Conclusion Mass migration to cloud needs be accompanied by transformation (of technology, processes and the organization) why? Most applications are not natively cloud ready and alternative architectures and deployments constructs need to be considered and adopted Automation provides new opportunities for orchestration, innovate and providing end users with self service functionality increasing productivity Governance needs to be refactored to ensure compliance and control is maintained in the new environment Stakeholders change Application owners become major player with the move to infrastructure as code. Its not just about infrastructure anymore and business become more involved in decision making

28 Conclusion Mass migration to cloud is different case by case, but some common evidences are reported below: Change is hard but the reward is large Exec Sponsor & Steering committee are critical Engage the business units early and include them in the journey Understand desired outcomes (tangible & intangible) What / why catalyst for change Do the POC s they provide vital learning s & are a valuable point of reference (validation) of what is possible Hybrid team (Enterprise, AWS, SI s) is a proven model - it will save time & money in the short and long term

29