TUT19741
Use SUSE Cloud 5 with Manila to utilize
NetApp’s enterprise class storage for
SAP workloads
Bernd Herth
TME
Bernd.herth@netapp.com
Thore Bahr
System Engineer
Thore.Bahr@suse.com
Agenda
• OpenStack : NetApp, SUSE and SAP
• Enterprise Application Requirements
• Proof of Concept – SAP – NetApp - SUSE
• Lessons Learned
• Final Words
OpenStack : NetApp, SUSE, SAP
What is OpenStack
• 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
nearly
100% of PayPal
traffic for
Web/API &
Mid-Tier
Walmart
100.000
cores
powering Black
Friday and
peaks
5
2015.4
Liberty Summit Sponsor Manila Maturation
2014.10
Kilo Release Summit Sponsor Manila Incubation
2013.10
Icehouse Summit Sponsor Swift on E-series
2014.4
Juno Summit Sponsor E/EF-series
drivers in Icehouse
2013.4
Havana Summit Sponsor Direct Drivers in
Grizzly
2012.10
Grizzly Summit Sponsor Clustered ONTAP
driver in Folsom
2012.4
Folsom Summit Sponsor 7-mode driver in
Essex
2011.3
NetApp Joins Integration Announced
NetApp’s OpenStack Journey
• OpenStack Foundation
– Charter member (Gold)
–
OpenStack Summit sponsors
• 1st Major Storage Provider
– Upstream Contributions
• Production Deployments &
Deployer
2011.10
Essex Summit Sponsor 7-mode driver
previewed
2015.10
Mitaka Summit Sponsor Manila 1.0 Replication
All companies are “cloud” focused
SAP
• Private Cloud
– HEC – HANA Enterprise
Cloud
• Has joined OpenStack
as gold member
– HANA cloud platform
“powered by OpenStack”
• Cloud business is
growing
• Strategy and Products
– Data Fabric
– NetApp private Storage
Storage Appliance)
• OpenStack Gold Member
NetApp
• Enterprise Linux
– Pioneer in open source
– Leading Linux Distribution
for SAP
• OpenStack Platinum
Member
–
Founding & Contributing
member
–
Cloud 5
Automated OpenStack
SUSE
7
Demo OpenStack Overview
TUT19741-OS-overview
Enterprise Application Requirements
9
A world of many clouds
9
SoftLayer
VMware
OpenStack
AWS
SAP Cloud
Azure
A world of many clouds
SoftLayer
VMware
OpenStack
AWS
SAP Cloud
Azure
11
The Data Fabric & OpenStack Interoperability
SoftLayer
VMware
OpenStack
AWS
SAP Cloud
Azure
The Data Fabric & OpenStack Interoperability
SoftLayer
VMware
OpenStack
AWS
SAP Cloud
Azure
NetApp’s vision
Give customer the freedom of choice for their
infrastructure by actively working and defining
open standards such as OpenStack.
&
Let them choose NetApp because of the best
integration, features, reliability and support.
Proof of Concept – SAP – NetApp - SUSE
How to orchestrate an OpenStack SAP/LVM
Architecture
Manila
Glance Cinder
Neutron Nova
15
DEMO SAP Landscape Virtualization Manager (LVM)
To be defined
Design Criteria
• Secure Multi Tenant Cloud environment
– Network / Storage / Compute
• 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”
17
OpenStack Logical Architecture
17
Core components for the PoC
Project / Tenant
SAP requirements / Storage & I/O
• Storage
–
Volume, I/O / bandwidth requirements in a cloud
–
Storage/Volume layout to utilize snapshots
• Network
–
High I/O requirements, low latency, easy
deployment and manageability
• Secure Multi Tenant
– Segregation Network & Storage
• Project decision
–
2 Volumes / SAP system
Clustered Data ONTAP
SVM
D L
Data / Log Volumes
D L
19
SAP requirements / external access
• Adaptive computing (LVM)
–
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
• Network
–
Typical: Separate Storage / Access network
–
DNS for “virtual” ip’s
–
Project decision
–
External router / firewall into tenant
–
Linux bridge / VLAN segregation
L3 router & ACL’s
Tenant-1 Tenant-2
Storage-LAN (private)
Access-LAN (routed)
Access-LAN (routed)
Physical Setup using SUSE Cloud 5
• HW FlexPod based on
“SAP Applications build
on FlexPod”
–
Cisco UCS / Nexus / NetApp
• OpenStack Environment
–
Cloud5 Management station
–
OS Controller
–
2 Blades OS Compute
• Cloud5 enables
–
PXE Boot of any new HW
OSCtrl C5mg
m
T001-Access
O S 03 0- A (V L1 30 ) O S 03 1- A (V L1 31 ) O S 03 2- A (v l1 32 )
T001-backend O
S 0 30 -B (V L3 30 ) O S 03 1- B (V L3 31 ) O S 03 2- B (V L3 32 )
Eth0 : VLAN 100
(native)
Eth1 : VL 130-159
330-359
(trunk)
Eth2 : VLAN 300
(native)
Storage:
cinder,glance
21
SUSE Cloud5 (Juno) + Manila (Kilo)
Management
VM Mgmt Image Tool
Billling Portal App Monitor Sec & Perf
Cloud
Management Tools OS and Hypervisor OpenStack Icehouse
Orchestration
(Heat)Dashboard
(Horizon) Cloud APIs
(OpenStack andEC2)
AUTH
(Keystone)
Images
(Glance)Compute
(Nova)
Object
(Swift)
Network
(Neutron)Block
(Cinder)Telemetry
(Ceilometer)Shared
(Manial)Physical Infrastructure SUSE
Manager
SUSE Studio
Partner Solutions
Adapters Adapters Vmware, HyperV
Physical Infrastructure: x86-64, Switches, Storage
NetApp
SUSE Product SUSE Cloud Adds
Required Services
RabbitMQ
Postgresql
Hypervisor Xen, KVM
SUSE Linux Enterprise Server 11 SP3
Ceph RBD
RadosGW
Manila added
On Kilo Release
(tec preview)
SUSE
®Cloud Structure
Administration
Server
Control Node
Customer
•
SLES
•
Database
•
Message queue
•
Self-Service Portal
•
Image Repository
•
Centralized Tracking
•
Scheduler
•
Identity and Authentication
•
Storage
Crowbar + PXE Boot
•
SLES
•
Chef server
•
Crowbar
•
Software mirror
•
TFTP
•
PXE Server
•
SLES
•
Ceph
•
Lvm / raw
•
Nfs / cifs
•
Vcenter (api)
•
Hyper-V
•
Xen (sles)
•
KVM (sles
•
Routing
•
Floating IP
Network Node
Compute Node
Storage Node
23
Highlights of SUSE Cloud 5
• 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
25
OpenStack Components : Glance / (Cinder) OS
provisioning
• Standardized SUSE SLES 11 SP3 images
–
Prepared for SAP System
–
i.e. saphostagent, database client
–
User management
–
Different versions
–
HANA , SAP Netweaver, …
• Glance to provide Image via NFS
–
Rapid image creation
–
Storage efficiency through de-duplication
–
Image “copy’ handled on storage – “space efficient” and fast.
• Cinder to provide persistent copies
Clustered Data ONTAP
Glance on NetApp
UbuntuHANA SUSE Ubuntu
OS HANA
OS SAP
SUSE
RHEL SUSERHEL SUSE
SUSE SAP
SUSE
Boot "4” SAP
ready instances
Cinder on NetApp
SUSE SUSE SUSE
SUSE SUSE SUSE SUSE
SUSE
Manila: Clustered Data ONTAP Driver
• Use Manila to create SAP volumes
–
Create SVM for Tenant
–
Create volumes and export policies
• Future requirements
–
Use “Type” standard extensions to specify
–
Network requirements
–
LIF placement (interface, bond, node)
–
“shared” / “exclusive” LIF
–
Volume placement
Aggregate / node
Using managed shared servers
Manila
Clustered Data ONTAP
HANA SAP Share
Nova
Create 2
volumes TYPE
HANA with 2T
and .5 TB
27
Manila: Clustered Data ONTAP Driver without Neutron
Dependence
Driver points at an existing cluster and SVM
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)
Supporting standalone deployments and simpler network topologies
nova-compute
manila create
Control Path Data Path
Manila
mount –t nfs
nova-compute
NFS
Use Manila types and extra-specs to tune for SAP
• Single SVM to map
– Aggregates with data LIF mapped to NIC on
same controller/node
• Manila multiple backend
Data-LIF and Volume placement
SVM SAP1
SAS
SATA
SVM SAP2
[DEFAULT]
enabled_share_backends=os032-SAP1,os032-SAP2
[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
29
• Use Extra specs to define types
• Create SAP volumes using types
Example 1/2
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 |
+---+---+---+
manila create --share-type SAP1 --name PA0-data NFS 100
manila create --share-type SAP2 --name PA0-log NFS 60
• Use Manila list to show the shares
• Grant access for the instance(s) to mount SAP data/log
Example 2/2
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 |
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
31
Demo: Manila CLI and NetApp Storage
TUT19741-Manila-*
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)
Prototype : OpenStack Storage Adapter for LVM
SAP LVM Nova
OS-Manila
Storage Adapter
- REST API
calls
- manila
create
snapshot
- manila
access
33
Demo
NetApp Proprietary – Limited Use Only
Lessons Learned
35
The simple things…..
• Allow SAP’s “virtual ip’s”, to pass the firewall
– neutron port-update 138f1e36-a4f7-4738-8ffd-3942e0508314
--allowed_address_pairs list=true type=dict ip_address=192.168.32.128/27
• 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
– integrate infrastructure and SAP management
Final Words
38
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:
–
OpenStack @ NetApp
Thank you.
Call to action line one
and call to action line two
www.calltoaction.com
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.