SDS: Object or File: How to Choose?

Transcription

1 SDS: Object or File: How to Choose?

2 Storage Industry is Transforming like Compute Virtualization Performance and reliability designed for ten years ago Embedded software tied to hardware Disks and components marked up multiple times along value chain From Monolithic Appliances To Pure Software on Standard Servers HW-Agnostic Software Industry Standard Servers BETTER: Performance Reliability Flexibility Economics

3 SDS Replaces Traditional File Storage Silos LOW LATENCY Flash $5/GB SAN $2/GB (EMC) Storage Defined Software on Standard x86 $[ ]/GB TERABYTES OBJECT $0.70/GB (Cleversafe) EXABYTES NAS $1/GB (EMC/NTAP) TAPE $0.10/GB (Quantum) HIGH BANDWIDTH HW+SW acquisition costs

4 Scality Key Facts Founded: 2009 Product release: July 2010 $85M venture capital San Francisco (HQ), Washington, Paris (Engineering), Tokyo, Boston, Singapore 150+ people Product: Scality RING software Markets: Service Providers, Banks, Media, Government 250% global sales growth in 2014 DNA: Webmail storage for 200M users, requiring high durability, 24x7 availability, instant access, & low cost 85+ cloud-scale customers in production worldwide

5 Scality RING: Software for Storing the Information Age Throughput performance scales from 15GB/s to infinity 100% reliability with minimal intervention, at massive scale Pure software runs on any x86, Linux-based servers, even mixed generations Just works, as proven in the most demanding environments

6 85+ Cloud-scale Production Customers Worldwide Consumer Service Providers Web & Cloud Services Two of Japan s largest Telcos Media Largest post-production Largest cable network Very large retail Enterprise Multiple large Healthcare Multiple large Manufacturers Multiple large Financials Govt/Research

7 What issues does Exascale raise? 8 TB Drives 60 Drives/Server/4U 2% drive failure/year 1MB average file size 1 Exabyte 100PB 1PB Drives 125,000 12, Daily disk loss Servers Number of Files 1,000,000,000, ,000,000, MB/sec, 22 hours to fill a 8TB drive, 1Tb network ~100 days to move 1Exabyte IF load is well balanced across all drives

8 Where is Scality Today? 1 Exabyte 100PB 1PB Drives 125,000 12, Daily disk loss Servers Number of files 1,000,000,000, ,000,000,000 1,000,000, Servers > 80 Billion Files 50 PBs with 100s of PB in view

9 Object Storage isn t a Grail Object storage doesn t save space Most applications expect POSIX file systems so there is much work to be done: eg Whamcloud/Intel DAOS. We will need to do the work! Hierarchical models are a good way to organize data File locking: multiple writers & sync issues don t just go away

10 But, the Grass is Greener on Object Storage! Object storage manages 1000 s fewer things Only useful data is rebuilt in the case of drive loss Massively parallel reads and writes are straightforward Each object or collection has meaning: the blocks of traditional systems have no intrinsic meaning Maintaining system-wide consistency is not required Geo-Distribution becomes realistic

11 What about Data Integrity? Note: RAID 5 < 4x9s, Raid 6 < 5x9s, 3 Copies ~ 7x9s (1 year) With 7 x 9s ~ 1/100,000 chance of losing data, but if we have billions of files, the likelihood is very high ARC(8,4) gives > 11x9s of durability similar to 4 copies with 1.5 overhead Silent Data Corruption CERN found that in 15PB of data 38,000 files were corrupted Unrecoverable Tape error rates every 1PB LSE ~ Indicates Disk bit error every 10TB accounts for ~ 5-10% of risk compared to drive failures Scality stores and checks CRC on every object

12 High-level RING Architecture

13 Scality RING software-defined storage components Multi-app FILE-BASED OBJECT-BASED OPENSTACK-BASED Linear performance scaling PARALLEL, HIGH PERFORMANCE ACCESS TO DATA SCALITY RING SOFTWARE-DEFINED STORAGE Connectors Data Protection and Geo-Redundancy Management Core RING x86 servers Limitless infrastructure scaling

14 Scality RING Technology Architectural Deep dive

15 Core RING Design Principles Core RING 100% Parallel System Skip Technical Presentation Fully distributed data & metadata No Single Point of Failure Durable & Resilient Location & geo-aware for durability (disks, servers, racks, sites) Self-healing for component failures Always available even during upgrades Hardware agnostic User space software, no kernel modifications Runs on any hardware without requiring certification

16 Core RING topology: an extremely resilient system designed to tolerate failure Core RING

17 What is Replication? Data Protection and Geo-Redundancy Optimal for small objects & files Class of service can be set from 0 to 5 replicas (1 to 6 copies) Location-aware Data placement across failure domains Locates replicas across disks, servers, racks, sites No data transformation Clear / native data format for very fast access Simple projection (no need to store replica keys) Self-healing Auto-heals missing replicas or parity blocks Auto-rebalancing for new or dropped nodes Transparent proxy for object being balanced Permanent CRC of all contents (no silent data corruption)

18 Data Protection and Geo- Redundancy Intelligent Data Protection: Replication, Erasure Coding & Geo-distribution Replication ARC Erasure Coding Geo- distribution Scality RING Software Defined Storage Copyright Scality 2015

19 What is Erasure Coding? Data Protection and Geo-Redundancy Scality ARC (Advanced Resiliency Configuration) Erasure coding for optimal data protection of large files and objects Avoids the overhead of multiple replicas (data copies) Dynamically configurable schema (data + parity chunks) to protect against variable number of failures with improved efficiency versus replication Protects against disk, server, rack or data center level failures Flexible & Efficient Select replication or ARC strategy per object/file (or policy-based) Data chunks stored in clear to avoid read performance penalties ARC data and correction chunks are always contiguous. For example: 9+3 Schema provides three disk failure protection with ~33% space overhead data chunks parity chunks

20 Zoom on the Access

21 The Data Path Key BCEEE8B99EB9E96E71AF EFA8B35D2011? APPLICATION/CONNECTOR Chord lookup (IP) IP:PORT DATA STORAGE NODE DATA DATA BIZIOD.DAT File operation on IP:PORT lookup on biziod attached to HDD read length from.dat file at offset Skip chain lookup (memory) HDD for key bizobj lookup (file).dat file + offset + length Node with key on disk bizobj.bin HDR HASH TABLE key data key data key data key data key data key data key data key data HASH TABLE key data key data. Skip Chain BizObj.bin Determines: *.DAT File * Offset Maintains: * Version * Times * Status RAM-based Skip Chain returns: * Existence * BizIOD Ref (which HDD?) * Version * Status Flag 21

22 New Storage Strategies BIZIOD w/ HSE - Release M BIZOBJ CONTROL LSM DATA STRATEGY HSE Index Storage SQLite B-Tree Containers IP-Drive (Kinetic API) Pluggable Architecture Multiple Indexing Strategies Multiple Object Storage Strategies Kinetic Interface Plug-in replacement to bizobj Slide 22

23 Sprov part of Scality s sauce Data placement Optimization: Data wisely spread across servers, sites & racks to support site, rack and server failures Data equally distributed by disk space heterogeneous server capacity Minimize impact of server failures Minimize data movement while growing the ring Determine Data security

24 Multi-Geo: Single, Mirrored & Stretched RING Single RING One RING, one datacenter Replication or ARC erasure coding (within RING) for higher durability Mirrored RING Multi-RING (2 or more) in one or multiple datacenters Store multiple copies in multiple rings for higher availability Mirrored Replication to EC possible Data Protection and Geo-Redundancy Stretched RING across multiple sites Active/Active - managed as a single RING Location aware allocation: both Replication and ARC can spread data across disparate domains for site failure tolerance Synchronous operations: best for lowerlatency WAN environment Scality RING Software Defined Storage Scality RING Software Defined Storage Scality RING Software Defined Storage Scality RING Software Defined Storage DC1 DC 2 DC 3

25 RING Management: Easy to use GUI & sophisticated CLI Management New improved GUI and CLI Easy integration with Puppet/Chef/SaltStack Integration with standard SNMP tools All statistics can be exported via HTTP

26 Scality RING Management UI Management

27 RING 5.0: Volume Provisioning through Supervisor UI Management Simplified SOFS Configuration & Provisioning Current SOFS Connector configuration is manual & requires knowledge of many parameters New Volume concept for SOFS connectors Supervisor UI enables easy selection of NFS, FUSE, CDMI and SMB (planned) connectors and configuration Fully automates the startup of the connectors ready to be accessed by applications!

28 Fast rebuilds with minimum performance impact START 0:16 1:30 3: Disk Failed Disk Repaired in only 16 mins 2100 Storage Server Failure Scality RING on six servers 1.8GB/s sustained with continuous I/O Megabytes per second Self-healing: Rebalance / Rebuild 60TB in only two hours Performance impact is limited to the offline server 1400

29 MESA a Distributed, ACID-Compliant Database Slide 29

30 RING Connectors: A wide choice of Native Object & File interfaces Connectors NFS sproxyd sfused RS2 SMB OpenStack Swift CDMI How do we recommend the optimal connector(s) for customers to use? File versus objects are usually an application driven choice Some partner applications do support both types Some customers are ready to migrate their application from files to objects due to growth, performance or sometimes a negative experience with legacy products File Object

31 RING Object and File Connectors Connectors Type Connector Strength Tradeoffs Object Sproxyd Stateless, lightweight, native REST API, highly scalable, support for geo-distributed deployments RS2 RS2 light CDMI S3 compatible REST API, with Buckets, authentication & object indexing support Subset of RS2 highly-scalable, supports geo-distributed deployments REST API namespace compatible with SOFS (NFS, SMB, FUSE) data File NFS NFS v3 compatible server, supports Kerberos, advisory-locking (NLM), and user/group quotas FUSE SMB Local Linux file system driver, great for application servers. Fast for big files: parallel IO to multiple back-end storage servers SMB 2.x and subset of SMB 3.x compliant server No container mechanism, no authentication Buckets cannot be geo-distributed, performance overhead for authentication & MD5 verification Eliminates the S3 bucket containers & authentication mechanism Containers may present a scaling or concurrency limitation Multiple concurrent readers OK, multiple writers serialize on single directories/files Requires driver to be installed on client / app server. Same concurrency behavior as NFS Runs on top of FUSE. Does not yet support SMB 3.0 multi-channel IO

32 Scality RING: Unified Storage Management for OpenStack RING provides single system to manage Simplified, autonomous management Self-healing Unifies OpenStack Swift, Cinder & Glance Eliminates multiple storage silos Consolidates 80% of OpenStack data storage In the future: Manila for shared files Scalable to petabytes and beyond Enables Cloud Economics Runs on your choice of hardware Organically scalable, no downtime, no forklift upgrades

33 The Next Step in Flexibility: IP Drives MetaData access Direct Data access (Object / File / Block) MDC Redundant Geo Metadata farms (available also at Kinetic sites) x86 servers or VM w. File SSD system Directories Small objects Cache Erasure coding and/or replication MetaData Ring Farm Data Center #0 Data Center #1 Data Center #2 Seagate Kinetic Pools

34 Scality File Connectors Connectors NFS, wide platform support NFS v3 is the commonly used and available version of the popular Network File System protocol originally developed by Sun Microsystems. Supports Linux, Mac, Microsoft Windows, Includes support for NFS quotas and NFS advisory locking within a single connector Authentication for NFS clients via the Kerberos mechanism Support for security server solutions such as Microsoft Active Directory (AD) NFS Multi-app FILE-BASED OBJECT-BASED VM-BASED Linear performance scaling Scality RING Software Defined Storage x86 servers Limitless infrastructure scaling

35 Scality File Connectors Connectors sfused, local file system with parallel IO capabilities FUSE is a POSIX compliant local file system supported across all major Linux distributions (CentOS, Ubuntu, Debian (L)) Typically deployed as local file system access on Linux app server Local file and range locking, performs parallel backend file I/O to the same file, to optimize access to very large files. Support for user and group quotas sfused Multi-app FILE-BASED OBJECT-BASED VM-BASED Linear performance scaling Scality RING Software Defined Storage x86 servers Limitless infrastructure scaling Slide 35

36 Scality File Connectors Connectors SMB Connector (RING 5.0) SMB 2.x and SMB 3.x compliant (MultiChannel IO planned in 2015) Support for basic Windows ACLs Runs on the FUSE connector (sfused) SMB Multi-app FILE-BASED OBJECT-BASED VM-BASED Linear performance scaling Scality RING Software Defined Storage x86 servers Limitless infrastructure scaling Slide 36

37 Scality Object Connectors Connectors CDMI, REST interface with file compatibility CDMI is an industry-standard REST protocol sponsored by the Storage Networking Industry Association (SNIA). Object REST API (PUT, GET, DELETE) based on the SNIA CDMI v1.0 specification Namespace compatible with Scality file system (SOFS) to enable object & file sharing CDMI Multi-app FILE-BASED OBJECT-BASED VM-BASED Linear performance scaling Scality RING Software Defined Storage x86 servers Limitless infrastructure scaling

38 Scality Object Connectors Connectors sproxyd, high-performance & scalability Pure object REST API with simple key/value semantics Designed to meet extreme scalability and performance requirements. Provides a single, scalable, flat namespace but no Container or Bucket concept Great fit for distributed (multi-site) deployments Application must therefore manage the following: Catalog of keys & metadata sproxyd Security (Authentication) Metering & reporting Multi-app FILE-BASED OBJECT-BASED VM-BASED Linear performance scaling Scality RING Software Defined Storage x86 servers Limitless infrastructure scaling

39 Scality Object Connectors Connectors RS2, public cloud compatibility Object REST API (PUT, GET, DELETE) based on AWS S3 designed mainly for public cloud deployments Mandatory MD5 signature on every operation (impacts performance) Includes Bucket concept with commands for Bucket operations Potential bucket list update contention has performance and deployment impacts Not idea for distributed, multi-site deployments RS2 light Subset of the RS2 REST API Eliminates use of buckets No authentication Higher-performance & more scalable Multi-app FILE-BASED RS2 OBJECT-BASED VM-BASED Linear performance scaling Scality RING Software Defined Storage x86 servers Limitless infrastructure scaling

40 Scality Object Connectors Connectors OpenStack Swift OpenStack Swift compatible API that uses Scality Sproxyd (REST API) to store object on Scality RING (by path method) Enables replication & erasure coded storage Highly scalable, high-performance storage Preserves Swift Functionality Account & Containers Keystone authentication OpenStack Swift Multi-app FILE-BASED OBJECT-BASED VM-BASED Linear performance scaling Scality RING Software Defined Storage x86 servers Limitless infrastructure scaling

41 Example Deployments

42 The Easiest Examples: Sensor Data vs. Simulation Data Sensor Data Data is captured through innovative sensors Output can be graphical (images, film) but also numerical: temperature, humidity, DNA sequences, SKA, etc. Sensor data is often processed in a truly parallel fashion, also called embarrassingly parallel Simulation Data Data is generated with computational devices Output is computational; typically many writers to 1 file Data computation requires very low latency and high random I/O loads Less clear use for object storage Copyright Scality 2015

43 Example: Medical Research Multi-petabyte system High value physical data Ultra hi-res images Multi-site Usage Adopted a Object based model Site A Site B

44 Examples : RAM Flush (Simulation) or Sensor Burst (Seismic & Particle Physics) PUT Key GET Range PUT Key Get Range PUT Key Get Range PUT Key Get Range PUT Key Get Range 1000s-10000s Writers Parallel data access to deliver high throughput 100s-1000s Storage Servers Offload ~ 1PB in less than 1 hour Global Namespace ONE Single View of Content Scality RING

45 Example: 2 nd Tier using Scality RING & Lustre Integration HPC Cluster Compute Lustre MDS s Home Directories Lustre OSS OST Sproxyd Lustre OSS Lustre OSS Lustre 2.5 Parallel FIlesystem Lustre 2.5 Copy Tool Lustre OSS OST OST OST Sproxyd Lustre OSS This is Scality recommended method for best performance results: Objects are stored using HTTP/REST interface with FID Scality OBJECT connectors run on the Storage servers Scality RING x86 servers Limitless infrastructure scaling SCALITY RING SOFTWARE RING Management! Security Replication! Erasure Coding! Geo-Redundancy Scality REST REST Block Driver API

46 Example : European Car Manufacturer A leading European Car manufacturer. For a video data analysis project, Cars Inc. uses a 5PB Scality platform. The system will hold 1 million km of cars video analysis for crash avoidance. Highest valued features: Granular and gradual scalability Hardware-agnostic flexibility to upgrade hardware in the future without impact on the business Scality s support for distributed & parallel computing Performance: the more data can be processed, the more safety improvements can be achieved

47 THANK YOU! Try it today