Erik Julin

Sr. Director, Technical Business Development

Open-Xchange

Summit 2017

Brussels

Introducing Scality

(in 2 slides)

Scality RING Architecture

• Scale-out – access and capacity (millions of clients, billions of objects)

• Any-to-Any – any client can access any object in parallel with no added latency

• Shared-nothing – no ”master” metadata node or SPOF for high availability

• Self-healing – automated, fast repair and rebuild

• 100% Software – complete hardware choice, flexible deployment, 100% available during SW/HW upgrades, no data migrations

SCALITY RING SOFTWARE

Management

Local and Geo-Protection, Self-healing

Object & File Access

Advanced Routing, Object Storage

OBJECTAPPLICATIONS

FILEAPPLICATIONS

……

STANDARD LINUX / STANDARD x86 SERVERS

Scality Confidential 2

Scality RING Key Components

Scality RING Software Infrastructure

STORAGE NODESHighly durable, scale-out object storage

CONNECTOR NODESFile, Object, Email Access

SUPERVISORManagement GUI and CLI

STORAGE SERVERSConnector and Storage Nodes both run on the storage servers. Based on use case, Connectors can also be run separately on physical or virtual servers

MANAGEMENT SERVERCan run on physical or virtual servers

Scality Confidential 3

Optimized for email

In production since 2010

Dozens of deployments

Hundreds of millions of accounts

Scores of petabytes stored

Trillions of objects

Scality for Email

4

Scality / Dovecot

Integration

5

Dovecot Pro / Scality: High Level Multi-site Architecture

Dovecot Pro / Scality: Connection to RING

Site A and Sit B active concurrently. Users have affinity to a site.

Dovecot Pro Backend uses sproxyd (HTTP/REST) API to communicate with RING.

Backend servers with software LB like HAProxy or external LB.

LB has pool of sproxyd connectors for local data center. Simple stateless load balancing.

sproxyd connectors, co-located on storage servers, distribute objects to storenodes

RING keyspace guarantees two copies per data center for Class of Service(3)

Sizing

Methodology

Enhancements

8

Key e-mail Parameters for Sizing RING▪ peak message delivery per second (post AA/AV)

▪ peak message retrieval per second

▪ peak message delete per second

▪ average message size

▪message storage capacity

Add▪ data center topology

▪ SLAs

▪ few more relevant details...

Sizing RING for e-mail

9

RING Parameter Email Parameter Conversion (apply Magic Sauce)

PUT/sec msg delivery/sec msg delivery + indices generated

GET/sec msg retrieval/sec msg read + index object reads + HEAD operations

DEL/sec msg del/sec msg del + index obj del

average object size average msg sizeweighted average of msg size post compression,all indices

total usable capacity stored email capacitystored email capacity + capacity of all indices + capacity of objects pending purge

RING Sizing Inputs

10

Methodology worked well, but...

tended to modestly overestimate RING loading

which is much better than underestimating

RING Sizing

11

Now Dovecot supplies directly transaction rates▪ peak object PUTs per second

▪ peak object GETs per second

▪ peak object DELs per second

Removes assumptions mapping messages to objects

Scality still validates metrics, applies our experience, especially for average object size and total capacity

RESULT – less time to BOM, reduction in cost, greater confidence

New Methodology

12

Introducing

Stretched RING Failover Optimization

for Dovecot

(a.k.a. CoST)

13

Dynamic RING Failover Optimization

a.ka. Class of Service Translator (CoST)

Introduced in RING 6 (2016) as an optionally licensed feature to

• Reduce raw storage requirements

• Reduce IO requirements

• Improve data durability

Invoked only during RING partition events, e.g.

• Loss of data center

• Loss of WAN connectivity

Now available for Dovecot Pro using sproxyd API

Dynamic RING Failover Optimization Applicability

Dynamic RING Failover Optimization feature applies only to

• Immutable objects• all mail ISVs integrated with RING treat objects as immutable

• Protected via replication• vast majority of email deployments use replication

• typically lowest TCO

• lowest latency for multi-geo

• Deployed in multi-geo configuration

RING Background

• Self-healing operations

• Rebuild – Recreates “missing” copies/chunks of objects.

• Repair – optimized version of repair, where there is a list of “missing” objects, such as during a disk failure. If process dies or server reboots then a rebuild is necessary

• Rebuild is an “all or none” operation

• Rebuild every missing copy.

• By default rebuild is automatically disabled during site failure.

• If full rebuild needed, then additional raw capacity may be needed

• Repair operation

• Can occur during site failure

17

RING: CoS(3) PUTS on Fully Operational RING

18

RING: CoS(3) PUTS after Failed DC

CoS(3): 4 Replicas to

surviving DC

RING

Storage Server

Connector

RING

Storage Server

Connector

RING

Storage Server

Connector

RING

Storage Server

Connector

RING

Storage Server

Connector

RING

Storage Server

Connector

Replica 0

Replica 1

Replica 3

RING

Storage Server

Connector

RING

Storage Server

Connector

Replica 2

Data Center A Data Center B

19

RING: CoS(F) PUTS after Failed DC

CoS(F): 2 Replicas

per DC

RING

Storage Server

Connector

RING

Storage Server

Connector

RING

Storage Server

Connector

RING

Storage Server

Connector

RING

Storage Server

Connector

RING

Storage Server

ConnectorReplica 0

RING

Storage Server

Connector

RING

Storage Server

Connector

Replica 1

Data Center A Data Center B

20

Benefits of CoST

Significant reduction in IO load during site failure

Rebuilds during site failure without doubling raw capacity

Much higher data durability during site failure

• Not nearly as good as normal operations

Can save significant

• hardware CapEx (30-50%) and associated OpEx

• RING capacity license

Scality RING

Deployed Architectures

for Email

21 Scality Confidential

Single Site RING

22

Two-site Stretched RING

23

Three-site Stretched RING

24

Two-sites with Async Replication

25

Data Center A

Data Center B

Single Site – pre-planned Two-site Growth

26

Single Site – pre-planned multi-site

27

555 California Street, Ste 3050, San Francisco, CA 94104, USA

Email: sales.us@scality.com | Telephone: +1 (650) 356-8500 | Fax: +1 (650) 356-8501 | Toll Free: +1 (855) 722-5489

scality.com

Thank You

Erik Julinerik.julin@scality.com

+1 781 572 09390