存储厂家EMC云计算存储解决方案 AtmosTechnicalOverview

1、1 copyright 2009 emc corporation. all rights reserved. emc atmos: technical overview emc 2 copyright 2009 emc corporation. all rights reserved. agenda atmos overview atmos offerings atmos hardware architectural overview of atmos operational efficiency access methods role of policies atmos online 3 c

2、opyright 2009 emc corporation. all rights reserved. transactionunstructuredcompliance distribution / content atmos (software) atmos (hardware) centera v-max clariion celerra san (storage area network) block nas (network-attached storage) file cas (content-addressable storage) immutable cos (cloud-op

3、timized storage) policy where does cloud fit? market leading storage solutions for all information and applications 4 copyright 2009 emc corporation. all rights reserved. atmos solution offerings bundled hardware and software solution larger footprints (up to 720 tb in one frame) ease of configurati

4、on software-only solution small footprints vmware install supports existing hardware deployment terminology atmos cloud: comprised of one to many locations each location is a “resource management group” (rmg) each rmg is comprised of one or more “installation segments” (is) an is equates to the priv

5、ate network connecting several atmos “nodes” rack two or more atmos vms on the same private subnet 5 copyright 2009 emc corporation. all rights reserved. atmos next generation hardware dense compute 1:15 server-to-drive ratio now up to 480 tb total capacity lower power / btu at 2x capacity small/med

6、ium scale compute 1:15 servers-to-disks 60 tb cloud entry point now up to 240 tb total capacity lower power / btu at 2x capacity ws2-120ws2-240ws2-360 capacity 1:60 server-to-drive ratio now up to 720 tb total capacity lower power / btu at 2x capacity new intel xeon 5500 “nehalem” microarchitecture

7、2 tb low power sata drives new 6 copyright 2009 emc corporation. all rights reserved. hardware design philosophy industry standard components standard data center environments factory configured, racked and cabled flexible, cost effective service model optional ha and redundancy user serviceable 30

8、drives per 3u drawer up to 720 tb per rack ws2-120, ws2-240 or ws2-360 configurations 7 copyright 2009 emc corporation. all rights reserved. ws2-360: dense scale capacity up to 720tb total capacity 1 or 2 tb drives 44 u “hulk” cabinet 1:60 server to drive ratio 6 servers / 24 bullet daes partial rac

9、k will be supported q2 4 -6 nodes, 2 node increment 1tb drive: 240, 360 tb 2tb drive: 480, 720 tb gbe connectivity 1 allied telesis gbe switch redundant power and cooling environmentals (1 tb) 82” height 24” width 43” depth 2548 lbs weight 10,290 w power 35,120 btu/hr 8 copyright 2009 emc corporatio

10、n. all rights reserved. ws2-240: dense scale compute up to 480tb total capacity 1 or 2 tb drives 44 u “hulk” cabinet 1:15 server to drive ratio 16 servers / 16 bullet daes partial rack will be supported q2 4 16 nodes, 2 node increment 1tb drive: 60, 90, 120, 180, 210, 240 tb 2tb drive: 120, 180, 240

11、, 300, 360, 420, 480 tb gbe connectivity 2 allied telesis gbe switches redundant power and cooling environmentals (1 tb) 82” height 24” width 43” depth 2282 lbs weight 10,020 w power 34,198 btu/hr 9 copyright 2009 emc corporation. all rights reserved. ws2-360 / ws2-240 serviceability and accessibili

12、ty patented expandable drawer provides full access to embedded components full rear access no special cooling requirements clean, rear-only cabling and automated cable management systems 10 copyright 2009 emc corporation. all rights reserved. ws2-120: small scale compute up to 240 tb total capacity

13、1 or 2 tb drives 40 u “titan” cabinet 1:15 server to drive ratio partial rack in q1: 4, 6, or 8 nodes 1tb: 60tb - 4 node, 90tb - 6 node, 120tb - 8 node 2tb: 120tb 4 node,180 tb 6 node, 240 tb 8 node gbe connectivity 1 allied telesis ip x9924 switch 2 pdus environmentals (1 tb) 70” height 24” width 4

14、0” depth 1,356 lbs weight 4,880 w power 16,655 btu/hr 11 copyright 2009 emc corporation. all rights reserved. additional cabinet power information cabinet type cabinet type drive type drive type total max capacity total max capacity max power max power max btu max btu tb / kw tb / kw ws2-120 1tb 720

15、0 120 tb 4,880 w 16,838 24.6 ws2-120 2tb 5400, low power 240 tb 3,945 w 13,464 60.8 ws2-2401tb 7200 240 tb 10,020 w 34,198 24.0 ws2-240 2tb 5400, low power 480 tb 7,890 w 26,929 60.8 ws2-360 1tb 7200 360 tb 10,290 w 35,120 35.0 ws2-360 2tb 5400, low power 720 tb 7,239 w 24,706 99.5 12 copyright 2009

16、 emc corporation. all rights reserved. soap/rest dns load balancer reference architecture access points cifs/nfs/ifs location 3 “tokyo” location 2 “london” location 1 “boston” access points tcp/iptcp/ip 13 copyright 2009 emc corporation. all rights reserved. policy management job service storage ser

17、vice atmos high-level architecture atmos native client access api metadata service applications restsoap apache httpd installable file system (ifs) system management metadata location service resource management service administration 1 - client access 2 - data5 - management4 - discovery3 - metadata

18、 atmos software collection of distributed services client access (1) data (2) metadata (3) discovery (4) management (5) rpc-xml like protocol x86 serversdense storagevmware esx atmos virtual edition / atmos hardware clients / management nfscifs 1 23 4 5 14 copyright 2009 emc corporation. all rights

19、reserved. reference architecture creating objects “london” application server farm dns load balancer application makes api call to create object load balances to “access node” meta data written “locally”. and synchronized policy manager makes 2 synchronous replicas “boston” object identifier returne

20、d to application 15 copyright 2009 emc corporation. all rights reserved. reference architecture reading objects “london” application server farm dns load balancer application makes read object call load balances to “access node” meta data server queried optimal object found data read from copy “bost

21、on” object data and meta data returned to application 16 copyright 2009 emc corporation. all rights reserved. atmos tenancy model foundation for cloud storage architecture conceptual grouping of resources hierarchical model enables flexible application integration platform to support millions of use

22、rs provides robust reporting and resource management improves operational efficiency manage access and resources per tenant/subtenant allows optimal policy definition and management helps manage node services 17 copyright 2009 emc corporation. all rights reserved. secure multi-tenancy access control

23、, auditing, separation multiple “customers” can share the same cloud isolation between sets of customers (at the tenant and sub-tenant level) maui tenant capabilities multiple tenants, each with a unique tenant id unique policies per tenant logical separation of all resources available note: servers

24、 are dedicated to one tenant examples of multiple tenants sharing a single atmos cloud customers (clients of an organization) business units (within the same organization) applications (cifs backups vs. rest access) geographic regions (e.g. australia, germany, united states) tenants can be divided i

25、nto sub-tenants by default, each tenant has a sub-tenant with the same tenant id 18 copyright 2009 emc corporation. all rights reserved. atmos tenancy model conceptual grouping of resources tenants, sub-tenants and users physical and network separation of tenants, logical separation of sub-tenants (

26、each have a unique system-wide id) unique policies per tenant separate admin management, user management and tenant-defined policies per sub-tenant supports thousands of customers, departments, applications or users in one cloud supports internal / external service providers supports tenancy across

27、many locations while providing a unified name space within the tenant supports optimal policy definition for different groups or applications, providing operational efficiency allows granular management of access and resources per tenant, subtenant and user provides robust reporting boston rmg node

28、1 node 2 node 3 node 4 node 5 node 6 node 7 node 8 london rmg node 1 node 2 node 3 node 4 node 5 node 6 node 7 node 8 tenant a tenant b cifs sub-tenant user n user 1 cifs users nfs usersnfs sub-tenant user n user 1 sub-tenant2 user n user 1 ws users ws userssub-tenant1 user n user 1 19 copyright 200

29、9 emc corporation. all rights reserved. atmos policy key feature of atmos cloud storage maps business requirements defined and managed per tenant sub-tenants inherit policies from tenants one default policy per tenant optimal and efficient storage management maps business objectives to replication a

30、nd location requirements increase operational efficiency set it and forget value added services are defined per policy data-path service data at rest service location attributes ss attributes expiration and retention initial design and implementation of policies is vital 20 copyright 2009 emc corpor

31、ation. all rights reserved. policy-based information management increasing operational efficiency audio transcriptsdigital images object metadata matches policies policies map to business objectives policies drive actions where to store information what content services to apply the number of copies

32、 gold: 2 synchronous copies boston 1 asynchronous copy seattle 1 asynchronous copy miami bronze:1 synchronous copy miami de-dupe, compression 1 asynchronous copy seattle availability= gold availability= bronze “.mov”, “image”, etc.“.mp3”, “audio”, etc. 21 copyright 2009 emc corporation. all rights r

33、eserved. custom metadata replicated by policy across your enterprise retained and archived to the cloud policy-driven management 22 copyright 2009 emc corporation. all rights reserved. additional data services compression reduction of physical space required for object storage de-duplication reducti

34、on of replicated identical objects spin-down “green”, power efficient method for long term storage fast / striping data striping within nodes or across nodes for higher throughput auto-configuration and auto-healing install once just add capacity node-level data services 23 copyright 2009 emc corpor

35、ation. all rights reserved. storage server attributes storage server attributes are set at install time defined per node they cannot be changed on the fly attributes must be defined on two levels data placement action type (transformations) pick one of each for node profile data placement action typ

36、e optimal green fast balanced none compression deduplication checksum compress+dedupe 24 copyright 2009 emc corporation. all rights reserved. fine tune your environment geoprotect dial the right performance and protection levels to your content two implementation methods to choose from implement bot

37、h to maximize content distribution efficiency and cost multiple copies across locations active content highly available replication (non-parity) longtail content retention decrease storage overhead survive multiple component failures erasure code (parity) 25 copyright 2009 emc corporation. all right

38、s reserved. managing storage at global scale a new approach 1 copy 2 copies n copies n by maintaining: susceptible to failures of the system, site, and network connectivity may not meet required performance because limits of device and or location of access improves resilience to failures of the sys

39、tem, site, and network connectivity potentially improves performance of remote access greatly improves resilience to failures of the system, site, and network connectivity greatly improves performance of remote access disperse copies address geographic performance and reliability 26 copyright 2009 e

40、mc corporation. all rights reserved. managing storage at global scale a new approach erasure codes: location specific content hardening increase content durability with less overhead higher fault tolerance (tolerates k faults) with less storage cost (n / m) availability measures if data stored on a

41、system can be returned promptly (i.e. no special action required to generate the data) durability measures if data stored in a system is not lost due to failures (i.e. data is available but special action may be needed) 27 copyright 2009 emc corporation. all rights reserved. erasure codes: at a glan

42、ce object written into m data segments and k coded segments determine where to store segments object can still be retrieved when k components are unavailable or fail cannot recreate the object without all required segments 28 copyright 2009 emc corporation. all rights reserved. atmos erasure code im

43、plementation objects are divided into m data fragments and k coding fragments supports two configurations 9/12 configuration = m=9,k=3 ( default) tolerates up-to three drive failures 33% storage overhead performance overhead is under review 10/16 configuration high fault tolerance (up-to 6 drive fai

44、lure) 60% storage overhead performance overhead is under review fragments are stored in independent fault domains 1.3 release has the ability to choose fault domains based on replication location configuration fragments can be distributed across rmg fragments can be distributed across the system 29

45、copyright 2009 emc corporation. all rights reserved. erasure code encode ( 9/12 configuration) encodewrite 9 fragments encoded fragments m=9 k=3 objects are divided into m=9 data fragments and k=3 coding fragments k=3 coding fragments are computed using cauchy reed-solomon code fragments are stored

46、in independent fault domains each fragment is stored on a different disk rmg or system level fault domain options overhead = k/(m) ex: =3/(9)=33% encode operations has overhead on cpu fragment level consistency and integrity checks 30 copyright 2009 emc corporation. all rights reserved. configuring

47、erasure codes click “erasure code” two additional fields appear algorithm: crs (cauchy reed-solomon) fragmentation: 9/12 or 10/16 31 copyright 2009 emc corporation. all rights reserved. policy layout replica options standard replicas single instance of the data per single drive erasure coded replica

48、s policy based striped replicas specify a number of storage servers to stripe across specify a striped depth federated replicas with an atmos online account configured a “federated” location is allowed 32 copyright 2009 emc corporation. all rights reserved. object recovery: drive failure benefits pr

49、ovides proactive object recovery in the event of a disk failure supports multiple drive failures does not require drive replacement recovery distributes objects within the same rmg alerts and gui provide information recovery start times objects impacted completion status 33 copyright 2009 emc corpor

50、ation. all rights reserved. disk failure alert 34 copyright 2009 emc corporation. all rights reserved. recovery process has begun 35 copyright 2009 emc corporation. all rights reserved. alert for impacted objects 36 copyright 2009 emc corporation. all rights reserved. recovery progress 37 copyright

51、2009 emc corporation. all rights reserved. flexible access methods web services access soap: simple object access protocol rest: representational state transfer file services access nfs: network file system cifs: common internet file system ifs: installable file system cifs nfs http cross platform (

52、via soap / rest) linux/unix (via nfs) windows (via cifs) linux w/fuse rpm (via ifs) ifs ws soap rest atmos native client api 38 copyright 2009 emc corporation. all rights reserved. overview installable (atmos) file system native atmos file system same global file system code and library as on atmos

53、nodes allows an external client act as the atmos client services that runs on an atmos node. ip-based communication requires fuse and rhel5 39 copyright 2009 emc corporation. all rights reserved. atmosfs rpm atmosfs, mauifs, ifs rhel5 support only 32 or 64 bit requires fuse 2.7.4 speaks native atmos

54、 atmosfs servers are part of the cloud atmos native file system mounted to a subtenant client mountpoint: /mnt/mauifs even though it is /mnt/mauifs/tid/sid multiple atmosfs clients may point to the same subtenant ifs is inherently clustered improves performance and parallelism atmos ports must be op

55、en can act as a gateway for nfs/cifs match ifs version to atmos version atmos native client access api installable file system (ifs) atmosfs rpm rhel5 server “boston” 40 copyright 2009 emc corporation. all rights reserved. application q1: pushing a file to atmos: fs client mdls mds rm ss ss ss ext3

56、ext3 ext3 mds pm rm linux os /mnt/mauifs maui client 1 1 1. file passed to maui mount point 2 2. client queries rm for mdls 4 4. create request issued to mds 5 5. policy queried for layout 6 lso 6. layout (lso) and oid returned to client 7 7. client writes data to selected resources proprietary prot

57、ocols 3 3. client queries mdls for mds that owns the parent directory 41 copyright 2009 emc corporation. all rights reserved. nfs and cifs access nfs or cifs configured per atmos node nfs service or smb service started layered on top of the atmosfs (ifs) that runs on each node no automatic failover

58、of access nodes atmos native client access api installable file system (ifs) nfscifs atmos access node unix clients windows clients 42 copyright 2009 emc corporation. all rights reserved. cifs configuration atmos exports cifs at node (tenant) level tenant or subtenant admin manages the shares regard

59、less of the access method, all objects are defined using global unique identifier (object id) all files are defined using a global, unique identifier translation from traditional namespace to the object id transparent sub-tenant shares ability to access cifs share if multi-subtenant access is enable

60、d leverage same authentication model that of tenants cifs user management is managed using ad integration atmos cifs share acl details directory and file level permission inheritance acl inheritance default permissions configuration ease of cifs share management and configuration multi-level admin c