Leveraging SUSE Linux to run SAP HANA on the Amazon Web Services Cloud
•Als PPTX, PDF herunterladen•
1 gefällt mir•1,793 views
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Andere mochten auch
Andere mochten auch (20)
Ähnlich wie Leveraging SUSE Linux to run SAP HANA on the Amazon Web Services Cloud
Ähnlich wie Leveraging SUSE Linux to run SAP HANA on the Amazon Web Services Cloud (20)
Mehr von Dirk Oppenkowski
Mehr von Dirk Oppenkowski (19)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Leveraging SUSE Linux to run SAP HANA on the Amazon Web Services Cloud
- 1. © 2011 Amazon.com, Inc. and its affiliates. All rights reserved. May not be copied, modified or distributed in whole or in part without the express consent of Amazon.com, Inc. Leveraging SUSE Linux to run SAP HANA on the Amazon Web Services Cloud Peter Mauel, SAP Global Alliance Leader, AWS Steven Jones, Sr Manager, Global Alliance Solutions Architecture, AWS
- 2. What is Amazon Web Services? AWS Global Infrastructure Application Services Networking Deployment & Administration DatabaseStorageCompute
- 3. Lower Overall Cost Benefit from AWS’s economies of scale and efficiencies. Only pay for what you use. Running SAP ERP Systems on AWS can save up to 71% on Infrastructure costs! AWS Drives Agility and Innovation Benefits for SAP Customers Shift Focus to Differentiation Free internal resources from the undifferentiating tasks of managing infrastructure and focus resources on innovation Replace CapEx with OpEx Start using AWS with no up-front cost or commitment and only pay for what you use Agility & Speed Provision new infrastructure and SAP systems in minutes vs. days, weeks or months Self-service Procure, provision and manage AWS resources completely via self-service End Hardware Refresh Cycles Stop having to plan and manage hardware refreshes every 3-5 years Elasticity and Flexible Capacity Scale resources automatically up or down as needed. On- demand access to virtually unlimited compute, storage and network capacity to meet your SAP Sizing needs. Secure & Durable Secure and durable technology platform with industry- recognized certifications and audits
- 4. Trusted by Enterprises Around the World
- 5. Used by Government Agencies & Educational Institutions Worldwide
- 6. Architected for Enterprise Security Requirements “The Amazon Virtual Private Cloud [Amazon VPC] was a unique option that offered an additional level of security and an ability to integrate with other aspects of our infrastructure.” Dr. Michael Miller, Head of HPC for R&D
- 7. Gartner Magic Quadrants 2013 Gartner Magic Quadrant - IaaS Gartner “Magic Quadrant for Cloud Infrastructure as a Service,” Lydia Leong, Douglas Toombs, Bob Gill, Gregor Petri, Tiny Haynes, August 19, 2013. This Magic Quadrant graphic was published by Gartner, Inc. as part of a larger research note and should be evaluated in the context of the entire report.. Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings. Gartner research publications consist of the opinions of Gartner's research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose.
- 8. SAP & AWS Relationship - Key Milestones 2008 20122010 2014 SAP as a Customer A1/B1 BOBJ HANA Dev HANA One Afaria HANA (BYOL) Business Suite CAL CustomerAdoption Time RDS Solutions
- 10. Infrastructure Subscription SAP HANA One Developer Edition Overview Quickly deploy and manage your pre- licensed SAP HANA instances Fully featured SAP HANA virtual appliance on AWS Fully featured SAP HANA virtual appliance on AWS for individual developers Use Cases Production and non-production All SAP HANA use cases supported including SAP Business Suite and SAP NetWeaver Business Warehouse on HANA Production and non-production Analytics acceleration Data merging Temporary event-based analytics Self-service BI Prototypes and proofs-of-concept Non-production only Develop, test and demo applications on top of the HANA platform Learning environment Key Benefits Real-time provisioning on the AWS Cloud for your existing HANA licenses. Replace Capital expense for Hardware with Operational expense. No Capital outlay required. Support for production use cases. Develop and deploy HANA faster. Instant, self-serve access – up and running in 10 minutes Start and stop when needed – reduce license and infrastructure cost Community support Free developer license Easily accessible and rapidly deployable Pay-per-use infrastructure HANA License Bring-your-own-License On-demand - $0.99 per hour Free Developer License¹ Memory 244 GB | 732 GB | 976 GB | 1.22 TB 60.5 GB Up to 68.5 GB Available from SAP HANA Marketplace http://bit.ly/aws-hana-byol AWS Marketplace: http://bit.ly/aws-hana- one SAP SCN: http://bit.ly/aws-hana-dev SAP HANA Offerings on AWS leveraging SUSE ¹ License available directly from SAP: http://scn.sap.com/docs/DOC-28294
- 11. 10 Regions* 26 Availability Zones* 51 Edge Locations * China (Beijing) Region- EC2 Availability Zones: 1 Coming Soon Global Infrastructure
- 12. Amazon EC2 Cluster Compute Instances for SAP HANA 2 x Intel Xeon E5-2670 processors (Sandy Bridge) 32 vCPUs with hyperthreading 64-bit 60.5 GB RAM 10 Gigabit Network 2 x Intel Xeon E5-2670 processors (Sandy Bridge) 32 vCPUs with hyperthreading 64-bit 244 GB RAM 10 Gigabit Network NUMA and Turbo Support cc2.8xlarge cr1.8xlarge All c* instances support high-performance (10 gigabit) networking to Elastic Block Storage volumes (EBS) 2 x Intel Xeon E5-2670 v2 processors (Ivy Bridge) 32 vCPUs with hyperthreading 64-bit 244 GB RAM 10 Gigabit Network NUMA and Turbo Support Enhanced Networking r3.8xlarge HANA One SAP HANA Infrastructure Subscription
- 13. Customer Data Centers VPN or Direct Connect Virtual Private Cloud SAP HANA Disaster Recovery (DR) on AWS DR ECC BWBW ECC PRD SAP production (PRD) landscape runs in customer’s own datacentre SAP development & quality assurance landscape runs on AWS SAP HANA Appliance(s) HANA DB SAP HANA System Replication (Async)
- 14. Customer Data Centers VPN or Direct Connect Secure connectivity between datacentre & AWS Virtual Private Cloud Hybrid HANA Deployment – Customer Data Centre & AWS DEV QAS ECC BW ECC BW BW ECC SRM PRD SAP production landscape runs in customer’s own datacentre SAP development & quality assurance landscape runs on AWS SAP HANA Appliance(s) HANA DB HANA DB
- 15. Virtual Private Cloud Full SAP HANA Deployment on AWS DEV QAS Customer runs DEV, QAS, & PRD on AWS PRD VPN or Direct Connect Secure connectivity between LAN & AWS network Customer LAN ECC BW ECC BW HANA DB HANA DB ECC BW HANA DB
- 16. Virtual Private Cloud SAP HANA for Big Data Analytics VPN or Direct Connect Secure connectivity between LAN & AWS network Customer LAN ECC BW BW HANA DB SAP BI Amazon EMR +
- 17. SAP HANA Scalability Test for SAP BW Using In-Memory Data Fabric 111 SAP HANA Instances (1,776 CPU Cores) 8M Rows loaded per second (60 Billion Total) 220ms single node query (600 Million Rows) 330ms for federated query (60 Billion rows) Throughput of 3 million queries per hour Additional Details: http://bit.ly/scale-hana-aws
- 18. Virtual Private Cloud 10.0.0.0 / 16 10.0.1.x / 24 (Private Subnet) SAP HANA (Master) Availability Zone Amazon S3 S3 Backup Bucket Root Volume SAP Volume LVM Group SAP HANA (Workers) Root Volume SAP Volume LVM Group HANA Data HANA Log & Backup Area HANA Data HANA Log Push/Pull Backup to/from S3 Elastic IP Address Private IP Address(es) Shares From Master Mount Global Shares: /hana/shared /backup Internet NAT Outbound Internet Traffic Studio (50013/14) HLM (1128/9) JDBC (30015/17) XS App (8000/4300) RDP SSH SSH (22) Quick Start SAP HANA Deployment in Minutes 10.0.2.x / 24 (Public) HANA Studio Inbound SSH Internet Gateway Corporate Data Center CorporateNetwork Virtual Private Gateway Customer Gateway VPN Tunnel or AWS Direct Connect Internal (30000-10) NFS (Various) Easily connect to your own network post deployment
- 19. Where to Find SAP HANA on AWS Resources Latest updates How to Get Started Deployment Information Support Information SAP HANA on AWS Implementation and Operations Guide Contact us: saphana@amazon.com http://aws.amazon.com/sap/saphana/ SAP HANA in the AWS Cloud Quick Start Deployment Guide http://aws.amazon.com/quickstart/
Hinweis der Redaktion
- Amazon Web Services is part of Amazon.com. Most of us at some point in time have used the online amazon retail store to buy books, and a myriad of other products for friends and family but there are three parts to the amazon business: There’s this retail consumer business, our seller business that enables retailers to sell through the same online store as amazon, and finally amazon web services, our IT infrastructure business. This is a simple view of the set of services that we offer. At the core is the compute, storage and data services that are the heart of our offering. We then surround these offerings with a range of supporting components like management tools, networking services and application augmentation services. All this is hosted within our global data center footprint that allows you to consume services without having to build out facilities or equipment.
- Since we invest and operate at such high scale, we pay less per unit than most anybody else in the IT industry. We run our business on a high volume, low margin basis, which is also quite unique. So this combination of high scale and low margins allows us to pass significant savings along to all of our customers. A proof point of this is the 32 price reductions that we’ve announced over time. With traditional infrastructure, you have to guess how much capacity you will need over the next 3-7 years, and pay for most or all of it on day one. This ties up money that you could be spending on other things and it’s very difficult to forecast accurately over such a long period of time. With AWS, you pay for what you need, when you need it. With the elasticity of AWS, you no longer need to forecast demand and buy up front. You get the ability to scale up to meet the needs of spiky workloads, but then give that capacity back when the spike is over. We’ve even seen SAP customers be able to take advantage of the elasticity of our platform and the ability to add/remove additional capacity depending on a myriad of reasons (ie additional project environments, seasonal demand, month end processing, etc). We see our customers do amazing things when they reduce the cost of experimentation- it moves IT from being a roadblock, where each idea costs lots of money and takes lots of time, to being an enabler where you can launch a speculative project quickly and cheaply. It allows firms to take more chances on ideas, and gives them a shot at winning big, as opposed to being scared to even try. And let’s face it, racking and stacking gear in a data center just doesn’t help you win over your competitors. It takes lots of time and lots of money and becomes a big distraction from activities that can truly differentiate you. Plus, without big economy of scale, these activities simply cost more.
- AWS is solving problems for big organizations across many Verticals and geographies. We’re extremely proud of our customer list and happy to know that we’re providing good outcomes and better results for some of the best firms in the world
- And our customer list extends into the public sector as well with many agencies adopting a cloud first on AWS approach.
- You might have questions about security in the cloud, but our biggest and most conservative customers have found that we’re able to meet their security requirements, and often we can provide a better security profile than what they can deliver internally. Our focus and investment in security, and the fact that we incorporate requirements from our most security conscious customers which then benefit all of the customers on our platform allows us to offer an effective approach to meeting enterprise security requirements. We encourage you to dig deeper with our security white paper, and would be happy to help you get the information you need to feel confident in our security capabilities and options.
- As this charts show, Gartner has categorized AWS in the Leader category for Infrastructure-as-a-Services (IAAS) for three years now. According to them, “AWS is the overwhelming market share leader, with more than five times the compute capacity in use than the aggregate total of the other fourteen providers in this Magic Quadrant. AWS is a thought leader; is extraordinarily innovative, exceptionally agile and very responsive to the market.” Excerpts of these reports are available on our website.
- Our data center footprint is global, spanning 5 continents with highly redundant clusters of data centers in each region. We are organized into what we call regions and availability zones. At this time you can see that there are nine regions strategically placed around the globe. You can think of regions as essentially separate clouds. There is total isolation between regions, and even the control plane is not shared. When you as a customer sign up for AWS services you immediately have access to resources all over the globe. No longer should you be constrained by IT infrastructure. Our footprint is expanding continuously as we increase capacity, redundancy and add locations to meet the needs of our customers around the world. In general we use the term “availability zone” to refer to one or more data centers. And regions are comprised of 2 or more Availability zones. If we refer to something as a distinct availability zone, there is fault isolation involved. Now all Azs are in the same general metro area for latency reasons; however they are far enough apart that there is a “share as little as possible” principle. That is, insofar as practical each AZ has separate power utilities – or at least separate distribution trunks, separate network connections, different flood plains, and so forth. The amount of separation varies according to geography, because for example Singapore has relatively less real estate over which to distribute things.
- For SAP HANA we leverage our largest and most powerful cluster compute instance types. You can see that HANA One leverages… For the Infrastructure subscription we use our largest instance types which have 16 Cores (32 virtual CPU’s with hyperthreading) and 244 GB RAM. The cr1.8xlargeinstance type is based on the Intel Sandy Bridge Processor while our recently released r3.8xlarge instance type uses the latest Intel Ivy Bridge Processor. Both cr1 and r3 provide turbo and NUMA support which is important for SAP HANA performance. In addition r3.8xlarge also provides: -Support for Enhanced Networking that provides lower latency, low jitter, and very high packet per second performance -Higher sustained memory bandwidth - up to 63,000 MB/s -And R3 instances are available in all AWS Regions except GovCloud (US), China (Beijing), and South America (São Paulo). Lastly, all cluster compute instances leverage a high speed 10 Gigabit Network. Comment on ease of upgrading from one instance type to another. No costly expenditure or data migration required.
- First you might be surprised that when it comes to DR many customers don’t have a solution for their SAP HANA environment which they’ve invested a lot of resources. Instead of having to maintain secondary appliances sometimes even in the same datacenter, customers are able to protect this investment by easily spinning up virtual HANA Appliances on AWS and leveraging native built in technology of SAP HANA called system replication to replicate their critical data. My hats off to SAP on this one. It’s really slick.
- Others choose to run Production hardware appliances on-premises and operate non-production HANA environments in a VPC on the AWS platform. This also works quite well.
- But the vast majority of customers are choosing to go all in with their SAP HANA environments on us. And there’s a good reason for this beyond what both Peter and I have mentioned already with regards to agility, and flexibility. For many customers it’s the speed with which they deploy these environments and begin to differentiate themselves from their competitors.
- But it’s also because our platform encourages innovation. We’ve seen customers do amazing like being able to combine the power of SAP HANA with other services that we provide like Elastic Map Reduce or Hadoop clusters. Imagine churning through massive amounts of data and performing in-memory analytics on just a subset. It’s happening. And do it all at scale… this is just one example
- In a separate test, one SAP HANA federated instance has been tested with 25 SAP HANA data instances. This means, in principle, with two levels of data federation, an in-memory data fabric architecture can be easily scaled to 625 AWS instances (625 * 12 cores = 10,000 cores) which can handle queries on 375 billion (625 * 600 million) rows. Test results conclude that: Speed at which data is loaded is linearly proportional to the number of SAP HANA instances. On a single HANA instance, 80 thousand rows per second are loaded. On 100 HANA instances, 8 Million (100 * 80 thousand) rows per second are loaded Query performance remains almost same when query is federated on multiple SAP HANA instances. Data analyzed is linearly proportional to the number of SAP HANA instances. Local query executed on a single HANA instance took 220 milliseconds and processed analyzed 600 million rows. Two levels of federated query executed on 100 HANA instances took 330 milliseconds and analyzed 60 billion (100 * 600 million) rows Query throughput (number of queries processed) is linearly proportional to the number of SAP HANA instance. 30 thousand queries are executed per hour on single HANA instance. 3 million (100 * 30 thousand) queries are executed per hour on 100 HANA instances. This concludes that the in-memory data fabric architecture can be scaled to address large enterprises data warehouse requirements.
- You won’t have to wait long. About 10 minutes for a single node deployment and about 20 for multi-node. So let me describe a bit of what’s been created as part of this process. -VPC -Deployed in a secure manner -Private, public (DMZ) -NAT (inbound ssh access, outbound internet access) -Studio instance -Security groups -Remember you can also easily connect this VPC your own network All that in about 20 minutes. Much more detail in the SAP HANA on AWS implementation and operations guide. -Customizable For any advanced configurations, custom CloudFormation templates substituted in order to customize the deployment.