• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
ATMOS ARCHITECTURE OVERVIEW
 

ATMOS ARCHITECTURE OVERVIEW

on

  • 4,926 views

ATMOS

ATMOS
ARCHITECTURE
OVERVIEW

Statistics

Views

Total Views
4,926
Views on SlideShare
4,744
Embed Views
182

Actions

Likes
3
Downloads
313
Comments
0

4 Embeds 182

http://www.panoptic.biz 155
http://panoptic.biz 18
http://localhost 8
http://panoptic 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    ATMOS ARCHITECTURE OVERVIEW ATMOS ARCHITECTURE OVERVIEW Presentation Transcript

    • ATMOS ARCHITECTURE OVERVIEW Mark O’Connell© Copyright 2011 EMC Corporation. All rights reserved. 1
    • Agenda •  Why Object Storage •  Architecture •  Data Management at Scale •  Multi-tenancy for management at scale© Copyright 2011 EMC Corporation. All rights reserved. 2
    • Trends in IT •  Companies, information, and services are global •  Growth of unstructured, digital information •  24x7, worldwide access to data •  Growth in data access points – laptops, mobiles, etc. •  Scale out architecture, grow with your data needs •  Huge worldwide networking infrastructural building blocks© Copyright 2011 EMC Corporation. All rights reserved. 3
    • EMC Atmos – Managing Big Data in the Cloud •  Purpose-built cloud storage platform •  Globally distributed •  Intelligent data management •  Web-scale© Copyright 2011 EMC Corporation. All rights reserved. 4
    • Typical Customer Usage Models Build and Manage Enterprise Cloud Storage global unstructured data •  Manage •  Protect data •  Reduce IT storage costs Make Existing Storage Cloud-Ready •  Utilize existing storage resources and hardware •  Atmos Cloud storage in virtual environment Provide Cloud Storage-as-a-service •  Service multiple consumers •  Provide secure multitenancy •  Meter and bill for usage Archive to the Cloud •  Isolate distributed archives •  Manage chargeback •  Ensure security and protect data© Copyright 2011 EMC Corporation. All rights reserved. 5
    • EMC Atmos Design Principles •  Massively scalable infrastructure –  Multiple petabytes; billions of objects –  Hundreds of sites, fully distributed –  Unified namespace •  Policy-based management –  Policy tells content where to go, what actions to take –  Integrated object based metadata –  Event driven policy evaluation© Copyright 2011 EMC Corporation. All rights reserved. 6
    • EMC Atmos Design Principles •  Data services and access methods –  Replication, GeoProtection, compression, de-duplication, spin-down –  Web Services (REST/SOAP) and file system access –  Full metering and billing infrastructure •  Management at scale –  Auto-config and auto-healing architecture –  Multi-tenancy –  Manage more with fewer people –  Partitioned management services allows sharing a common infrastructure amongst disparate users© Copyright 2011 EMC Corporation. All rights reserved. 7
    • Atmos High-Level Architecture REST WAN access Firewall REST Runs LAN access Server LAN access protocols on each node Atmos Native Client Access API Runs across Blob storage nodes© Copyright 2011 EMC Corporation. All rights reserved. 8
    • Atmos - Access Architecture NFS CIFS GeoDrive Browser Custom Apps REST Firewall WAN access NFS CIFS Atmos REST LAN access CAS Server Installable FilesystemCDP log Atmos Native Client Access APIcollection andprocessing Blob storage © Copyright 2011 EMC Corporation. All rights reserved. 9
    • Atmos – Storage Architecture Atmos Native Client Access API Write K46DJ…3X2 Track online storageReplicated, identifies an MDS resources Node 1 Node 2 MetaData Resource Location MDLS MDLS Management Service Service A-M N-Z Queues Metadata Metadata asynchronous Replicated Service Service replication requests Policy Management Policy Policy Job Management Management Service One per node Locally stores data Storage Storage Service Service No communication with other SSs© Copyright 2011 EMC Corporation. All rights reserved. 10
    • Atmos Storage Architecture •  MDS (MetaData Service) design is the key to scalable global storage •  Each MDS manages a slice of the object namespace –  3x replicated for HA and availability –  MDS unavailability only affects some objects •  MDS can use any available storage server –  Storage outages do not affect ability to store new data –  No impact for reads unless no stored copies are available •  Normal operation favors MDSs local to the client –  Reduces latency for most operations while maintaining global availability •  REST protocol for globally scalable access© Copyright 2011 EMC Corporation. All rights reserved. 11
    • Creating an Atmos System© Copyright 2011 EMC Corporation. All rights reserved. 12
    • Architecture Overview – Building Blocks•  Industry standard components –  Processor, memory, etc details•  Standard data center environments•  Factory configured, racked, and cabled•  Flexible, cost-effective service model•  User serviceable•  Up to 30 drives per 3U drawer•  Up to 720 TB per rack WS 120/240 WS 360 Compute Configuration Capacity Configuration•  120, 240, or 360 drive configurations •  1:15 Server-to-drive ratio •  1:60 Server-to-drive ratio •  120/240/480 TB capacity •  360/720 TB capacity •  GbE or 10GbE •  GbE or 10GbE connectivity connectivity© Copyright 2011 EMC Corporation. All rights reserved. 13
    • Architecture Overview – Virtual Building Block Ÿ  Identical software components REST clients IFS clients CAS clients and capabilities in a virtual (VMware ESX) environment  Interoperates with HW based RES LAN Protocols Atmos CAS T Atmos deployments IS1 IS2 RMG IS3 IS4 Ÿ  Extends any storage with a ESX Servers web services interface and Atmos RMG, 4 IS, 8 Nodes object storage FC/ NFS − Heterogeneous SAN, NAS, and Object access on a single platform − Enables scale out unified object storage across data centers or geographies© Copyright 2011 EMC Corporation. All rights reserved. 14
    • Forming a System from the Building Blocks •  Each physical or virtual building block is typically one RMG –  RMG = Resource Management Group, unit of geographic scaling –  LAN connected nodes, typically collocated –  One RMG can house multiple racks RMG 1 RMG 2 •  RMGs organize the nodes into (Boston) (London) distinct locations –  Used in policy placement of data IS1 IS2 RMG IS3 IS4 –  Resource availability tracked locally and ESX Server then communicated globally s •  Client requests localized via RMG •  Responses optimized to use resources local to the RMG RMG 3 RMG 4 (Raleigh) (Rome)© Copyright 2011 EMC Corporation. All rights reserved. 15
    • Atmos Data Storage© Copyright 2011 EMC Corporation. All rights reserved. 16
    • Atmos Object Creation and RMG Interactions 1)  REST request recv’d 2)  MDLS finds a Metadata Service (normally in local RMG), creates record 3)  Local data copy(s) stored, normally synchronous 4)  Asynchronous remote data copy(s) queued via Job Service 5)  Multiple remote asynchronous copies leverage RMG local resources 6)  A record is made of bandwidth and storage consumed 2 4 5 6 1 3 RMG 1 RMG 2 (Boston) (London)© Copyright 2011 EMC Corporation. All rights reserved. 17
    • Atmos Data Path – Data Placement How is it decided where the metadata and data are placed? •  User policies guide the placement decision •  Can be based on –  Initiating user RMG 1 RMG 2 (Boston) (London) –  Location of request –  User specified metadata IS1 IS2 RMG IS3 IS4 –  Or more ESX Server •  Policy specifies s –  Metadata location –  Data protection level –  Data protection location RMG 3 RMG 4 (Raleigh) (Rome)© Copyright 2011 EMC Corporation. All rights reserved. 18
    • Atmos Data Path – Policy Specification Policy specifications detail how an object is to be stored within the system Metadata is normally placed in the RMG which receives the create request Specify data storage options – N way mirroring, erasure encoding, location, sync vs async, etc.© Copyright 2011 EMC Corporation. All rights reserved. 19
    • Atmos Data Path – Policy Selector Policy selectors use criteria from the object to choose how the object will be stored. Specify the policy Specify how the decision is Specify if the policy specification, which made – user metadata value should be applied controls where the (s), system metadata, etc when objects are data is stored created or when they are updated© Copyright 2011 EMC Corporation. All rights reserved. 20
    • Accessing Data in Atmos© Copyright 2011 EMC Corporation. All rights reserved. 21
    • Atmos Read interactions with RMG and Policy 1)  REST read request recv’d 2)  MDLS uses Object ID to identify Metadata Service 3)  Metadata Service returns locations of all replicas 4)  Closest replica used to satisfy the read 5)  A record is made of the bandwidth consumed 2 3 4 5 1 1 5 3 3 4 RMG 1 RMG 2 (Boston) (London)© Copyright 2011 EMC Corporation. All rights reserved. 22
    • Decomposition of an Atmos object•  Blob –  The actual data bits of the object, protected according to policy•  System Metadata –  Standard information added automatically to the object –  E.g. time last modified, time created, size, name, storage policy, etc.•  ACL –  Security information about which UIDs may access this object –  May be freely changed by the object creator and others with access•  User Metadata –  Arbitrary information which can be associated with an object –  Can be used to drive policy decisions for the object –  Applications independent of the creator can add metadata •  Subject to object ACL permission –  Can be declared listable for easy object access© Copyright 2011 EMC Corporation. All rights reserved. 23
    • Accessing Your Data•  How can I identify the piece of data that I want? –  Use the object id •  May require an external database to manage the object ids –  Named objects (filesystem names) /home/finance/records/2011© Copyright 2011 EMC Corporation. All rights reserved. 24
    • Accessing Your Data Using Metadata•  Associate descriptive metadata with objects of interest•  Use listable metadata tags to quickly index similar items –  Walk the listable tag, possibly examining the object(s) to find the one of interest, e.g. •  Records from 2011 •  Records from blackjack table with dealer = “Mark O’Connell”© Copyright 2011 EMC Corporation. All rights reserved. 25
    • Accessing Your Data•  Atmos provides multiple object access schemes –  Object id •  Automatically assigned by the Atmos system •  Fastest mechanism to retrieve your data –  Named objects •  Optionally associate a name with a particular object •  Names are like pathnames (e.g. /mark/files/presentation.ppt) •  Supports directory list operations •  Additional overhead on R/W to translate name –  Listable tags •  Based on metadata in the object •  Quickly find a set of objects which share a certain property •  Useful for application specific index and search operations© Copyright 2011 EMC Corporation. All rights reserved. 26
    • Atmos Multi-tenancy© Copyright 2011 EMC Corporation. All rights reserved. 27
    • Architecture OverviewAtmos Tenancy Model•  Foundation for cloud storage architecture –  Conceptual grouping of resources –  Hierarchical model enables flexible application integration –  Platform to support millions of users –  Provides robust reporting and resource management•  Improves operational efficiency –  Manage access and resources per tenant/subtenant –  Allows optimal policy definition and management© Copyright 2011 EMC Corporation. All rights reserved. 28
    • Atmos Tenancy Model UIDs •  Represent an entity which Subtenants can connect to the blob •  Preconfigured storage system store and create/access •  A distinct object namespace objects •  Can be metered and billed •  Can be metered/billed •  Manages/creates application N+3 2x mirror connection credentialsTenants Tenant 1 Tenant 2 Tenant 3•  Dedicated network connections − Control of ingest bandwidth•  Controls storage usage (policies) − N+3, N+6, 2x mirror, etc•  Creates subtenants − Storage system + storage admin Blob storage© Copyright 2011 EMC Corporation. All rights reserved. 29
    • Atmos Tenancy Model - Data•  Tenants –  Tenancy is a logical compartmentalization of data and resources –  Tenants have their own access nodes, security control, storage policies, and access to the data •  Not aware of any other resources except for its own •  No access to other tenant’s resources –  All underlying resources shared among Tenants•  Subtenants –  Each Subtenant owns a distinct storage environment •  Users, objects and filesystem •  UserID needs to be unique only within a subtenant –  Each subtenant manages a disjoint set of data •  Stronger than an ACL, like a virtual storage machine –  Subtenant inherits policy specifications and selectors from the Tenant –  Subtenant may reorder policy specifications© Copyright 2011 EMC Corporation. All rights reserved. 30
    • Atmos Tenancy Model - Data•  Users –  Authenticates to store/retrieve/manipulate data in the cloud –  Per-user listable tags (metadata organization) –  May share files with other users in the same subtenant (via ACLs)© Copyright 2011 EMC Corporation. All rights reserved. 31
    • Atmos Tenancy Model - Management•  SysAdmin –  SysAdmin creates tenants –  SysAdmin assigns nodes to tenants –  SysAdmin manages the physical state of the system •  Upgrades, adding nodes to the system, etc –  SysAdmin has no data access, SysAdmin cannot create/alter policies•  Tenant admin –  Tenant admin creates policy specifications – how data will be stored in the system –  Tenant admin creates subtenants (virtual storage environment) and subtenant admins –  Tenant admin assigns policies to a subtenant© Copyright 2011 EMC Corporation. All rights reserved. 32
    • Atmos Tenancy Model - Management•  Subtenant admin –  Subtenant admin allows access to the storage environment (creates/deletes users) –  Subtenant may have a level of control over storage policies which are in effect •  If the tenant admin allows multiple policies to be used by a subtenant storage environment, then the subtenant admin has a level of control over how the policies are applied•  Users –  No management rights© Copyright 2011 EMC Corporation. All rights reserved. 33
    • Atmos Tenancy Model – PolicyApplication Subtenants and Engineering Finance IT Beta Research Assigned Policy Default policy Criticality Low, Default policy Size > 1MB, use normal use Silver Selectors Normal Test Default policy Criticality High, Payroll use Gold Silver Gold Storage Policy Normal Payroll Test 2 Sync copies 2 Sync EC 3 Sync EC copies 2 Sync copies 1 Sync copy 1 async copy copies India 1 async EC India© Copyright 2011 EMC Corporation. All rights reserved. 34
    • Atmos Management Strategy•  Atmos storage was designed to be customized to the needs of multiple individual environments –  Tenant and subtenant model –  Multiple individuals can have multiple custom environments on one storage system•  Atmos management was designed to be similarly customized•  Full REST/POX API available for management operations –  Allows customizable management flows •  Management interface could be different for each tenant admin or subtenant admin –  Authenticate as SysAdmin, TenantAdmin, or SubtenantAdmin –  Management API can also be used to fully automate Atmos system management© Copyright 2011 EMC Corporation. All rights reserved. 35
    • Default Atmos GUI•  Common operations available in the default GUI –  Logins available for SysAdmin, TenantAdmin, SubtenantAdmin –  Different screens and information shown based on login© Copyright 2011 EMC Corporation. All rights reserved. 36
    • Customizing the Atmos GUI – AtmosOnline •  Designed for a fully automated compute and storage service •  Customized workflow based on the Atmos system management APIs –  Allows automated onboarding of new customers, querying of billing information, etc •  Available at www.atmosonline.com© Copyright 2011 EMC Corporation. All rights reserved. 37
    • Atmos Architecture Summary•  A multi-site architecture for storing massive amounts of content•  Policy management allows control over data placement and protection•  Multi-tenancy for both data and management –  Allows customization of the storage for multiple, independent environments –  Allows a fine degree of logical separation of data –  Allows scoped management control for administrators© Copyright 2011 EMC Corporation. All rights reserved. 38
    • See Atmos in Action – Visit Booth 201 Theatre presentations every half hour Find Atmos-powered Storage-as-a- Service options available worldwide See how easy it is to integrate and customize Atmos via the open API and SDK Enter to Win Learn how Centera and Atmos work an iPad 2.0 together for compliance via the cloud Sneak peek at new features – like GeoDrive! Meet with experts, peers and customers© Copyright 2011 EMC Corporation. All rights reserved. 39
    • Additional Resources Atmos Web landing page http://www.emc.com/products/family/atmos.htm Video: Why Beth Israel Deaconess Chooses Atmos for Cloud Computing http://www.emc.com/collateral/demos/microsites/mediaplayer-video/beth-israel- deaconess-emc.htm IDC Analyst Paper, EMC Atmos: Making Rain in the Clouds http://info.emc.com/mk/get/SDL? reg_src=web&P.ctp_program_execution.Source_ID=AMA00018247 Analyst Report: ESG: EMC Atmos Cloud Storage Helps Vistaprint Cut Storage Infrastructure Costs and Accelerate Production http://www.emc.com/collateral/analyst-reports/esg-solution-impact-analysis-emc- vistaprint.pdf Sandbox: Atmos Online Developer Network https://community.emc.com/community/edn/atmos© Copyright 2011 EMC Corporation. All rights reserved. 40
    • © Copyright 2011 EMC Corporation. All rights reserved. 41
    • THANK YOU© Copyright 2011 EMC Corporation. All rights reserved. 42