Ism Module 7: Object-Based Storage

Front 1

How much of data generated is unstructured?

Back 1

90%

Front 2

Cons of NAS

Back 2

- Cannot scale to the capacities required

- Provide universal access across geographically dispersed locations

- More management as it scales

- Limited in Size

Front 3

Object-based Storage Device

Back 3

Stores data in the form of objects on flat address space based on its content and attributes rather than the name and location.

Front 4

What is a object?

Back 4

The fundamental unit of object-based storage that contains user data, related metadata (size date, ownership, etc.), and user defined attributes of data.

Front 5

Object ID

Back 5

Each object stored in the object-based storage system is identified by a unique identifier.

Easy access to objects without the need to specify the storage location.

Front 6

Hierarchical File System

Back 6

Organizes data in the form of files/directories

Limits the number of files that can be stored

Front 7

Flat Address Space

Back 7

How OSD Stores

The object exists at the same level and one object cannot be placed inside another object.

NO hierarchy

Scale-out storage requirement of third platform

Front 8

Three key components of an OSD System

Back 8

OSD nodes (Controller)

Internal network

Storage

Front 9

Metadata Service

Back 9

Responsible for generating the object ID from the contents (may also include other attributes of data) of a file.

- mapping of the object IDs and the file system namespace.

Front 10

Storage service

Back 10

Manages a set of disk on which the user data is stored

Front 11

OSD

Back 11

Uses low-cost and high density disk drives to store the objects.

Front 12

Scale-out architecture

Back 12

Provides linear scalability where nodes are independently added to the cluster to scale massively

Front 13

Multi-tenancy

Back 13

Enables multiple applications/clients to be served from the same infrastructure

Front 14

Metadata-driven policy

Back 14

Intelligently drive data placement, protection, and data services based on the service requirements.

Front 15

Global namespace

Back 15

Abstracts storage from the application and provides a common view- independent of location and making scaling seamless.

Front 16

Flexible data access method

Back 16

Supports REST/SOAP APIs for web/mobile access, and file sharing protocols (CIFS and NFS) for file service access

Some OSD storage systems support HDFS interface for big data analytics.

Front 17

Automated system management

Back 17

Provides auto-configuring, auto-healing capabilities to reduce administrative complexity and downtown.

No single point failure

Front 18

Data protection- geo distribution

Back 18

Object is protected using either replication or erasure coding technique and the copies are distributed across different locations.

Front 19

Erasure Coding
`

Back 19

Parity

Provides space-optimal data redundancy to protect data loss against multiple drive failure

A set of n disks is divided into m disks to hold data and k disks to hold coding information.

Front 20

Software-based Object Storage

Back 20

Object storage software is installed on any compatible hardware (compute system)

- Provides the flexibility to reuse the existing infrastructure (compute and storage) and to use commodity hardware

Object-based software can also be installed on virtual machines

Front 21

Hardware-based object storage

Back 21

- Both software and purpose-built hardware are provided by vendor

-Typically pre-configured and pre-tested

-Provides better performance

Front 22

Process of Storing Object in OSD

Back 22

1. Application server presents the data to be stored to the OSD node.

2. The OSD node divides the data into two parts: user data and metadata.

3. The OSD node generates the object ID using a specialized algorithm. The algorithm is executed against the contents of the user data to derive an ID unique to this data.

4. For future access, the OSD node stores the metadata service.

5. The OSD node stores the user data (objects) in the storage device using the storage service.

6. An acknowledgment is sent to the application server stating that the object is store. Sometimes, the Object ID is returned back to the application server.

Front 23

Process of Retrieving Object from OSD System

Back 23

1. The application server sends a read request to the OSD system.

2. The metadata service retrieves the object IF for the requested data.

3. The metadata service sends the object ID to the application server.

4. The application server sends the object ID to the OSD storage service for object retrieval.

5. The OSD storage service retrieves the object from the storage device.

6. The OSD storage service sends the data to the application server.

Front 24

Capabilities and features of OSD

Back 24

Multi-tenancy, scalability, geographical distribution of data, and data sharing across heterogenous platforms or tenants while ensuring integrity of data

This is why it is a strong option for Cloud Based Storage

Front 25

Cloud Storage Offerings

Back 25

Better agility, on-demand scalability, lower cost, and operational efficiency compared to traditional storage solution.

Front 26

Cloud Service Providers Lever OSD to offer

Back 26

Storage-as-a-service

Backup-as-a-service

Archive-as-a-service

Front 27

Gateways provider a translation later between

Back 27

The standard interfaces {iSCSI, FC, NFS, CIFS} and cloud provider's REST API

Front 28

Unified Storage

Back 28

A single integrated (converged) storage infrastructure that consolidates block (iSCSI, FC, FCoE), file, (CIFS, NFS), and object (REST, SOAP) access.

Ideal solution would be to have an integrated storage solution that supports block, file and object access.

Front 29

Unified Storage Benefits

Back 29

- Creates a single pool of resources that can be managed with a single management interface.

- Sharing of pooled storage capacity for multiple business workloads should lead to a lower overall system cost and administrative time, thus reducing the total cost of ownership (TCO)

- Provides the capability to plant he overall storage capacity consumption. Deploying a unified storage system takes away the guess work associated with planning for file and block storage capacity separately.

- Increase utilization, with no stranded capacity. Unified storage eliminates the capacity utilization penalty associated with planning for block and file storage support separately.

- Provides the capability to integrate with software-defined storage environment to provide next generation storage solutions for mobile cloud, big data, and social computing needs.

Front 30

Unified Storage Architecture

Back 30

Enables the creation of common storage pool that can be shared across a diverse set of applications with a common set of management processes.

Front 31

Key Component of a unified storage architecture

Back 31

unified controller- provides the functionalities of block storage, file storage, and object storage.

Front 32

Block-level US Access

Back 32

The controller configures LUNs and presents them to application servers and the LUNS presented to the application server appear as local disks.

A file system is configured on these LUNs at the server and is made available to applications for storing data.

Front 33

Atmos

Back 33

- Scale-out object-based cloud storage platform, stores data as objects

Front 34

Key Atmos Cloud features

Back 34

- global namespace

- REST API-driven storage

- multi-tenancy and self-service

-metering and chargeback

Front 35

ECS Appliance

Back 35

-Hyper-scale storage infrastructure

-Provides universal accessibility with support for object and HDFS

-Provides a single platform for all web, mobile, Big Data, and social media applications

Front 36

VNX

Back 36

- Family of unified storage platform

- Consolidates block, file, and object access

- Built for 5MBs and enterprises

- Ideally suited for applications with predictable workloads.

Front 37

VMAX3

Back 37

- Family of high-end enterprise storage platforms for hybrid cloud

-Provides embedded file data services (eNAS)

- Built around a scalable Dynamic Virtual Matrix architecture to support the storage growth

Front 38

Cloud Array

Back 38

-Cloud storage gateway solution

- Integrates existing applications with cloud using SAN and NAS interfaces

- On-site, dynamic cache maintains local performance

- Multi-layer encryption and local key management guard against unauthorized access