Upload
ecleasing
View
289
Download
1
Tags:
Embed Size (px)
Citation preview
IT Platform Selection by Economic Factors and Information Security
Requirements (SAP Case Study)
2010
А. SHMIDDoctor, Professor
www.ec-leasing.ru
Global System Services
Interpretive InformationSystems
EC-leasing
EC-leasing Soft in Russia
in USA
IBM BP in Russia, USA, Germany
www.ec-leasing.ru
www. gs-s.com
Main Focus – to decrease Total Cost of Ownership (TCO) for corporate customers by
architecture consolidation and create disaster recovery and availability solutions
ЕС- leasing is a Systems Integrator for Major Corporate Customers
EC-leasing – 63% of Mainframe market of RFTwo biggest SAP Computer Centres in RF
Target of the Project: 25% HR decrease in 5 years
FROM(static
physical)
TO(dynamic
virtual
. . . . . . . . . .
Move and share2.Hard + Soft3.Data4.HR
Keep as is:Terminals(regional skills)Regional skills are to be same
1 Regional Branch 39 Regional Branch 78 RCC
S
I
B
F
- done
- in progress
- in progress
- in progress
Settlement System (S)
IA System (I)Book keeping
(B)Financing (F)
Home made IBM BDW 1C SAP
COMPUTER CENTRE (CC)COMPUTER CENTRE (CC)
4 systems share the same resources and FIGHT for resources in virtual environment
PHYSICAL
PHYSICAL
. . .
S I
B F
S I
B F
S I
B F
RussiaWide
Intranet
Unix OS Unix OS 1
Unix OS 2
AIX
HP-UX
Solaris
Linux
Process 1work unit 1(thread 1)
Process 2work unit 2(thread 2)
Process 1work unit 1
Process 2 work unit 2
Two Parallel Processes and Service Outages due to Fight for Resources
(Dynamic resource allocation Outage)
It is impossible to allocate Guaranteed Resource Minimum (GRM) for processes at the UNIX ОS level – consequently possible service outages
Сonsequence: Guaranteed Resource Minimum have to be allocated at the level of:
• Separate Servers
• Domains – Subdomains (SUN) – OS level
• Logical Partitions (LPAR) for IBM z and p – OS level
• z\OS Tasks for IBM z – task level
SAP Case: from SAP Logical Design to Computer Centre (CC) Physical Design
DEFINITIONS:
2. Logical complexity of CC: number of SAP systems can be allocated on CC by SAP rules
3. Efficient CC Performance (EP) (in SAPS): performance, required for SAP logical project (∑ requirements of all SAP systems)
4. Performance to be purchased (PP) - performance of CC to meet both factors: logical complexity of SAP project and requirement of EP for SAP instances
5. Efficiency Factor (EF) : efficient performance / purchased performance
Step #Step # Conceptual levelsConceptual levels # of elements on # of elements on the levelthe level
Prerequisite to Prerequisite to go to the next go to the next
levellevel
CommentComment
1 SAP business processes # of BPs in SAP to be located on CC
# of SAP users for each BP and SAP
user roles
Types of SAP systems order
for CC
2 SAP systems # of SAP systems to be located on CC
Minimum Guaranteed SAP Capacity in SAPS per system (MGC)
Logical complexity order
for CC(SAP systems)
3 SAP hosts for HAS mode # of SAP hosts to be located on CC
∑ MGC for all hosts SAP capacity order for CC
(in SAPS)
4 Platform logical work units for SAP host
allocation(tasks, LPARs, domains)
# of logical platform work units for SAP
host allocation
MGC for each logical Platform
work unit
SAP capacity order distribution
for logical platform work
units
5 Platform physical units for SAP capacity
distribution
# of servers and LPARs / domains with
cores/cpu
Hardware/Software order draft
configuration for competing platforms
Estimate TCO for competing platforms
(∑ $ for 5 years per platform)
Project Steps for Selection of CC Platform for SAPbased on the final CC configuration comparison
AIX: IBM DB2 for z/OS Solaris : Oracle
High Availability System: HAS mode
Page 20Page 23
Configuration Documentation– SAP Tasks
AIX: IBM DB2 for z/OS HP-UX : Oracle
Page 19Page 23
Configuration Documentation– SAP Tasks
High Availability System: HAS mode
Conclusions from SAP documentation: For HAS mode
2. For AIX: IBM DB2 for z/OS: we need to allocate3 SAP hosts on CC for 1 SAP system
3. For HP-UX, Solaris, AIX all with ORACLE: we need to allocate7 SAP hosts on CC for 1 SAP system
We assume that SAP host for HAS mode has to be estimated as Work unit and supplied with GRM not to loose availability
Platform Choice Influence on TCO(High Availability Implementation Case)
Final Configurations, Estimation and Comparison
HP Integrity Superdome
IBM – Power System p6
Sun - SPARC Enterprise
M9000
ProductProduct
152 530
177 950
196 570
SAPSSAPS
1,6
5,0
2,52
Clock Clock (GHz)(GHz)
18 Dec 06
24 March
08
28 June
08
DateDate
32
64
ChipsChips
128
64
256
CoresCores
Looking for Difference in Single Servers (SAP Website)
www.sap.com
For same performance Sun uses 4 times more cores than p and 2 times more than HP: 3 times more power supply for the same performance; 3 times more soft cost
Minimum Resource Allocation on UNIX-Platforms– Hardware-microprogramming Level
(LPAR, Domain, Subdomain)
Domain – LPAR1
Unix OSUnix OS
Domain – LPAR2
Unix OSUnix OS
Domain - 24
(There are no subdomains in High End models)
LPAR - 256
• Domain – minimum resource allocation in a number of processors (a priori at the peak)
• LPAR – allocation in % of overall core performance with the ability to move free resources into other LPAR
• Container – is not appropriate from the guaranteed resources minimum (GRM) viewpoint
LPAR – LPAR : EAL5 (EAL4)
Domain – Domain : NO!
OS Number on a single Server for:SUN – 24
IBM Power - 256
Resources
Dinamic resource allocation
Yes - LPARNo - Domain
Domain – Domain noSubdomain –Subdomain noSolaris thread EAL4+
nPAR – nPAR novPAR – vPAR noHP-UX thread EAL4+
LPAR – LPAR EAL4+ AIX thread EAL4+
LPAR – LPAR EAL5 zOS task EAL4+
http://www.commoncriteriaportal.org/products.html
Sun
HP
IBM p
IBM z
Facilities Certificate (W U) Level
Platform
Existing Certificates on Common Criteria Website
Separate Servers yes yes yesDomain – Domain no yes yesSubdomain – Subdomain no yes yesSolaris thread EAL4+ no no
Separate Servers yes yes yes nPAR – nPAR no yes yesvPAR – vPAR no yes yesHP-UX thread EAL4+ no no
Separate Servers yes yes yesLPAR – LPAR EAL4+ yes yes AIX thread EAL4+ no no
Separate Servers yes yes yesLPAR – LPAR EAL5 yes yes zOS task EAL4+ yes yes
http://www.commoncriteriaportal.org/products.html
Sun
HP
IBM p
IBM z
Platform
Platform Work Units To Be Used For Process Allocation in Parallel Virtual Environment
Facilities Certificate Guaranteed Conclusions Level (С) Resource Availability
(W U) Minimum (GRM) (GRM)
SAP Logical Hosts Allocation On Platform Work Units With GRM
PlatformPlatform Work unit Work unit with GRMwith GRM
Resource Resource order per order per
WUWU
Max # of Max # of WU per WU per serverserver
Max # of Max # of SAP Hosts SAP Hosts per serverper server
Min # of Min # of core/cpu core/cpu per Max # per Max # of WU on of WU on
ServerServer
Min SAPS Min SAPS per Server/per Server/
Host(WU)Host(WU)
IBM z z/OS task LPAR(z/OS)
% of CPU group
(not less than 1% for WU)
100 tasks x 16 LPAR
= 1600 WU
1600 1 CPU 4 680 (0.73)
IBM p LPAR
(AIX,Linux)
% of core group
(not less than 1% for WU)
256 LPAR = 256 WU
256 4 Cores 11 062 (43.71)
SUN Domain
(Solaris)
# of cores per domain
24 Domain = 24 WU
24 24x4=96(1 proc -
4 cores per domain)
73 713 (3071)
Example To Compare Competitive CC Allocation For 78 SAP Systems
NN # SAP # SAP SystemsSystems
LCLC
#SAP #SAP Systems for Systems for
3 3 landscapes landscapes
LCLC
#SAP #SAP hosts in hosts in
HAS modeHAS mode
# Servers for # Servers for host allocationhost allocation
Min Min #Core/CPU #Core/CPU
for 2.3.4.for 2.3.4.
Min # of Min # of SAPS per SAPS per
2.3.4.2.3.4.
1 2 3 4 5 6 7
Sun Solaris(HAS)
78 234 234x7=1638 1638:24=68.25 (69)(24 - #of Sun domain)
69 Servers
1 processor min (4cores) per 1
domain4x24x69=6624
cores
5 086 249
pAIX
(HAS)
78 234 234x7=1638 1638:256=6.4 (7)(256 - #of LPAR for p)
7 Servers
LPAR–0.01 proc1 proc = 2 cores
0.01x2x256=5.12
7x6=42 cores
116 780
z/OS + pAIX(HAS)
78 234 234x3=702 234 DB hosts – z468 App hosts – 2p
3 Servers (1z+2p)
1 CPU z
2x7=14 cores4687+44187
=48 874
To meet logical complexity (LC) for CC.
Min performance for given LC is required to create testing and development landscapes
Logical complexity: 234 systems.Performance 1 000 000 SAPS total for 3 landscapes
SAPS Performance allocation for systemsMin MGC for SAP system – 95 SAPSMax MGC for SAP system – 42 000 SAPS
780%1 245 6501 000 0001638234pAIX
1z + 5p (6)
93%1 067 7001 000 0007022334z/OS + pAIX
Min 69Max 19%Min 5 086 249 for 4 cores on domain,
varies from max 42 000 SAPS to min 95 SAPS
1 000 0001638234Sun Solaris
7654321
Number of Number of ServersServers
EEfficiencyfficiency Factor %Factor %
(4 / 5)(4 / 5)
CC performance to CC performance to be purchasedbe purchased
CC CC performance performance in SAPS in in SAPS in
useuse
#SAP #SAP hosts in hosts in
HAS HAS modemode
#SAP systems #SAP systems for 3 for 3
landscapeslandscapes(Logical (Logical
complexity )complexity )
NN
Final Configuration Comparison for Given Logical Complexity and Effective Performance
Energy Efficiency
Sun 196 570 SAPS – 256 coresIBM Power – 177 950 SAPS – 64 cores
Sun uses 3 times more energy per SAPS than IBM Power
Efficiency Factor for SUN = Efficiency Factor for IBM Power(64:256)x(199 570:177950)= 0.3 (30%) - single server
80%1 245 6501 000 000100%1IBM Power
6%5 086 2491 000 00030%3Sun
EEfffficiencyiciency Factor Factor for CCfor CC
CC CC performance performance
to be to be purchasedpurchased
CC CC performance performance in SAPs in in SAPs in
useuse
Efficiency Efficiency FactorFactor
per 1 SAPs per 1 SAPs
Energy per 1 Energy per 1 SAPsSAPs
On CC level Sun implementation will use 13 times more energy than IBM Power (15 times: z+p)
Computer Centre Characteristics:
Expandability– logical complexity – up to 300 systems
Scalability - up to 1 000 000 SAPS efficient performance
Availability: Downtime
With IBM GDPS – less than 10 minutes a year. BUT depends on WU allocation
Concept: Centralized Architecture of Computer Centre with Virtualization on System z – Power Basis
zEnterprizezEnterprize
At the expandability level - up to 300 SAP Systems – initial configuration equals to final configuration (1z + 5p)
Power Rating according to Gartner Group: №2
z10 Rating according to Gartner Group: №1
Virtual Net of Virtual Application Servers
Virtual Net of Virtual Application Servers
IBM Cluster
EAL5
Up to 60 Base Servers EAL5
PowerPowerEAL4PowerPower
EAL4
Up to 256 Application Servers according to
EAL4 (on each pSeries)
Virtual Net of Virtual Data Base Servers
1. For Large Logic Complexities of SAP landscapes Computer Centres Outages may appear due to WU fight for resourcesThis problem can be resolved for SAP HAS mode via usage of GRM mechanism for SAP hosts
2. On the Single server level, for different platforms there are multiple differences in a number of SAP hosts, that can be allocated with GRM mechanism for each host at the level of Computer Centre.On the Computer Center level, in case of multiplication of servers, these differences increase dramatically
3. Thus for High Availability Computer Centers for SAP Projects –the Main Computer Centre platform dependant Parameters are:
- Number of Servers- Cost of Acquisition for HW - Server Software Cost- Server Energy Cost - Human Resources for Server support- Efficiency Factor- TCO (Total Cost of Ownership)
All these Parameters may vary by times for the same logical complexity and the same efficient performance in SAPS
4. All this Comparisons has to be made for Final configurations on different platforms at the level of the Conceptual Project. The result has to be the Platform Selection for SAP Project
CONCLUSIONS: