Technical Architecture for Hybrid Cloud Scenarios. Gunther Schmalzhaf, Digital Business Services, SAP

Transcription

1 Technical Architecture for Hybrid Cloud Scenarios Gunther Schmalzhaf, Digital Business Services, SAP

2 Agenda Hybrid cloud What is a hybrid cloud? Technical Architecture for Hybrid Clouds What aspects to care for in hybrid environments? Customer Examples What was the result of first customer deliveries? Service Offering How to get support from SAP? 2

3 Technical Architecture for Hybrid Clouds What is a hybrid cloud?

4 Key Market Trends Gartner predicts that, by 2025, every industry will be transformed by digital business. Gartner Top 10 Strategic Technology Trends for 2016 In 2019, companies will deploy ear-worn wearables, with AI enabled voice interface, as digital assistants for customer-facing roles IDC 2016 By 2020, all enterprises performance will be measured by a demanding new set of digital transformation-driven benchmarks, requiring 20%-100% or better improvements in KPIs. IDC 2016 SAP Historical customer is the CIO, however the business stakeholders have gained power and demanding more / faster innovation driving them to SaaS and niche solutions. 4

5 Key business drivers for digital transformation 5

6 SAP s Modular Suite SAP Cloud Offering 6

7 Hybrid Cloud Cloud Types Cloud types in focus? Public SAAS Cloud Public PAAS Cloud Public IAAS Cloud Private Hosted Cloud SAP Cloud Solutions SAP Cloud Platform Classical SAP On Premise Apps Classical SAP On Premise Apps SF Ariba S/4HANA BO Cloud Fiori Leonardo WebIDE Amazon AWS Microsoft Azure SAP Hosting Partner HANA Enterprise Cloud Customer data center Integration Classical SAP On Premise Apps S/4 CRM BW/4 SRM HCM Private Cloud On-Premise 7

8 Customer Provider Technical Architecture for Hybrid Cloud Responsiblities Public SAAS Public PAAS Public IAAS Private Cloud Cloud Cloud Hosted Cloud Provided by SAP / 3 rd party cloud provider based on SLA SAP solution landscape defined and managed by customer Private Cloud On-Premise Major focus of a technical architecture definition 8

9 Technical Architecture for Hybrid Cloud Aspects of a technical integration Public SAAS Cloud SAP Cloud Solutions Public PAAS Cloud Which integration scenarios are in focus? Which integration component require additional IT infrastructure? SAP Cloud Platform Public IAAS Cloud Classical SAP On Premise Apps SF S/4HANA Fiori WebIDE Which components Ariba BO Cloud Leonardo need to be resized? Amazon AWS Is the entire solution stack protected in case of failure? Microsoft Azure Private Hosted Cloud Classical SAP On Premise Apps SAP Hosting Partner HANA Enterprise Cloud Which non PRD system do I need in the cloud? Customer data center Classical SAP On Premise Apps Private Cloud On-Premise S/4 CRM BW/4 Is my future hybrid implementation secure enough? SRM HCM 9

10 Technical Architecture for Hybrid Clouds Which aspects does the customer have to care for in hybrid clouds?

11 Technical Architecture for Hybrid Clouds Focus Areas Integration Scenarios Define technical architecture for integration middleware and networks from On-Premise to Cloud. Performance and Capacity Define volume and response time requirements for cloud connect for users (UI) and integration (interface) Architect a solution which scales along business requirements IT infrastructure architecture and availability Define technical architecture of on premise components required for integration and network Define a infrastructure consistently surviving unplanned downtimes SW Change Management Landscape / nonprd system landscape Define a SW change management landscape supporting the customer requirements on premise and in the SAAS cloud Define a release strategy which aligns with customer schedules and SAP cloud Security architecture Definition of an Architecture enabling data security via encryption as well as access control 11

12 Technical Architecture for Hybrid Clouds Cloud / On Premise Integration Scenarios Technical Architecture for Integration Overview over the integration concepts and tools (PI, HCI, FTP, 3 rd party) per cloud type (Success Factors, Ariba, Fieldglass, ) Required integration scenarios Overview where the integration tools can be located (on premise or cloud) Required technical architecture components and specs. (FW, load balancer, web server, server, application components for middleware) Load balancing concepts Protocols 12

13 Technical Architecture for Hybrid Clouds Sizing and Capacity Management Delta sizing for integration load for on premise systems and network Identify sizing relevant factors (bandwidth, latency, middleware component size, ) Define sizing relevant components (middleware, network bandwidth/response time, ) Develop a sizing approach for User access Hybrid cloud integration Provide generic sizing methodology for the areas which are under customer control Support definition of SLA s for the cloud negotiated by the customer Initial Calculation Method Educated guess T-Shirt Sizing Simple algorithms with many assumptions Formulas Simple or more complex Questionnaire without formulas For structured questions Quick Sizer Supports user-based and throughput-based sizing 13

14 Technical Architecture for Hybrid Clouds IT infrastructure architecture and availability IT infrastructure architecture Define technical architecture for all on premise components required for integration and network topology connecting the cloud solution Technical definition of standard templates defining all layers from the application stack down to storage All sytems in focus for installation (SAP HANA, classical DB s, SAP AS, non Net Weaver stacks, ) Availability architecture (HA/DR) Alignment concept for availability SLA s to the cloud with local SLA s and procedure for data consistency Availability concept for on premise systems and integration middleware Network and WAN redundancy Cloud Data Center Wide Area Network Data Center DMZ On Premise Network Application Database Server Storage 14

15 Technical Architecture for Hybrid Clouds Software Change Management Requirements Technical architecture definition of a landscape (PRD & nonprd) supporting the SW Change Management procedures of a customer Align nonprd landscape on premise and different options of nonprd systems in the cloud Define a plan to align potentially different maintenance cycles on premise and cloud Support test plan creation for integration Testing Cloud Cloud Cloud Cloud 15

16 Scoping Technical Architecture for Hybrid Clouds Security Scoping Technology Processes People Cybersecurity and Data privacy Confidentiality, Integrity, Availability Data Protection Protection of Intellectual Property Enforcement and evidence Requirements & Measures Monitoring Audit Technology Processes People Cyber-security & Data privacy 16

17 Technical Architecture for Hybrid Clouds What do other customers do?

18 Technical Architecture for Hybrid Clouds How to get support from SAP?

19 Transition to SAP S/4HANA Version 16Q4 19

20 Transition to SAP S/4HANA Version 16Q4 20

21 Service Components Technical Architecture and Infrastructure Work Stream Technical Architecture Workshop (TAI) Advanced Sizing (ADVS) Architecture Overview e.g. Memory areas, delta merges Sizing Sizing & Scalability Verification Final Report Sizing Projection Starting point, 1-n systems Technical Platform e.g. hardware options, virtualization, TDI Final Report Status Technical Platform Definition (TPD) HA/DR, Backup e.g. 1-n data centers, SLA definitions Final Report System Landscape Holistic landscape design Technical Architecture & Infrastructure (TAI) Platform Design Support (PDS) 21

22 Service Components Difference between the two major service offerings What is the difference between Technical Architecture and Infrastructure planning workshop (TAI) and the two flavors of Platform Design Support (PDS) Criteria (*) TAI PDS Technical Platform Definition (TPD) PDS Advanced Sizing (ADVS) Result High level technical architecture outlines (incl. knowledge transfer) of the HANA landscape to enable the customer to kick off a discussion with HW partner, hosting partner and internal groups Detailed architecture definition and verification to be able to prepare the installation of the entire landscape (SAP stack, server, storage, network, cloud,..) Project phase Discover and Prepare phase Explore and Realize (only for infrastructure verification) phase Major content focus of workshop Topic to be covered Usual workshop participants Landscapes HANA and Fiori layer Initial or rough budget sizing, technical platform options, HA/DR, PRD and nonprd Customer and SAP (partner optional) Broad view to all infrastructure layers and components in focus for installation (e.g. HANA, classical DB s, SAP AS, integration stacks, nonsap) Detailed deployment templates covering technical platform options, HA/DR detailed verification, detailed landscape outline Customer, implementation partner, HW partner and/or hosting partner and SAP Detailed sizing results to enable the customer to order required HW components and to strategically define mid term deployment models (on premise and/or cloud) Explore and Realize (only sizing verification) phase HANA, Fiori and SAP AS layer Expert sizing, sizing verification, workload analysis Customer and SAP On premise, hosted private clouds offered by SAP hosting partners and hybrid landscapes * Table only describes an general outline and shape of the offered services. Of course all offerings can be flexibly shaped to a specific customer demand. 22

23 Service Components Difference between the two major service offerings Technical Architecture and Infrastructure planning WS Platform Design Support Technical Platform Definition Platform Design Support Advanced Sizing 23

24 Thank you. Contact information: Gunther Schmalzhaf IT Planning Architect