TUT19741 Use SUSE Cloud 5 with Manila to utilize NetApp s enterprise class storage for SAP workloads Bernd Herth Thore Bahr TME System Engineer Thore.Bahr@suse.com Bernd.herth@netapp.com
Agenda 2 OpenStack : NetApp, SUSE and SAP Enterprise Application Requirements Proof of Concept SAP NetApp - SUSE Lessons Learned Final Words
OpenStack : NetApp, SUSE, SAP
Walmart What is OpenStack nearly 4 Open-Source cloud computing platform Founded 2010 by NASA and Rackspace Hosting > 400 companies joined project (AT&T, Cisco, Dell, EMC, HP, IBM, Intel, NetApp, Oracle, Red Hat, VMWare, ) One of the fastest growing open-source projects Linux of cloud platforms Public, private, and hybrid cloud solution Modular Infrastructure as a Service Subprojects for Platform as a Service emerging Amazon EC2 and S3 API compatibility 100% of PayPal traffic for Web/API & Mid-Tier 100.000 cores powering Black Friday and peaks
NetApp s OpenStack Journey OpenStack Foundation Charter member (Gold) OpenStack Summit sponsors 1st Major Storage Provider Upstream Contributions Production Deployments & Deployer Essex Summit Sponsor Folsom Summit Sponsor Grizzly Summit Sponsor Havana Summit Sponsor Integration Announced 7-mode driver previewed 7-mode driver in Essex Clustered ONTAP driver in Folsom Direct Drivers in Grizzly Swift on E-series 2011.3 2011.10 2012.4 2012.10 2013.4 2013.10 NetApp Joins 5 Icehouse Summit Sponsor Juno Summit Sponsor Mitaka Summit Sponsor E/EF-series drivers in Icehouse Kilo Release Summit Sponsor Liberty Summit Sponsor Manila Incubation Manila Maturation Manila 1.0 Replication 2014.4 2014.10 2015.4 2015.10
All companies are cloud focused SAP Private Cloud 6 HEC HANA Enterprise Cloud Has joined OpenStack as gold member NetApp Strategy and Products Data Fabric Pioneer in open source NetApp private Storage Storage Appliance) Leading Linux Distribution for SAP HANA cloud platform powered by OpenStack Cloud business is growing SUSE Enterprise Linux OpenStack Gold Member OpenStack Platinum Member Founding & Contributing member Cloud 5 Automated OpenStack solution
Demo OpenStack Overview TUT19741-OS-overview 7
Enterprise Application Requirements
A world of many clouds OpenStack AWS SoftLayer Azure VMware 9 9 SAP Cloud
A world of many clouds OpenStack AWS SoftLayer Azure VMware 10 SAP Cloud
The Data Fabric & OpenStack Interoperability OpenStack AWS SoftLayer Azure VMware 11 SAP Cloud
The Data Fabric & OpenStack Interoperability OpenStack NetApp s vision SoftLayer AWS Give customer the freedom of choice for their infrastructure by actively working and defining open standards such as OpenStack. & VMware 12 Let them choose NetApp because of the best Azure integration, features, reliability andcloud support. SAP
Proof of Concept SAP NetApp - SUSE
How to orchestrate an OpenStack SAP/LVM Architecture Nova Neutron Manila 14 Glance Cinder
DEMO SAP Landscape Virtualization Manager (LVM) To be defined 15
Design Criteria Secure Multi Tenant Cloud environment Storage Design Easy migration in a multi cloud / hybrid Cloud environment Data Fabric High Throughput / Low Latency -> Enterprise class storage Use all the features customers want in an SAP environment Utilize SAP s Landscape Virtualization Manager to Automate SAP administration SAP specific use cases such as System Clone & Copy Automation from Infrastructure to Application 16 Network / Storage / Compute Cloud5 & SAP Landscape Virtualization Manager
OpenStack Logical Architecture Core components for the PoC 17 17
SAP requirements / Storage & I/O Storage Volume, I/O / bandwidth requirements in a cloud Storage/Volume layout to utilize snapshots 18 High I/O requirements, low latency, easy deployment and manageability SVM Clustered Data ONTAP Segregation Network & Storage Project decision 2 Volumes / SAP system NFS L Data / Log Volumes Secure Multi Tenant D Network Project / Tenant D L
SAP requirements / external access Adaptive computing (LVM) 19 L3 router & ACL s Virtual ip s for all SAP services Ip s are bound during SAP startup by LVM External communication through virtual ip s only Different to floating ip concept Tenant-2 Tenant-1 Access-LAN (routed) Network Typical: Separate Storage / Access network DNS for virtual ip s Project decision External router / firewall into tenant Linux bridge / VLAN segregation Storage-LAN (private)
Physical Setup using SUSE Cloud 5 Cloud5 Management station OS Controller 20 OSCtrl 2 Blades OS Compute Cloud5 enables OS032-A (vl132) OS032-B (VL332) OpenStack Environment C5mg m OS031-A (VL131) Cisco UCS / Nexus / NetApp Eth1 : VL 130-159 330-359 (trunk) OS031-B (VL331) T001-Access Eth0 : VLAN 100 (native) OS030-A (VL130) HW FlexPod based on SAP Applications build on FlexPod OS030-B (VL330) T001-backend PXE Boot of any new HW Select OS components to deploy automatically Eth2 : VLAN 300 (native) Storage: cinder,glance
SUSE Cloud5 (Juno) + Manila (Kilo) Management Billling Cloud Required Services RabbitMQ Postgresql SUSE VM Mgmt SUSE Image Tool Manager Studio Dashboard (Horizon) Compute (Nova) Portal Cloud APIs (OpenStack and EC2) AUTH (Keystone) Images (Glance) App Monitor Orchestration (Heat) Object (Swift) Sec & Perf Telemetry (Ceilometer) Network (Neutron) RadosGW Block (Cinder) Hypervisor Shared (Manial) RBD Xen, KVM Vmware, HyperV Adapters Adapters NetApp SUSE Linux Enterprise Server 11 SP3 Physical Infrastructure: x86-64, Switches, Storage OpenStack Icehouse 21 Management SUSE Cloud Tools Adds OS andproduct Hypervisor SUSE Physical Infrastructure Partner Solutions Ceph Manila added On Kilo Release (tec preview)
SUSE Cloud Structure Compute Node Control Node Administration Server SLES Chef server Crowbar Software mirror TFTP PXE Server SLES Database Message queue Self-Service Portal Image Repository Centralized Tracking Scheduler Identity and Authentication Storage Crowbar + PXE Boot Vcenter (api) Hyper-V Xen (sles) KVM (sles Network Node Routing Floating IP Storage Node Customer Center 22 SLES Ceph Lvm / raw Nfs / cifs
Highlights of SUSE Cloud 5 23 Based on OpenStack Juno (2014.2) theme of the OpenStack Dashboards can be replaced Trove, Sahara, Manila (tec preview) Features HA Improvements SUSE Linux Enterprise Server 12 for compute nodes Support for SUSE Enterprise Storage 1.0 Windows Server 2012 R2 for Hyper-V compute nodes SUSE Cloud 4 to SUSE Cloud 5 upgrade Multi-Hypervisor Support (kvm,xen,hyper-v,vmware vcenter)
Demo Cloud5 Management TUT19741-SUSE-Cloud5 24
OpenStack Components : Glance / (Cinder) OS provisioning Standardized SUSE SLES 11 SP3 images i.e. saphostagent, database client User management Different versions Boot "4 SAP ready instances Prepared for SAP System Clustered Data ONTAP HANA, SAP Netweaver, Glance to provide Image via NFS Rapid image creation RHEL SUSE 25 RHEL SUSE Storage efficiency through de-duplication SAP HANA Ubuntu Image copy handled on storage space efficient andsuse fast. OS SUSE Cinder to provide persistent copies Cinder on NetApp Glance on NetApp SAP SUSE SUSE HANA Ubuntu OS SUSE SUSE SUSE SUSE SUSE SUSE SUSE SUSE
Manila: Clustered Data ONTAP Driver Create 2 volumes TYPE HANA with 2T and.5 TB Using managed shared servers Use Manila to create SAP volumes Create SVM for Tenant Create volumes and export policies Future requirements Network requirements Clustered Data ONTAP LIF placement (interface, bond, node) shared / exclusive LIF Volume placement 26 Manila Use Type standard extensions to specify Aggregate / node HANA SAP Share Nova
Manila: Clustered Data ONTAP Driver without Neutron Dependence Supporting standalone deployments and simpler network topologies Driver points at an existing cluster and SVM mount t nfs nova-compute Reuses existing NFS Data LIFs within the SVM scope for exporting access to new junction paths SVM and Data LIFs need to be created ahead of time by storage administrator Access permissions are set at the controller for guests Clients need L3 connectivity to Data LIF (not managed by Manila) manila create Manila NFS Control Path Data Path 27 nova-compute
Use Manila types and extra-specs to tune for SAP Data-LIF and Volume placement SVM SAP2 Single SVM to map SVM SAP1 Aggregates with data LIF mapped to NIC on same controller/node Manila multiple backend [DEFAULT] enabled_share_backends=os032-sap1,os032-sap2 SAS SATA node1 28 node2 [backend-netapp-0] share_driver=manila.share.drivers.netapp.common.netappdriver share_backend_name=os032-sap1 driver_handles_share_servers=false netapp_storage_family=ontap_cluster netapp_server_hostname=172.23.111.100 netapp_server_port=80 netapp_login=openstack netapp_password=xxxxxxxx netapp_vserver=os032-sap1 netapp_transport_type=http netapp_aggregate_name_search_pattern=(aggr01.*)
Example 1/2 Use Extra specs to define types root@d00-50-56-9e-59-d8:/etc/manila # manila extra-specs-list +--------------------------------------+---------+--------------------------------------+ ID Name all_extra_specs +--------------------------------------+---------+--------------------------------------+ 020b5e4d-a4fc-4d73-ac74-443b06323f48 general netapp_disk_type : SATA + driver_handles_share_servers : False 9b9e7d2c-a361-496b-85ab-57517f0f5b4a SAP2 netapp:snapshot_policy : openstack share_backend_name : os032-sap2 netapp_disk_type : SAS driver_handles_share_servers : False ebf175e2-7e18-47cd-b3c4-451b04f90991 SAP1 netapp:snapshot_policy : openstack share_backend_name : os032-sap1 netapp_disk_type : SAS driver_handles_share_servers : False +--------------------------------------+---------+--------------------------------------+ Create SAP volumes using types manila create --share-type SAP1 --name PA0-data NFS 100 manila create --share-type SAP2 --name PA0-log NFS 60 29
Example 2/2 Use Manila list to show the shares root@d00-50-56-9e-59-d8:~ # manila list +--------------------------------------+----------+------+-------------+-----------+-----------+-----------+-----------------------------------------------------------+--------------------------------------+ ID Name Size Share Proto Status Is Public Share Type Export location Host +--------------------------------------+----------+------+-------------+-----------+-----------+-----------+-----------------------------------------------------------+--------------------------------------+ 88358fdb-d4e0-4ce6-9f57-a8dfc7ac2267 PA0-data 100 NFS available False SAP1 192.168.132.3:/share_88358fdb_d4e0_4ce6_9f57_a8dfc7ac2267 d00-50-56-9e-59-d8@backend-netapp-0#aggr01 f74fac9a-c698-4737-8f6c-c93b856359bd PA0-log 60 NFS available False SAP2 192.168.132.4:/share_f74fac9a_c698_4737_8f6c_c93b856359bd d00-50-56-9e-59-d8@backend-netapp-1#aggr02 Grant access for the instance(s) to mount SAP data/log manila access-allow 88358fdb-d4e0-4ce6-9f57-a8dfc7ac2267 ip 192.168.132.0/24 manila access-allow f74fac9a-c698-4737-8f6c-c93b856359bd ip 192.168.132.0/24 30
Demo: Manila CLI and NetApp Storage TUT19741-Manila-* 31
Prototype : OpenStack Storage Adapter for LVM SAP LVM Nova SAP OpenStack Adapter 1.) Storage Adapter for Cinder (Block storage) 2.) Storage Adapter for Manila (File storage) 3.) Virtualization Adapter for Nova (Virtualization Layer, Kilo) 32 Storage Adapter - REST API calls manila create snapshot manila access OS-Manila
Demo 33 NetApp Proprietary Limited Use Only
Lessons Learned
The simple things.. Allow SAP s virtual ip s, to pass the firewall To support easy cloning add user management and DNS Additional instance with NIS and dnsmasq as internal services Jumbo frames with 1 physical net -> difficult?? (Should we name it) Manila make SAP systems cloud portable In future even easier (manage / un-manage) SAP LVM is ready for OpenStack and helps to 35 neutron port-update 138f1e36-a4f7-4738-8ffd-3942e0508314 --allowed_address_pairs list=true type=dict ip_address=192.168.32.128/27 integrate infrastructure and SAP management
Final Words
Final words Publications and help see: Technical Report s : SUSE OpenStack Cloud 5 on NetApp Clustered Data ONTAP Business Critical Applications Built on OpenStack Using Manila on NetApp Storage Systems Central NetApp OpenStack github: 38 OpenStack @ NetApp
Call to action line one and call to action line two www.calltoaction.com Thank you. 39
Unpublished Work of SUSE. All Rights Reserved. This work is an unpublished work and contains confidential, proprietary, and trade secret information of SUSE. Access to this work is restricted to SUSE employees who have a need to know to perform tasks within the scope of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of SUSE. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability. General Disclaimer This document is not to be construed as a promise by any participating company to develop, deliver, or market a product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. SUSE makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. The development, release, and timing of features or functionality described for SUSE products remains at the sole discretion of SUSE. Further, SUSE reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All SUSE marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.