SAP HANA TDI Tailored Datacenter Integration with EMC
 

Like this? Share it with your network

Share

SAP HANA TDI Tailored Datacenter Integration with EMC

on

  • 411 views

 

Statistics

Views

Total Views
411
Views on SlideShare
405
Embed Views
6

Actions

Likes
0
Downloads
3
Comments
0

1 Embed 6

https://twitter.com 6

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • With the EMC VNX8000 storage models we created a solution based on 40 B440 M2 server – each with 512 GB memory – and 4 VNX8000 storages. <br /> Each storage provides the performance and capacity for the OS, HANA Data, HANA Log and HANA Share on 10 B440 server – regardless if multiple virtual HANA systems or a single one. <br /> <br /> We scale to 40 Blades and 4 Storages per cell to guaranty the performance and a design with no over-subscription. <br /> <br /> Boot Storage is based on FC / FCoE LUNs (this can change as PXE and persistent NFS root OS is supported by UCS-Director) <br /> All other storage, i.e. HANA data and log is based on NFS shares <br /> <br />
  • We talked a lot about the cell design, now lets see how the solution scales beyond the 40 nodes. <br /> <br /> For scalability we defined the terms Layer2 (L2) domain and Layer 3 (L3) domain. A L2 domain is based on VLAN ID separation and limitations and can hold multiple Cells. The core limitation is the number of VLAN Ids – 4090 max. A L3 domain is based on IP separation and can use multiple L2 domains to run the systems. <br /> <br /> As shown in the sandwich slide at the beginning the L2 domain is managed by a Infrastructure/platform manager – we use UCS-Director. Every L2 domain do have a own UCS-Directory instance (purple dot). The L3 domain is managed by a network automation tool – we use Cisco Network manager – and we use Cisco Intelligent Automation for Cloud (orange dot) for the Cloud Automation Layer and to coordinate the L3 network automation and the L2 / cell automation. <br /> <br /> We are fully aware that the most Service Providers do have a cloud automation and / or network automation tool in place and it is possible to use these tools for the L3 part. <br /> <br /> One unique point of our solution is UCS-Director as this tool abstract the infrastructure complexity and provides a services catalog for the different HANA sizes and applications. <br />
  • Here is a sample configuration that is designed for SAP to host HANA as a Service. <br /> <br /> There are 5 cells with 40 nodes each – 200 nodes – in one L2 domain. <br /> All cells are attached to a pair of Nexus 7000 switches. <br /> There is a seperate management / backup cell. This cell hosts all the management tools, like UCS-Director, CIAC, Virtual Center, … as well as storages to store the application backups. <br /> The backup destination is outside of the cell for three reasons. <br /> #1 customers may want to discontinue the HANA service for a while but will come back. The application backup can be stored for X weeks or month withouth any impact to the cell design and as the customer comes back the new HANA system can be placed in any cell. <br /> #2 The backup storage can be optimized for capacity and does not impact the core HANA performance. <br /> #3 The backup destination is not on the same storage as the productive data. <br /> <br /> For customer access Cisco ASA and ASR devices are used to provide VPN and MPLS functionality. <br />

SAP HANA TDI Tailored Datacenter Integration with EMC Presentation Transcript

  • 1. © 2014 VCE Company, LLC. All rights reserved. Robert Michael Moore (Mike) SME, WW SAP Center of Competence SAP HANA TDI TAILORED DATACENTER INTEGRATION WITH EMC
  • 2.  HANA is a database with in-memory performance capabilities.  For SAP and their customers, it is a revolutionary platform.  Most deployments since launch, have been as a dedicated Appliance.  Appliance – pre-engineered combination of network, storage, compute.  Tailored Datacenter Integration offers flexible deployment.  IT centers would like to integrate HANA onto infrastructure and capacity they may already own. TDI allows for this. QUICK BACKGROUND, WHAT IS SAP HANA, TDI?
  • 3. Multiple potential use cases: • Utilize existing datacenter SAN • Multiple HANA production systems (hosting, cloud) • Utilize existing datacenter 10GB network • Run SAP HANA together with other applications on shared infrastructure HANA DEPLOYED AS TDI
  • 4. HANA EVOLUTION – BUSINESS AND DEPLOYMENT CASES Cisco portfolio covers the full spectrum DW/Analytics Business Suite Suite on HANACustomer Specific Applications Hadoop Integration Deployment Models TDI • Shared/multi- instanceDedicated/ Appliance On Prem Standardization Virtualized Cloud Ref Arch • Enterprise • SP/GSI • SAP 20102012 Customer Use Cases 2014+ Hosted
  • 5. COMPARING APPLIANCE AND TDI Compute Network Storage Compute Network Storage Compute Applianc e TDI
  • 6. COMPARING – CUSTOMER PROFILE Applianc e TDI Note: TDI Network is in ramp. Must be accepted by SAP & Cisco Faster time to implementation Skilled SAP infrastructure teams Hands-off like SAP implementation philosophy Large storage and/or network investments and standardization Prefer with the appliance life cycle model Resources available to manage solution Storage/Network partner is datacenter trusted advisor Dedicated, purposeful HANA infrastructure
  • 7. COMPARING – OFFERING AND SUPPORT Applianc e TDI Pre-Engineered, Optimized, Pre- Certified solution with Delivery and Reactive Support Services Customer owns Engineering, Certification/Validation, Delivery and all Support coordination activities All specified components are required to maintain certification Customer replaces “appliance” storage and/or network with pre- validated Enterprise Storage or Network SAP or Cisco first point of contact for solution support Customer owns solution support. SAP & Cisco provide component- level support Customer adopts new life cycle management capabilities for appliance Customer leverages existing storage investment in people, process and equipment Installed by Cisco or validated partner Installed by SAP HANA Certified self or SAP HANA Certified installation partner Note: TDI Network is in ramp. Must be accepted by SAP & Cisco
  • 8. Network Storage HANA WHY THE CONCERN? COMPARING – I/O BEHAVIOR SAP/RDBMS AND SAP/HANA Compute Network Storage RDBMS SAP App SAP transactions are processed New sales orders, customer/supplier Changes in company data is collected SAP update process sends commits for these data changes to RDBMS Network I/O as App communicates with DB RDBMS commits to disk the new data Database files are written Logs are written for rollback Storage I/O as DB server writes to disk Network Database tables and log volumes are updated SAP App Network SAP transactions are processed, queries are run. In many use cases, SAP is near real-time synchronizing various business data into HANA Network I/O as App and synch processes are continuously refreshing data Data commits are issued to memory HANA also has data calculation engines. This means data changes will occur at this layer and issue commits without delay from the App HANA logs these commits in memory to disk Storage I/O is generated, lots of it. HANA continuously logs data changes occurring in memory. Also, every 300 seconds, it is writing a server memory image to disk
  • 9. CISCO HANA PORTFOLIO  Scale Economics: UCS chassis and fabric cost half as much in enterprise and cloud scale deployments *  Operational efficiency: Add capacity 77% faster with 67% fewer configuration steps ** • Cloud Readiness: Instant compatibility across Cisco’s ecosystem of Service Provider / Cloud Power partners • Management simplicity: Single orchestration interface across four pillars (compute, network, storage, multi-instance) • Consistency: Single family of building blocks across appliance, TDI and cloud deployment models Starter Scaleout 512G to 2TB Full Scale-Out for Private and Public Cloud 20 TB building block All-in-one Appliances 128-512 GB Application Orchestration (new) Databases Applications Sales Portal SAP BW, Business Suite, EC/BizX, LMS, OnDemand apps … Non-SAP databases Non-SAP applications SAP HANA platform, incorporating Sybase IQ & Hadoop SAP HANA Marketplace (new) Application Orchestratio n CIAC OS/VM Infrastructur e Managemen t UCS Director Cisco Application-Centric Infrastructure (new) Infrastructure Compute Storage Networking Nexus 5K to 9KUCS Cisco Cell Architecture Facilities Space, Power, Cooling, Operations, Location (national boundaries) Cloud Reference Architecture * Cisco internal comparison of HP and IBM systems scaling from a dozen to ninety-six blades ** Principled Technology study: http://www.youtube.com/watch?v=bSSQfNt7SFk
  • 10. BACKUP
  • 11. Self Service Portal Hybrid Cloud • Enterprise-Wide Orchestration • Extensible Service Catalog for IT Governance • Integration with IT Operations and Management Tools CISCO REFERENCE ARCHITECTURE FOR SAP CLOUD – HANA & APPS MODULAR, SCALABLE AND SECURE – ENABLING HAAS PHASE 2, CISCO CLOUD AND SPS End Users Cloud Automation, Portal Services c Compute - UCS Network - Nexus Storage OS/Hypervisor Core Platform Platform Management UCS Director for Converged Infrastructure Mgmt Cloud Service Providers Other Cloud Automation, Orchestration and Portal Services incl. OpenStack Others Cisco Unified Security Solution for Physical and Virtual Deployment Cisco Advanced Services for delivery and management Cisco Solution Other options Cisco Network Management SAP declarative delivery and governance (“Excalibur”) Portal HANA Market Place Other Service Provider Portals Cisco Intelligent Automation for Cloud (CIAC)
  • 12. SINGLE 40 NODE HANA CELL BUILDING BLOCK FOR SCALABILITY
  • 13. L3 Domain L2 Domain 1 MULTI CELL / L2 DOMAIN / L3 DOMAIN WITH AUTOMATION Cell 1 N5K+UCS+40 B440 + Storage Cell 2 N5K+UCS+40 B440 + Storage Cell 3 Cell N L2 Domain N Cell 1 Cell 2 Cell 3 Cell N FW / Router UCDDirector Manage&Automate Networks Automation CIAC to manage and automate
  • 14. SAMPLE: 200 NODE SOLUTION vCenter UCS Director CIAC Network Automation