Upload
yew-jin-kang
View
133
Download
0
Embed Size (px)
Citation preview
3rd Annual Technology & Innovation –Future of Banking & Financial Services
Establishing a Shared Service Platform
for Databases
May 2015
2
■Traditionally, these are how databases are set up
2 x P740 (PRD)
DB2:
• CV-RIB MY
2 x P720 (DR)
DB2:
• CV-RIB MY
1 x P740 (UAT/SIT)
DB2:
• CV-RIB MY
1 x Wintel (PRD)
MSSQL:
• Siebel 6
1 x Wintel (UAT/SIT)
MSSQL:
• Siebel 6
1 x P5 (PRD)
DB2:
• FPX/ePay
1 x P5 (UAT/SIT)
DB2:
• FPX/ePay
1 x RS6000 (PRD)
DB2:
• BScore
1 x RS6000 (UAT/SIT)
DB2:
• BScore
4 x T3-2 (PRD)
Oracle 11g SE:
• LOAD$ MG, CC & PL
2 x T3-2 (UAT/SIT)
Oracle 11g SE:
• LOAD$ MG, CC & PL
2 x P720 (PRD)
Oracle 11g SE:
• AML MY & VN
1 x P720 (UAT/SIT)
Oracle 11g SE:
• AML MY & VN
c1
c2
c4
c5
1 x P5 (PRD)
Oracle 10g:
• HL Wealth Planner
1 x P5 (UAT/SIT)
Oracle 10g:
• HL Wealth Planner
1 x Intel (PRD)
Oracle 9i on Linux:
• UTNS
1 x Intel (SIT/UAT)
Oracle 9i on Linux:
• UTNS
1 x Intel (PRD)
MySQL on CentOS:
• 8i Token MY
1 x Intel (UAT/SIT)
MySQL on CentOS:
• 8i Token MY
2 x M4000 (PRD)
DB2:
• CIB MY
1 x M4000 (UAT/SIT)
DB2:
• CIB MY
c3
p3
p4
c5
c6
w1
w2
w3
w4
p1
p2
p5
p6
p9
p10
p7
p8
Legend:
• Tech refresh completed
• Tech refresh WIP
• Tech refresh in planning
• New initiative completed
• New initiative WIP
• New initiative in planning
c1
w1
p1
1. Capital Expenditure Request includes
Capex/Opex for hardware, software &
professional services for 3 or 5 years
2. Charge-out based on agreed percentage
to business unit 1, 2, 3 etc
1. Capital Expenditure Request includes
Capex/Opex for hardware, software &
professional services for 3 or 5 years
2. Charge-out based on agreed percentage
to business unit 4, 5, 6 etc
1. Capital Expenditure Request includes
Capex/Opex for hardware, software &
professional services for 3 or 5 years
2. Charge-out based on agreed percentage
to business unit 7, 8, 9 etc
1. Capital Expenditure Request includes
Capex/Opex for hardware, software &
professional services for 3 or 5 years
2. Charge-out based on agreed percentage
to business unit 10, 11, 12 etc
No Challenges
1 High Capex/Opex for silo
hardware
2 Long time-to-market (e-bidding,
procurement etc) for each
project
3 Data center exhausted with
heterogeneous hardware,
increase facility cost
4 Decrease operation efficiency
3
■How can we make this more efficient?
Oracle Infiniband
Switch
Oracle Infiniband
Switch
40
Gb
ps In
finib
and
Fa
bric
6 Oracle SPARC T5-2 Servers
Oracle ZFS Clustered Storage
Clustered
MY CRELOAD$ VN WLL G.Earth IB.Fraud
We built a shared infrastructure/ private cloud
Currently built with 6 Oracle T5
hardware nodes running at least
10 application databases in
production
Built with no single point of
failure, clustered hardware and
software, and storage with
compression
4
■What benefits does our Private Cloud provide?
Core License Core License Core License Core License
1 Fuzion ESS 2
2 Fuzion MY 2
3 Fuzion VN 2
4 LOAD$ HP 8
5 LOAD$ MG 4
6 LOAD$ CC/PL/RCB/SME 4
7 Siebel 4
8 CRE 4
9 WLL 4 2
10 Green Earth 4 2 2 1
11 IB Fraud 4 2 2 1
12 FPX 2 2
13 EAI (WMB & DataPower) 2 2
14 Falcon 2 -
15 Basel II 4 4
16 Fuzion KH 2 2
17 Fuzion SG 2 2
18 8i Token SG 2 2
19 WinOps & CMS 4 2 4 2 1 1
20 8i Token MY - - - - - - - -
21 MVI Payment Gateway SG - - - - - - - -
22 LOAD$ VN - - - - - - - -
23 Basel II VN - - - - - - - -
24 UTNS MY - - - - - - - -
25 CMS - - - - - - - -
62 26 26 10 10 5 10 5
SIT
10
2
2
PRD
4 2
4
DR
10
UAT
Total
10
8
2
2
No Projects
Squeeze more in Less Better Resource Utilisation
Scalability &
Elasticity
Faster Database Provisioning
5
■Database Private Cloud: Greatest advantage is cost avoidance
5
2 x P740 (PRD)
DB2:
• CV-RIB MY
2 x P720 (DR)
DB2:
• CV-RIB MY
1 x P740 (UAT/SIT)
DB2:
• CV-RIB MY
1 x Wintel (PRD)
MSSQL:
• Siebel 6
1 x Wintel (UAT/SIT)
MSSQL:
• Siebel 6
1 x P5 (PRD)
DB2:
• FPX/ePay
1 x P5 (UAT/SIT)
DB2:
• FPX/ePay
1 x RS6000 (PRD)
DB2:
• BScore
1 x RS6000 (UAT/SIT)
DB2:
• BScore
4 x T3-2 (PRD)
Oracle 11g SE:
• LOAD$ MG/CC/PL
2 x T3-2 (UAT/SIT)
Oracle 11g SE:
• LOAD$ MG/CC/PL
2 x P720 (PRD)
Oracle 11g SE:
• AML MY/VN
1 x P720 (UAT/SIT)
Oracle 11g SE:
• AML MY/VN
Target Pro
d/D
R
UA
T/S
IT
c1
c2
c4
c5
5 x T5-2 Existing Server
(PRD/DR/UAT/SIT)
Oracle 11gR2 EE:
• Fuzion RIB MY
• Fuzion RIB VN
• Siebel 8
• LOAD$ HP/MG/CC/PL
• CRE
• WLL
• GreenEarth
• IB Fraud
• FPX/ePay
• EAI
Oracle 12c EE:
• Falcon
• Fuzion RIB KH
• Fuzion RIB SG
• 8i Token SG
• Basel2
• HLIB WinOps
2 x T5-2 New Server
(PRD/DR/UAT/SIT)
Oracle 12c EE:
• MVI SG
• 8i Token MY
• UTNS
• LOAD$ VN
Next expansion:
• AML MY/VN
• Cash Mgmt
1 x P5 (PRD)
Oracle 10g:
• HL Wealth Planner
1 x P5 (UAT/SIT)
Oracle 10g:
• HL Wealth Planner
1 x Intel (PRD)
Oracle 9i on Linux:
• UTNS
1 x Intel (SIT/UAT)
Oracle 9i on Linux:
• UTNS
1 x Intel (PRD)
MySQL on CentOS:
• 8i Token MY
1 x Intel (UAT/SIT)
MySQL on CentOS:
• 8i Token MY
Baseline
2 x M4000 (PRD)
DB2:
• CIB MY
1 x M4000 (UAT/SIT)
DB2:
• CIB MY
c3
p3
p4
c5
c6
w1
w2
w3
w4
p1
p2
p5
p6
p9
p10
p7
p8
c1 c2 c3
c4 c5
w1 w1
c5 c6
w3 w4
p5 p6
p1
p7 p8
p9 p10
p2
Legend:
• Tech refresh completed
• Tech refresh WIP
• Tech refresh in planning
• New initiative completed
• New initiative WIP
• New initiative in planning
c1w1
p1
Oct’14
Nov’14Mar’14
May’15
May’15
KIV
May’15
TBD
TBD
TBD
Projects (Cost Avoidance 3 years TCO) Silo (MYR) Cloud (MYR)
Fuzion MY/VN, Siebel, LOAD$, CRE, WLL, GreenEarth, IBFraud 30,035,765 9,990,252
FPX, EAI, Basel2, Falcon, Fuzion RIB KH/SG, 8i SG, WinOps 27,800,228 10,378,287
MVI SG, 8i Token MY, LOAD$ VN, UTNS 14,561,224 1,795,580
AML MY/VN, Cash Mgmt 7,280,612 4,000,000
Total 79,677,829 26,164,119
4:1
~RM XXX M
Cost Avoidance
6
■Awards….
Awarded by IDC on March 6 at Asian Financial Services Congress 2015. This is its 11th consecutive year
Over 80 entries by banks across the region. HLB is a winner in the category of infrastructure
Each year, IDC Financial Insights invites banks across Asia/ Pacific to nominate initiatives in the area of innovation. The
award recognizes successes of these institutions in displaying innovation to achieve business objectives
IDC Financial Insights is the region's leading research & advisory firm, helping financial institutions choose or short list
solutions and vendors, assess their business or IT master plans. They are headquartered in Massachusetts, USA.
7
■Recognition…
Featured on Oracle Website
Oracle whitepaper based on HLB design
8
■Cloud?
9
■Challenges - Governance
10
■Challenges – Managing the Cloud
11
■Challenges – Determining what goes into the cloud
12
■Challenges - Eradicating Single points of failure
13
■Challenges - Virtualisation & Physicality are Interdependent
14
■Challenges – Chargeback (Previous)
Initial Projects (Jun’13)
1. Fuzion RIB/ESS MY
2. Fuzion RIB VN
3. Siebel 8
4. LOAD$-HP/MG/CC/PL
5. CRE
Additional Projects (Jan’14)
6. WLL
7. Green Earth
8. IB Fraud
Cloud Expansion Projects (Sep’14)
9. FPX/ePay
10.EAI
11.Falcon
12.Basel 2
13.Fuzion RIB KH
Additional Projects (Nov’14)
14.Fuzion RIB SG
15.8i Token SG
16.HLIB WinOps & CMS
New Projects (Jan’15)
17.8i Token MY
18.MVI Payment Gateway SG
1. Bulk purchase cloud hardware,
software & professional services for
3 or 5 years
2. Charge-out based on agreed
percentage to business unit 1, 2, 3 etc
1. Each Capital expenditure request only
includes additional storage, software
& professional services for 3 or 5
years
2. Charge-out based on agreed
percentage to business unit 4, 5, 6 etc
1. Bulk purchase cloud expansion
hardware, software & professional
services for 3 or 5 years
2. Charge-out based on agreed
percentage to business unit 7, 8, 9 etc
1. Each Capital Expenditure request only
includes additional storage, software
& professional services for 3 or 5
years
2. Charge-out based on agreed
percentage to business unit 1, 2, 3 etc
No Challenges
1 High Capex/Opex for silo hardware
Lower Capex/Opex overall
2 Long time-to-market (e-bidding,
procurement etc) for each project
Shorten Lower Capex/Opex
for overall projects
3 Data center exhausted with
heterogeneous hardware, increase
facility cost
Standardize infrastructure
4 Decrease operation efficiency
Improve operation efficiency
5 Difficult to align bulk purchase
timeline for multiple projects
6 Un-fair business model as only
initial project fully bear the
Capex/Opex base infrastructure
7 Might not able to consolidate
few projects to contribute for
future expansion
15
■Challenges – Chargeback (Now)
Proposed To-Be Cloud Chargeback Methodology
Initial Projects (Jun’13)
1. Fuzion RIB/ESS MY
2. Fuzion RIB VN
3. Siebel 8
4. LOAD$-HP/MG/CC/PL
5. CRE
Additional Projects (Jan’14)
6. WLL
7. Green Earth
8. IB Fraud
Cloud Expansion Projects (Sep’14)
9. FPX/ePay
10.EAI
11.Falcon
12.Basel 2
13.Fuzion RIB KH
Additional Projects (Nov’14)
14.Fuzion RIB SG
15.8i Token SG
16.HLIB WinOps & CMS
New Projects (Jan’15)
17.8i Token MY
18.MVI Payment Gateway SG
No Challenges
1 High Capex/Opex for silo hardware
Lower Capex/Opex overall
2 Long time-to-market (e-bidding,
procurement etc) for each project
Shorten Lower Capex/Opex for
overall projects
3 Data center exhausted with
heterogeneous hardware, increase
facility cost
Standardize infrastructure
4 Decrease operation efficiency
Improve operation efficiency
5 Difficult to align bulk purchase
timeline for multiple projects
Reserved capacity
6 Un-fair business model as only
initial project fully bear the
Capex/Opex base infrastructure
Chargeback by allocation
7 Might not able to consolidate few
projects to contribute for future
expansion
Cloud Cost CenterReserved capacities
under Cloud Cost Center
for upcoming projects or
organic business growth
Proposed chargeback process:
1. Finance summarizes the existing cloud
total investment for hardware & software
2. Custodian to calculate the chargeback
block for hardware & software into a cloud
catalogue
3. Custodian to provide the capacity
allocation & derive the chargeback cost
by project
4. Finance to manage the chargeback to
respective business units into Cloud Cost
Center
Chargeback for new projects:
1. Monthly chargeback of Capex/Opex for
cloud infrastructure to business unit
2. Chargeback the professional services to
project
3. IT to purchase new Cloud expansion in
advance and keep the capacities for next
business project using Cloud Cost Center
Chargeback for existing projects:
1. Monthly chargeback of Opex only for
cloud infrastructure to business unit for
next 2 years and chargeback Capex/Opex
thereafter
16
■Challenges – Chargeback (Future)
Proposed To-Be Cloud Chargeback Methodology
Initial Projects (Jun’13)
1. Fuzion RIB/ESS MY
2. Fuzion RIB VN
3. Siebel 8
4. LOAD$-HP/MG/CC/PL
5. CRE
Additional Projects (Jan’14)
6. WLL
7. Green Earth
8. IB Fraud
Cloud Expansion Projects (Sep’14)
9. FPX/ePay
10.EAI
11.Falcon
12.Basel 2
13.Fuzion RIB KH
Additional Projects (Nov’14)
14.Fuzion RIB SG
15.8i Token SG
16.HLIB WinOps & CMS
New Projects (Jan’15)
17.8i Token MY
18.MVI Payment Gateway SG
No Challenges
1 High Capex/Opex for silo hardware
Lower Capex/Opex overall
2 Long time-to-market (e-bidding,
procurement etc) for each project
Shorten Lower Capex/Opex for
overall projects
3 Data center exhausted with
heterogeneous hardware, increase
facility cost
Standardize infrastructure
4 Decrease operation efficiency
Improve operation efficiency
5 Difficult to align bulk purchase
timeline for multiple projects
Reserved capacity
6 Un-fair business model as only
initial project fully bear the
Capex/Opex base infrastructure
Chargeback by allocation
7 Might not able to consolidate few
projects to contribute for future
expansion
Cloud Cost CenterReserved capacities
under Cloud Cost Center
for upcoming projects or
organic business growth
Proposed chargeback process:
1. Finance summarizes the existing cloud
total investment for hardware & software
2. Custodian to calculate the chargeback
block for hardware & software into a cloud
catalogue
3. Custodian to provide the capacity
utilization & derive the chargeback cost
by project
4. Finance to manage the chargeback to
respective business units into Cloud Cost
Center
Chargeback for new projects:
1. Monthly chargeback of Capex/Opex for
cloud infrastructure to business unit
2. Chargeback the professional services to
project
3. IT to purchase new Cloud expansion in
advance and keep the capacities for next
business project using Cloud Cost Center
Chargeback for existing projects:
1. Monthly chargeback of Opex only for
cloud infrastructure to business unit for
next 2 years and chargeback Capex/Opex
thereafter
Upon maturity of
cloud monitoring
& metering
17
■Chargeback components of a private database cloud1 unit Server Rack
2 units Infiniband Switches
12 units T5-2 Servers
For each T5-2 server
• 512 GB memory per server
• 64GB memory reserved for Control Domain
• Each DB VM block is 8GB memory
• Total 56 blocks available [448/8=56]
For each Server Rack
• Total 12 servers
• Total blocks: 12*56=672
Standard allocation is 0.5 core per 8GB memory
1 unit Storage Rack
2 units Infiniband Switches
4 units ZFS
Storage Controller
(36 Drives)
For each Storage Drive
• 1TB reserved for workarea
• 8TB usable for DB
• Each storage block is 100GB
• Total 80 blocks available [8000/100=80]
For each Storage Rack
• Total 4 storage controller (36 drives each)
• Total blocks: 4*36*80=11,520
Proposed hardware chargeback block:
1. Oracle DB Cloud consists of 2 key components:
servers & storage drives
2. Server will be chargeback by core & memory allocation
3. Storage drive will be chargeback by storage allocation
18
■Chargeback – actual in action
Core License Core License Core License Core License
1 Fuzion ESS 2
2 Fuzion MY 2
3 Fuzion VN 2
4 LOAD$ HP 8
5 LOAD$ MG 4
6 LOAD$ CC/PL/RCB/SME 4
7 Siebel 4
8 CRE 4
9 WLL 4 2
10 Green Earth 4 2 2 1
11 IB Fraud 4 2 2 1
12 FPX 2 2
13 EAI (WMB & DataPower) 2 2
14 Falcon 2 -
15 Basel II 4 4
16 Fuzion KH 2 2
17 Fuzion SG 2 2
18 8i Token SG 2 2
19 WinOps & CMS 4 2 4 2 1 1
20 8i Token MY - - - - - - - -
21 MVI Payment Gateway SG - - - - - - - -
22 LOAD$ VN - - - - - - - -
23 Basel II VN - - - - - - - -
24 UTNS MY - - - - - - - -
25 CMS - - - - - - - -
62 26 26 10 10 5 10 5
SIT
10
2
2
PRD
4 2
4
DR
10
UAT
Total
10
8
2
2
No Projects
Proposed software chargeback block:
1. Chargeback 1 OPL for every 4 cores allocation (50% savings
from Oracle standard licensing model)
2. GITA/GITI to monitor the actual core utilization before next OPL
purchase for more core activation
For Oracle DB EE License (OPL)
• Each OPL allows activation of 2 core
• Initial projects started with 16 OPL
• Additional projects contribute some OPL
to the Cloud
• Cloud expansion projects contributed
additional 16 OPL
Server Core Allocation & Shared Pool
• Each project to contribute minimum
software license to enable more cores
into the shared pool
• Each application able to utilize unused
core within the shared pool
• Designed based on the concept of
maximizing cores sharing across multiple
applications by leveraging on the
differences during idle/peak hours
19
■Future?
Application
Platform
Customizations
Application
CustomizationsC
on
su
mer
Se
rvic
eP
rovid
er
Infra as a Service
Platform as a
Service
IT Professional Developer
HLB’s Wintel Cloud housing
- Branch teller, Siebel etc
- HLB’s Oracle T5 infra
housing Oracle database
HLB’s Wintel Cloud housing
- Windows applications
- HLB’s Oracle Cloud running on
the Oracle T5s
- WebSphere private cloud for
Java applications (eg Fuzion)
Presentation Tier
Data Tier
Business Logic Tier
Typical application schematic
1
1
2
4
2
33
4
4
Oracle
T5 hardware
Wintel
IBM
New WebSphere Cloud
for Java apps
Expansion of existing
clouds
5
5
Due to early success of the private clouds, HLB intends to expand
these cloud infrastructures to add more workloads into the cloud and
focus on virtualization to promote sharing and reduce server footprint
20
Thank You