use or provide storage cloud with oracle hsm - …konferenz-nz.dlr.de/pages/samfs2017/present/2....

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |

Use or Provide Storage Cloud with Oracle HSM

Dr. Dirk Gebh Principal Storage Sales Consultant Oracle Deutschland 23.06.2017


Program Agenda OHSM Cloud Interfaces

Object Storage – why use OHSM?

Openstack Swift

Architecture Details

1

2

3

3

4


OHSM Cloud Interfaces


Openstack Swift


1

2

4

3

4

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | 5

NAS Storage Use Cloud Storage as additional Archive Tier for OHSM

Tape Archive

Primary Disk Ap

plic

atio

ns

Stan

dard

PO

SIX

File

Sys

tem

API

Cloud Storage

Disk Archive

LDAP

AD

LAN

CIFS

NFS


Object Storage Build Private Cloud Archive Storage based on OHSM

Ope

nSta

ck S

wift

Tape Archive

Primary Disk

Cloud Storage

Disk Archive

REST

API

Appl

icat

ions

WAN

Stan

dard

PO

SIX

File

Sys

tem

http

Keystone




Openstack Swift


1

2

7

3

4


Object Storage – Use Cases

• Media Content Archive • Backup Archive

• File Distribution & Sharing

• Unstructured Data for Analytics

Private Cloud

8

‚Cool- Cold‘ Data Large Files

• Disaster Recovery / Geo-Scale • Disaster Recovery / Cost

• Geo-Scale

• Scalability / Cost

‚Cool-Hot‘ Data No Locking

‚Hot‘ Data

Value of individual Data


Object Storage NAS Storage Comparison

9

Object Storage NAS Storage

Authentication e.g.Openstack Keystone

LDAP / AD

Access Protocol http Swift NFS / CIFS

Network WAN LAN

Structure ID, object, container directory, name, attribut...

Data Access Get / Put / Delete no Locking

Read / Write / Change FS Locking

Latency High Low

Scalability infinite depends on NAS system (very high for OHSM)


Based on Standard Server Farm Example: 10PB Object Storage – Power and Heat

standard server approach capacity [TB] power [w] heat [BTU/h] number X6-2L 1* 10 Core 2,2GHZ /128GB / 600GB OS disk 12*8TB data disk 80 252 860 1

10 PB (3 copies) 30000 94500 322500 375

network switch 64 Ports 625 2133 1

3750 12798 6

total 98250 335298


Based on Oracle HSM Example: 10PB Object Storage – Power and Heat

OHSM Solution capacity [TB] power [w] heat [BTU/h] number

S7-2 1* 8 Core 4,27GHz / 128GB / 2* 600GB OS Disk 3* dual FC Card

347 1184 1

HSM server + 3* QFS client 1388 4736 4

SAN Switch Brocade 6505 80 338 1

Disk Cache ZS5-2 Head 591 2017 1

Disk Tray DE3 327 1116 1

disk cache 1 PB 1000 1962 6696 6 SL3000 / 8 drives LTO7 / 3400 slot 20000 618 2109 1

total 4639 15896


Example: 10PB Object Storage – Power and Heat

Oracle HSM solution has

factor 21 less power and heat consumption !!

12




Openstack Swift


1

2

13

3

4


OpenStack - a standardized construction kit


What means standard in detail?


OpenStack Swift Releases – Pike (2.14.0) – Ocata (2.11.0…2.13.1) – Newton (2.8.0 …2.10.2) – Mitaka (2.6.0 … 2.7.1) <= Oracle Linux / next Solaris – Liberty (2.4.0 … 2.5.0) – Kilo (2.2.1 …. 2.3.0) <= Solaris 11 – Juno (2.0.0 … 2.2.0)

16

– Icehouse (1.11.0 … 1.13.1) – Havana (1.9.0 … 1.10.0) – Grizzly (1.7.5 … 1.8.0) – Folsom (1.5.0 … 1.7.4) – Essex (1.4.4 … 1.4.8) – Diablo (1.4.0 ….1.4.3) – Cactus (1.3.0 – Bexar (1.2.0) – Austin (1.1.0)


Swift Architectural Overview • Proxy Server

– route request (account, container, object) – Encoding, decoding

• The Ring – Mapping between the names stored on disk and their physical location – Separate rings for accounts, containers per storage policy – Mapping zones, devices, partitions and replicas (default 3) – Handoff devices for failure scenarios – Moving one replica if new device is added

• Zones – Isolated failure boundaries

17


Swift Architectural Overview • Storage Policy

– exposed to client via an abstract name – each device assigned to one or more policies (=> multiple object rings) – > different storage tiers or number of replicas

• Object Server – blob storage server – binary files with metadata in extended attributs (xattrs) – path, object names hash and timestamp – deletion treated as version (=> replicated correctly)

18


Swift Architectural Overview • Container Server

– listings of objects in specific container – sql lite database replicated across the cluster

• Account Server – listings of containers

• Replication – compare local / remote data (hash) – push based replication (rsync)

• Reconstruction – used by erasure code policies

19


Swift Architectural Overview • Updaters

– needed for very high load or failure when container or account data can not be immediately updated

– update locally queued

• Auditors – check integrity of objects, containers and accounts – corrupted files quarantined and replaced from replica

20


Object Storage




Openstack Swift


1

2

22

3

4


Object Storage based on Oracle HSM


Swift Proxy Node – OpenStack Keystone • MySQL database

– administrative user – keystone service DB

• Keystone config file – /etc/keystone/keystone.conf

• Keystone services • Keystone and Swift endpoints • Proxy Server

– /etc/swift/proxy-server.conf

24

• Swift – /etc/swift/swift.conf

– > identical copy on all Swift storage nodes

• Configure The Ring


Swift Storage Node – QFS Client

• Packages: Swift -account, Swift-container, Swift-object • Account and container information stored on local storage (SSD !)

– > replicated to three different storage nodes

• Configure rsync

25


Swift Storage Node – different OHSM Systems

26


Conclusion • Oracle HSM can be used as private storage cloud platform

– Very cost effective – Large scaleout

• Object Interface today is OpenStack Swift – Swift proxy – Swift Storage Nodes as QFS clients (Linux or Solaris) – SAM/ QFS meets requirement of OpenStack Object Server (extended attributs) – Objects stored in QFS filesystem – > all well known featuers of Oracle HSM can be used

27


Archive Your Data with OHSM Private Cloud

Thank You for Your Attention !

use or provide storage cloud with oracle hsm - …konferenz-nz.dlr.de/pages/samfs2017/present/2....

Documents