Published on

Published in: Technology, Business
1 Comment
1 Like
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Cloud computing may futuristic but it is nothing more than a way to pull together proven technologies, including virtualization, SOA, and service management. (Note: Don’t need all three but cloud is most powerful at the intersection where all three technologies converge.) The central ideas of the Cloud Computing model: 1. Abstraction maximizes the benefit of skills and expertise. It decouples the user from operational details, allowing them to focus on high-value work 2. Virtualization allows the complex IT environment to be managed as one single large resource providing services 3. Dynamically allocation provisions, configures, reconfigures, and de-provisions IT capability as and when needed, transparently and seamlessly That’s the big picture for cloud. Tie back to the three examples outlined earlier. Celerity (speed) and reliability is achieved through standardization, where commonly used configurations are stored in a catalog, ready for automatic deployment, reducing downtime and error rate flexibility is achieved through virtualization, smart resource sharing and allocation. It anticipates needs and uses the most appropriate resource to address the need, With complete control over the environment, it can pool resources together and react to unexpected demand. efficiency is achieved through better automation, standardization, and prioritization, minimizing processing time and matching the best resources with the most important and difficult tasks Transition line : Let’s look at the impact of cloud in a real-life scenario.
  • Also: According to Gartner , "Worldwide total software revenue for software as a service (SaaS) within the enterprise software markets is projected to surpass $5.1 billion in 2007 , a 21 percent increase from 2006 revenue. The market is poised for strong growth through 2011, when worldwide revenue will reach $11.5 billion." – M2 Presswire – September 2007 Gartner says that 25% of the whole enterprise software industry, will be software as a service by 2012 and that’s right around the corner. Despite the current economic downturn, the software industry is poised for growth in 2008, with worldwide enterprise software revenue totaling $190.7 billion in 2008, an 8.2 percent increase from 2007 revenue of $176.3 billion, according to Gartner, Inc. – Business Wire, February 2008
  • Consulting methodogies – business SOA – for technology What does it yield – and what is the impact (Give an example – self service provisioning) At IBM, we have been working on a maturity model and process for achieving desirable stages of maturity, a model called the Service Integration Maturity Model (SIMM). The level of de-coupling and amount of flexibility achievable at each stage of maturity are what make up the following seven levels of maturity: Silo (data integration) Integrated (application integration) Componentized (functional integration) Simple services (process integration) Composite services (supply-chain integration) Virtualized services ( virtual infrastructure) Dynamically reconfigurable services (eco-system integration) Each level has a detailed set of characteristics and criteria for assessment, and what follows is a brief description of the highlights of each level: Silo : The organization starts from proprietary and quite ad-hoc integration, rendering the architecture brittle in the face of change. Integrated : The organization moves toward some form of EAI (Enterprise Application Integration), albeit with proprietary connections and integration points. The approaches it uses are tailored to use legacy systems and attempt to dissect and re-factor through data integration. Componentized : At this level, the organization componentizes and modularizes major or critical parts of its application portfolio. It uses legacy transformation and renovation methods to re-factor legacy J2EE or .NET-based systems with clear component boundaries and scope, exposing functionality in a more modular fashion. The integration between components is through their interfaces and the contracts between them. Services : The organization embarks on the early phases of SOA by defining and exposing services for consumption internally or externally for business partners -- not quite on a large scale -- but it acts as a service provider, nonetheless. Composite Services : Now the organization extends its influence into the value chain and into the service eco-system. Services form a contract among suppliers, consumers, and brokers who can build their own eco-system for on-demand interaction. Virtualized Services : The organization now creates a virtualized infrastructure to run applications. It achieves this level after decoupling the application, its servcies, components, and flows. Now the infrastructure is more finely tuned, and the notions of the grid and the grid service render it more agile. It externalizes its monitoring, management, and events (common event infrastructure). Dynamically Reconfigurable Services : The organization now has a dynamically re-configurable software architecture. It can compose services at run-time using externalized policy descriptions, management, and monitoring. The business domain looks primarily at three things: the maturity of the business architecture, the relationship between business and IT and the business value achieved by moving to a service-oriented paradigm. We assess the business architecture and IT support of service orientation with the goal of improved reuse and flexibility, reduced complexity and time-to-market and in both business architecture and IT solutions. The organization domain looks at the maturity of the enterprise and/or business units in the context of organization structure, processes, mechanisms, learning and knowledge enablement, and governance in support of service orientation. This includes the ability to deliver on changing business requirements. The method domain looks at the maturity of the enterprise and or business units in their use of specific software (system) development method and process to support the SOA life-cycle and methods. This includes project management and project estimation considerations for the development of services, components and flows for the SOA life-cycle. The application domain looks at the maturity of the application portfolio to leverage service orientation. It focuses on the use of services for sharing and reuse of business functionality across business units and the ability to flexibly interchanging functionality to meet changing business needs. The architecture domain looks at the maturity of various levels of the architecture including, the enterprise and application architecture to support service orientation. The information domain looks at the maturity of the information and data architecture and management to support service orientation. It includes the notions of information as a service and the ability to apply best practices such as MDM and appropriate application of best practices such as Data Cleansing and Migration. The infrastructure domain looks at the maturity of the infrastructure, monitoring and management in areas of service monitoring and management, service security, and service virtualization. Designing the infrastructure to support the non-functional and operational requirements and service-level agreements needed to operate in a specific scope of the service eco-system.
  • Massive number of services To massive number of users With quality of service
  • WebSphere VE : WebSphere Virtual Enterprise provides application infrastructure virtualization capabilities that dynamically deliver application server resources where they are needed most. The software separates applications and services from the underlying infrastructure. Workloads can then be dynamically placed and migrated across a pool of application server resources allowing the infrastructure to automatically adapt and respond to business needs. Requests are then prioritized and routed to respond to the most critical applications and users.
  • Download

    1. 1. Storage for Cloud Computing Clod Barrera – STG Systems Storage January 20, 2009
    2. 2. Agenda <ul><li>What and why is Cloud Computing? </li></ul><ul><li>Cloud Computing and Storage </li></ul><ul><li>Ensembles as Cloud and Enterprise Infrastructure </li></ul><ul><li>Storage Ensembles </li></ul>
    3. 3. Cloud Computing <ul><li>Notes: </li></ul><ul><li>Abstraction – alleviates IT consumers from the operations of applications, allowing end users to focus instead on the execution and high-value activities </li></ul><ul><li>Virtualization – access to business services on-demand independent of location and resource constraints </li></ul><ul><li>Dynamic allocation – dynamically provisions, configures, reconfigures, and de-provisions IT capability as and when needed, transparently and seamlessly </li></ul>Speed and reliability through standardization, higher level of automation, and abstraction Flexibility through virtualization, dynamic resource sharing, and proactive capacity allocation Efficiency through higher level of automation, catalog standardization, and prioritization Abstraction Current Environment SOA Service Mgmt <ul><li>Emerging model where users can have access to applications or compute resources from anywhere through their connected devices through a simplified UI </li></ul><ul><li>Applications reside in massively-scalable data centers where compute resources can be dynamically provisioned and shared to achieve significant economies of scale </li></ul><ul><li>A strong service management platform results in only marginal incremental management cost, if any, when more workload needs to be handled by the cloud </li></ul>Virtual- ization Information Virtualization Elasticity Work Mobility
    4. 4. Key Attributes of Cloud Computing <ul><ul><li>Simple “self service” user interface </li></ul></ul><ul><ul><li>where underlying technology and </li></ul></ul><ul><ul><li>services are irrelevant to the user. </li></ul></ul>*A Service Management platform allows an operations management team to collect or discover information about how the resources associated with a service are configured and consumed and then access that information to support integrated management processes that address changes to and problems with the service. <ul><ul><li>When adding IT resources to </li></ul></ul><ul><ul><li>the service, the incremental </li></ul></ul><ul><ul><li>cost to manage these new </li></ul></ul><ul><ul><li>resources approaches zero </li></ul></ul>Provides for an infinitely scalable pool of connected computing resources Although often associated with Internet Services, clouds will exist both inside a data center to support that customers & internal users as well as supporting third-party managed service offerings. Efficient, green, and cost effective infrastructure
    5. 5. <ul><li>AaaS - Architecture as a Service </li></ul><ul><li>BaaS - Business as a Service </li></ul><ul><li>CaaS - Computing as a Service </li></ul><ul><li>CRMaaS - CRM as a Service </li></ul><ul><li>DaaS - Data as a Service </li></ul><ul><li>DBaaS - Database as a Service </li></ul><ul><li>EaaS - Ethernet as a Service </li></ul><ul><li>FaaS - Frameworks as a Service </li></ul><ul><li>GaaS - Globalization or Governance as a Service </li></ul><ul><li>HaaS - Hardware as a Service </li></ul><ul><li>IaaS - Infrastructure or Integration as a Service </li></ul><ul><li>IDaaS - Identity as a Service </li></ul><ul><li>LaaS - Lending as a Service </li></ul><ul><li>MaaS - Mashups as a Service </li></ul><ul><li>OaaS - Organization or Operations as a Service </li></ul><ul><li>SaaS - Software as a Service </li></ul><ul><li>StaaS - Storage as a Service </li></ul><ul><li>PaaS - Platform as a Service </li></ul><ul><li>TaaS - Technology or Testing as a Service </li></ul><ul><li>VaaS - Voice as a Service </li></ul>A variety of ‘as-a-Service’ terms have been used to describe the services offered in Clouds:
    6. 6. Who’s Offering Cloud Services today? 3Tera Grid-based Platform For Cloud Apps Akamai Application Performance Services Amazon Web Services AretiInternet Virtual Hosting Bungee Labs Virtual Labs-as-a-Service software CohesiveFT Cloud Platform Elastra Hosted Elastic Computing EMC Storage Cloud – Decho(Mozy, Pi) + Cloud Infrastructure & Services Division Enki Computing Utility Flexiscale Utility Computing on Demand Fortress ITX DynamicGrid Google Search Services HP Adaptive Infrastructure as a Service iCloud Desktop Cloud IBM Computing Cloud, Advanced UIs, Deep Capacity on Demand Joyent Accelerator for Applications Layered Technology GridLayer Microsoft CRM, email and IM Services Mosso Hosting Cloud Terremark Infinistructure XCalibre FlexiScale
    7. 7. Cloud Computing Users and Business Models <ul><li>Main actors and their interaction mode in the use and delivery of Cloud Services, enable the identification of the models and evolving technologies that support the Cloud Computing strategy: </li></ul><ul><li>Acquisition Model (Service): &quot;All that matters is results; I don't care how it's done&quot; </li></ul><ul><li>Business Model (Pay for usage): &quot;I don't want to own assets - I want to pay for elastic usage, like a utility&quot; </li></ul><ul><li>Access Model (Internet): &quot;I want accessibility from anywhere, from any device&quot; </li></ul><ul><li>Technical Model (Scalable, elastic, shareable): &quot;It's about economies of scale, with effective and dynamic sharing&quot; </li></ul>Garter, 2008 Service Consumers Service Catalog, Component Library Cloud Administrator Datacenter Infrastructure Monitor & Manage Services & Resources Component Vendors / Software Publishers Publish & Update Components, Service Templates Access Services IT Cloud
    8. 8. Cloud Computing: A New Paradigm Enterprise Cloud Network Cloud INNOVATIVE BUSINESS MODELS End Users / Requestors Government/ Academics Industry (Startups/ SMB/ Enterprise) Consumers <ul><li>An “Elastic” pool of high performance virtualized compute resources </li></ul><ul><li>Cloud applications enable the simplification of complex services </li></ul><ul><li>A cloud computing platform combines modular components on a service oriented architecture </li></ul><ul><li>New combinations of services to form differentiating value propositions at lower costs in shorter time </li></ul><ul><li>Internet protocol based convergence of networks and devices </li></ul>SIMPLIFIED SERVICES Source: Corporate Strategy
    9. 9. Cloud computing perceived benefits and demand drivers <ul><li>Awareness and demand for cloud computing are fueled by perceived / potential benefits to business entities , individual users , and IT providers (includes enterprises + service providers) </li></ul>Cloud computing’s “nirvana-like” promise drives higher service level expectations among business entities and individual users Which in turn puts pressure on the enterprise data center to deliver higher service quality (at lower cost) <ul><li>IT Providers </li></ul><ul><li>Key Benefit: </li></ul><ul><li>Competitivenes </li></ul><ul><li>Lower TCO </li></ul><ul><li>Faster Time to Market </li></ul><ul><li>Higher Cust Rentention </li></ul><ul><li>Service quality </li></ul><ul><li>Resource optimization </li></ul><ul><li>Resiliency </li></ul><ul><li>Flexibility </li></ul><ul><li>Efficiency </li></ul><ul><li>“ Green” </li></ul><ul><li>Enhanced chargeback </li></ul><ul><li>Business Entities </li></ul><ul><li>Key Benefit: </li></ul><ul><li>Innovation </li></ul><ul><li>Faster, easier innovation </li></ul><ul><li>New business models </li></ul><ul><li>New products and services </li></ul><ul><li>Faster time to market </li></ul><ul><li>Lower IT cost </li></ul><ul><li>Lower IT risk (brand protection) </li></ul><ul><li>Improved IT user productivity </li></ul><ul><li>Improved Client Satisfaction </li></ul><ul><li>Improved Disaster Recovery </li></ul><ul><li>IT Users </li></ul><ul><li>Key Benefit: </li></ul><ul><li>Quality of Experience </li></ul><ul><li>Speed of access </li></ul><ul><li>Ease of access (anywhere, anytime) </li></ul><ul><li>Ease of use </li></ul><ul><li>Minimal software requirements on access device </li></ul><ul><li>No long-term commitments </li></ul>
    10. 10. Model for Delivering Cloud Services (single provider) Fulfillment Services <ul><li>End Users make requests using a catalog of services </li></ul><ul><li>The Provider delivers service using fulfillment processes and technology </li></ul><ul><li>Services are normalized to achieve Abstraction and Encapsulation </li></ul>Fulfillment Process Fulfillment + Enterprise Process (e.g. Open Account) Fulfillment + Enterprise Process + Governance (e.g. ITIL) Provisioning Services Usage & Accounting Services Monitoring Services Security Services Energy Management Services Technology … . End User Requestors & Operators … Service Requestor Service Catalog Request UI Operational UI Service Provider Service Creator Federated Data Repository Service Definition Tools Service Publishing Tools Service Fulfillment & Configuration Tools UI, Fulfillment, Data, MetaData Service Monitoring Tools KPIs Service Planning
    11. 11. August 24, 2008 Architectural Model for Cloud Computing End User Requests & Operators … Service Request & Operations Design & Build Image Library (Store) Deployment Operational Lifecycle of Images IT Infrastructure & Application Provider Service Creation & Deployment Virtual Image Management Service Catalog Request UI Operational UI Standards Based Interfaces Virtualized Infrastructure Service Management Service Oriented Architecture Information Architecture Standards Based Interfaces Service Catalog, Component Library Datacenter Infrastructure Cloud Administrator Access Services Optimized Middleware (image deployment, integrated security, workload mgmt., high-availability) Service Oriented Architecture Information Architecture User Request Management/Self Service Portal Security: Identity , Access, Integrity, Isolation, Audit & Compliance Usage Accounting License Management Image Lifecycle Management Provisioning Performance Management Availability/Backup/ Restore Service Lifecycle Management Service Management Virtual Resources & Aggregations SMP Servers Network Hardware Storage Servers System Resources Blades Storage Virtualized Infrastructure Server Virt. Storage Virt. Network Virt.
    12. 12. The Role of Storage in Clouds - 1 Deep Infrastructure (What cloud?) Service Management SOA Application Middleware Virtualized Infrastructure Server / Storage / Network Virtual Image Management Cloud Service User <ul><li>The ‘Cloud Service’ is an application or upper layer function, or a platform service </li></ul><ul><ul><li>e.g., hosted computing </li></ul></ul><ul><ul><li>“ Application computing” is done by the Cloud Service and is co-located with the storage </li></ul></ul><ul><li>Incremental cost and time to add a new user is effectively zero </li></ul><ul><li>Desired Storage Infrastructure is the same as advanced Enterprise Storage (only cheaper) </li></ul><ul><ul><li>Integrated server & storage management </li></ul></ul><ul><ul><li>Automated provisioning </li></ul></ul><ul><ul><li>Performance & security controls </li></ul></ul><ul><ul><li>Chargeback </li></ul></ul><ul><ul><li>TCO challenges </li></ul></ul><ul><li>Value of the Cloud Service </li></ul><ul><ul><li>Complete application stack offload </li></ul></ul>Compute Requires some new/better storage function
    13. 13. The Role of Storage in Clouds - 2 Storage Application As a Cloud Service Service Management SOA Storage Application Storage Optimized Infrastructure Virtual Image Management Cloud Service User <ul><li>The ‘Cloud Service’ is a Storage Intensive application or upper layer function </li></ul><ul><ul><li>e.g. Medical Image Archive </li></ul></ul><ul><ul><li>Backup/DR for SMB </li></ul></ul><ul><ul><li>Data Warehousing </li></ul></ul><ul><ul><li>Content serving </li></ul></ul><ul><ul><li>Client could be an individual or a server farm </li></ul></ul><ul><li>Desired Storage Infrastructure is an optimized Storage Application </li></ul><ul><ul><li>Archive + Indexing + Search, long term retention </li></ul></ul><ul><ul><li>Video/large object access </li></ul></ul><ul><li>Local compute limited to: </li></ul><ul><ul><li>Ingest and playback </li></ul></ul><ul><ul><li>Optimization, management </li></ul></ul><ul><li>Value in the Cloud Service </li></ul><ul><ul><li>Multi-tenancy </li></ul></ul><ul><ul><li>Content </li></ul></ul><ul><ul><li>Specialty storage application </li></ul></ul>Compute Compute Requires some new/better storage function Requires specialty storage/function
    14. 14. The Role of Storage in Clouds - 3 ‘ Storage in the Cloud’ (like the old SSPs) Service Management SOA Storage Application – Device emulation Storage Optimized Infrastructure Virtual Image Management Cloud Service User <ul><li>Storage devices are seen as local, deployed across the cloud </li></ul><ul><ul><li>E: drive on laptop/desktops – Amazon S3 </li></ul></ul><ul><ul><li>‘ Capacity on Demand’ for server farms </li></ul></ul><ul><li>Desired Storage Infrastructure is a very low cost ‘Network Virtual Disk’ facility </li></ul><ul><ul><li>Upsell services? </li></ul></ul><ul><ul><ul><li>Archive + Indexing + Search, long term retention </li></ul></ul></ul><ul><li>Local compute limited to: </li></ul><ul><ul><li>Ingest and playback </li></ul></ul><ul><ul><li>Optimization, management </li></ul></ul><ul><li>Value in the Cloud Service </li></ul><ul><ul><li>Convenience, cost </li></ul></ul><ul><ul><li>Capacity on demand </li></ul></ul><ul><li>Challenges </li></ul><ul><ul><li>Multi-tenancy </li></ul></ul><ul><ul><li>Cost </li></ul></ul><ul><ul><li>Performance </li></ul></ul><ul><ul><li>Application Synergy </li></ul></ul>Compute Compute
    15. 15. Making Cloud Computing a Reality requires: Virtualization Integrated virtualization and management with optimized systems and networks to break the lock between IT resources and business services Autonomic Management Autonomic management methods for both application and infrastructure services to meet user needs and expectations for delivery of high quality of service Ensembles Simplified IT infrastructure, reduced complexity and management through the creation of large, consistent pools of resources that are managed as one. Software Services Hardware
    16. 16. Methods for IT Simplification Service oriented architecture technologies frame business processes as services, ease of deployment, composition, reuse, change… Topologies of federated services must be mapped onto large numbers of diverse physical and virtual resources Business Processes as Services Heterogeneous servers, storage, networks “ Enterprises report that IT operational overhead = 70% of their IT budget and growing . . . leaving precious few resources for new initiatives.” – Forrester, 2007 OLD Virtual Resource Objects/Appliances, Libraries will reduce the labor required for software stack development and management Ensemble Ensemble Ensemble Ensembles, scalable pools of like systems that are manageable as single systems will replace multitudes of individual servers and reduce the labor required for physical systems management Service management software spans the diversity of heterogeneous physical and virtual resources, providing unified cross-platform management in support of SOA NEW
    17. 17. Ensemble Components <ul><li>An Ensemble generally consists of the following components: </li></ul><ul><ul><li>A pool of compatible system nodes (e.g., N physical servers; need not be homogeneous) </li></ul></ul><ul><ul><li>Virtual resource mobility within an ensemble and with compatible ensembles </li></ul></ul><ul><ul><li>The networks which interconnect the ensemble nodes (may be local / optimized) </li></ul></ul><ul><ul><li>Resource virtualizers (hypervisors, I/O virtualizers, storage virtualizers, …) </li></ul></ul><ul><ul><li>An ensemble manager appliance that provides platform management for the ensemble virtual and physical resources </li></ul></ul><ul><ul><li>Tools for planning, ensemble creation, P2V migration, image mgmt. & composition, … </li></ul></ul><ul><ul><li>Ensemble-local automated optimization software of performance, availability, energy usage, security, … with intelligent defaults </li></ul></ul><ul><ul><li>Multi-system services (locking, caching, message queuing, …) may be integrated with some ensembles </li></ul></ul>Ensemble definition: a pool of like systems that is manageable as a single system OS OS OS Hypervisor Server OS OS OS Hypervisor Server Workload Mobility Server Ensemble Example Ensemble Manager
    18. 18. Ensembles – Building blocks for the New Enterprise Data Center and Clouds Ensembles Server Ensemble Ensemble Manager Virtualization Network Ensemble Ensemble Manager Virtualization Storage Ensemble Ensemble Manager Virtualization Storage Instantiate Virtual System Collections by allocating or assigning resources, configuring the resources as required, and managing the resources in the context of the goals & constraints provided. SEP
    19. 19. Accessing and Exploiting Ensembles Service Management Center Service Request Manager Catalog of Available Services Policies, Parameters, Options Specific Subscriber Cloud Instance Secure & Provision Resources Monitoring Subscriber Cloud Service Request Ensembles Server Ensemble Ensemble Manager Virtualization Network Ensemble Ensemble Manager Virtualization Storage Ensemble Ensemble Manager Virtualization SEP Storage
    20. 20. The Benefits of Ensembles <ul><li>Ensembles will significantly reduce IT resource management complexity and cost, and improve IT functionality, in consumable data center increments </li></ul>Individual Servers Server Ensemble OS OS OS Hypervisor Server OS OS OS Hypervisor Server Workload Mobility OS OS OS Hypervisor Server Ensemble Manager Built-in optimizations; intelligent defaults Add-on software, custom scripts, … Management Automation Standard “off the shelf” assemblies Do it yourself; few assemblies are alike Create, Test, and Maintain N virtual elements; one physical ensemble N virtual elements; M physical elements # of Things to Manage Hierarchical; pool-level modularity Monolithic; spans d. c. heterogeneity Data Center Mgmt. Arch. Menus of selectable standard behaviors Many individual knobs and variables Management Interfaces Single console; in-context functionality Separate consoles for physical & virtual # of Consoles OS OS OS Hypervisor Server
    21. 21. Server Ensemble Hierarchy <ul><li>Server ensembles look like single systems, hiding their internal parallel structure </li></ul><ul><li>Virtual resource mobility within an ensemble is a key enabling technology </li></ul>Middleware Ensemble <ul><li>AIX 6.1 WPAR ensemble </li></ul><ul><li>System z ensemble </li></ul><ul><li>VMWare ensemble (e.g. on blade servers) </li></ul><ul><li>Other x86 ensembles </li></ul><ul><li>WebSphere VE ensemble </li></ul>Examples Corresponding Ensemble Virtual Runtimes Virtual Operating Systems Level Virtual Machines a.k.a. Logical Partitions Single System Server Ensemble OS Ensemble SMP Server Hypervisor OS App OS App App App OS SMP Server Runtime MW App App OS SMP Server Hypervisor Hypervisor SMP Server Hypervisor OS App OS App App App OS SMP Server Runtime MW App App OS SMP Server Hypervisor Hypervisor SMP Server Hypervisor OS App OS App App App OS SMP Server Runtime MW App App OS SMP Server Hypervisor Hypervisor Mobility Mobility Mobility
    22. 22. Cloud Computing – Requirements on Storage <ul><li>Scale, Low cost </li></ul><ul><li>Dynamic, unpredictable workloads </li></ul><ul><li>Automated management, provisioning, performance monitor & tuning, … </li></ul><ul><li>Security and data protection </li></ul><ul><li>Quality of Storage Service </li></ul><ul><li>Geographic distribution </li></ul><ul><li>Storage Use Cases </li></ul><ul><ul><li>Archive </li></ul></ul><ul><ul><li>Database </li></ul></ul><ul><ul><li>File </li></ul></ul><ul><ul><li>Block </li></ul></ul>
    23. 23. Storage Ensembles File Server Ensemble File Server Database Server Database Server/Storage Cluster Xaction service Query service Backup Remote copy Integration Provisioning QOS, load balance Virtual storage Automated mgmt Disaster recovery SAN Components SAN Ensemble Cluster FS Cluster FS File APIs QOS Storage Tiers Backup Remote copy Archive interface Archive Ensemble Block Storage Server File & Archive APIs Indexing/Search Retention Policy Compliance + File Ensemble Cluster FS Content Mgmt <ul><li>SoFS </li></ul><ul><li>Large scale NFS and CIFS data access </li></ul><ul><li>Stream servers </li></ul><ul><li>Compliance stores </li></ul>File <ul><li>Balanced Warehouse </li></ul><ul><li>Data Warehouse cluster </li></ul><ul><li>High performance OLTP </li></ul><ul><li>Virtual storage + SAN + management </li></ul><ul><li>Virtual SAN storage as an (enterprise ) service </li></ul><ul><li>Building block for larger ensembles </li></ul><ul><li>Compliance Warehouse </li></ul>Examples Storage Ensemble Archive Database Level Block (LUN) Single System
    24. 24. Storage Ensembles are ‘Dual Use’ technology <ul><li>Improve Enterprise Computing </li></ul><ul><ul><li>Lower complexity, lower costs of operation </li></ul></ul><ul><ul><li>Improved automation </li></ul></ul><ul><ul><li>Improved security </li></ul></ul><ul><ul><li>Server / storage / network integration </li></ul></ul><ul><li>Better infrastructure for Cloud Service Offerings </li></ul><ul><ul><li>Same as above + </li></ul></ul><ul><ul><li>Responsive to dynamic workloads </li></ul></ul><ul><ul><li>Responsive to new business modes </li></ul></ul>
    25. 25. Ensemble Pool Management : Dynamic Capacity for Ensembles <ul><li>New storage is discovered and can be easily added to the Ensemble </li></ul><ul><li>The Ensemble will automatically re-balance workloads given the new available capacity </li></ul>Pooled Resources CPU=a+b+c Mem=x+y+z Scheduler App OS Image App OS Image App OS Image App OS Image App OS Image App OS Image App OS Image
    26. 26. Technologies of Scale - Cluster File Systems Compute Node Storage Node NFS/CIFS Client external fabric NFS/CIFS clients Compute cluster NSD storage servers internal fabric SAN <ul><li>Highly Scalable NAS </li></ul>Compute cluster NSD storage servers internal fabric
    27. 27. SoFS – GTS Offering Similar implementations of varying degrees of maturity found in other vendor’s products. <ul><li>General Parallel Filesystem (GPFS) - </li></ul><ul><li>IBM’s High end clustered file system </li></ul><ul><li>CTDB – Clustered Trivial Database Daemon, Controls the cluster and the file service daemons </li></ul><ul><li>Enhanced CIFS Server with NTFS Semantics to Support Active Directory Integration </li></ul><ul><li>SoFS Package – Provides Management GUI, Apache file server module, acceleration tools, etc. </li></ul><ul><li>IBM Hardware </li></ul>
    28. 28. Storage Devices Pool 1 Storage Virtualization Archive Replicate Physical Storage Management Virtual Storage Management Backup/HSM Storage Devices Pool 2 Storage Devices Pool N Device Access, Pathing Storage Provisioning Archive Replicate Backup/HSM File Systems Content Management DBMS Applications Device Access, Pathing Storage Provisioning Archive Replicate Backup/HSM File Systems Content Management DBMS Applications Virtual Storage Tier 1 Virtual Storage Tier 2 Virtual Storage Tier 3 Virtual Systems Management Physical Systems Management Virtual Storage as Block Infrastructure
    29. 29. Virtual Storage Tier 3 Block Storage Export – FC, iSCSI, IB, … Storage Devices Pool 1 Storage Virtualization Virtual Storage Management Storage Devices Pool 2 Storage Devices Pool N Virtual Storage Tier 1 Virtual Storage Tier 2 Block Storage Clusters Archive Replicate Backup/HSM Physical Storage Mgmtt Fully integrated cluster as a storage block server - Virtual Storage - Thin provisioning - Space-efficient, container based replication - Self balancing, reconfiguration, rebuild - Multiple storage tiers – cost/performance
    30. 30. Virtual Storage Tier 3 Block Storage Export – FC, iSCSI, IB, … Storage Devices Pool 1 Storage Virtualization Virtual Storage Management Storage Devices Pool 2 Storage Devices Pool N Virtual Storage Tier 1 Virtual Storage Tier 2 Stacking Storage Ensembles Archive Replicate Backup/HSM Physical Storage Mgmtt Higher layer ensembles built on lower ones - File Built on Block - Archive built on File Cluster File System Content Management
    31. 31. Standards for Cloud Storage <ul><li>Service access interfaces </li></ul><ul><li>Storage service interfaces </li></ul><ul><ul><li>Provisioning </li></ul></ul><ul><ul><li>QOS </li></ul></ul><ul><ul><li>Performance management </li></ul></ul><ul><ul><li>Chargeback accounting </li></ul></ul><ul><ul><li>Data protection </li></ul></ul><ul><ul><li>Storage Security </li></ul></ul><ul><li>Storage infrastructure management interfaces (SMIS) </li></ul>Service Management SOA Application Middleware Virtualized Infrastructure Server / Storage / Network Virtual Image Management Cloud Service User Compute