Your SlideShare is downloading. ×
0
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Grids: the means to what ends?
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Grids: the means to what ends?

334

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
334
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • The End of Grid? One argument is that it is being subsumed by virtualization technologies that provide the foundations for service oriented infrastructure. In this model the challenge now is how to “dial in” the requirements of applications and services and organize some proportion of the infrastructure to accommodate these requirements. Grid is therefore just a way of organizing underlying virtual resources in a pattern that suits certain applications.  There is no enterprise grid – this has given way to more general service oriented infrastructure underpinned by the holy trinity of virtualization, provisioning and orchestration? Virtualization as a vehicle to realize the dream of grid computing? obtaining on-demand computational resources from distributed sources in the same simple and intuitive way we get  electricity today. Today to run a job on the grid a user has  to identify a set of platforms capable of running that job - the right installation of operating system, libraries etc Virtualization introduces a layer of abstraction that turns the  question around from "let's see what resources are available and  figure out if we can adapt our problem to use them" to "here is an  environment or workspace I need to solve my problem - I want to have it deployed on the grid as described."   It looks as if we will be able to use VMs/appliances - as well as distributed storage facilities and network overlays - to map such virtual workspace onto physical resources. Easy to define requirements, test, install, transport – and adjust on demand. By itself, the workspace service is a little bit like iTunes without  the music. Put them together into "virtual grids" and test their operation before  requesting serious resource allocations. The End of Grid? One argument is that it is being subsumed by virtualization technologies that provide the foundations for service oriented infrastructure. In this model the challenge now is how to “dial in” the requirements of applications and services and organize some proportion of the infrastructure to accommodate these requirements. Grid is therefore just a way of organizing underlying virtual resources in a pattern that suits certain applications.  There is no enterprise grid – this has given way to more general service oriented infrastructure underpinned by the holy trinity of virtualization, provisioning and orchestration? Virtualization as a vehicle to realize the dream of grid computing? obtaining on-demand computational resources from distributed sources in the same simple and intuitive way we get  electricity today. Today to run a job on the grid a user has  to identify a set of platforms capable of running that job - the right installation of operating system, libraries etc Virtualization introduces a layer of abstraction that turns the  question around from "let's see what resources are available and  figure out if we can adapt our problem to use them" to "here is an  environment or workspace I need to solve my problem - I want to have it deployed on the grid as described."   It looks as if we will be able to use VMs/appliances - as well as distributed storage facilities and network overlays - to map such virtual workspace onto physical resources. Easy to define requirements, test, install, transport – and adjust on demand. By itself, the workspace service is a little bit like iTunes without  the music. Put them together into "virtual grids" and test their operation before  requesting serious resource allocations.
  • The End of Grid? One argument is that it is being subsumed by virtualization technologies that provide the foundations for service oriented infrastructure. In this model the challenge now is how to “dial in” the requirements of applications and services and organize some proportion of the infrastructure to accommodate these requirements. Grid is therefore just a way of organizing underlying virtual resources in a pattern that suits certain applications.  There is no enterprise grid – this has given way to more general service oriented infrastructure underpinned by the holy trinity of virtualization, provisioning and orchestration? Virtualization as a vehicle to realize the dream of grid computing? obtaining on-demand computational resources from distributed sources in the same simple and intuitive way we get  electricity today. Today to run a job on the grid a user has  to identify a set of platforms capable of running that job - the right installation of operating system, libraries etc Virtualization introduces a layer of abstraction that turns the  question around from "let's see what resources are available and  figure out if we can adapt our problem to use them" to "here is an  environment or workspace I need to solve my problem - I want to have it deployed on the grid as described."   It looks as if we will be able to use VMs/appliances - as well as distributed storage facilities and network overlays - to map such virtual workspace onto physical resources. Easy to define requirements, test, install, transport – and adjust on demand. By itself, the workspace service is a little bit like iTunes without  the music. Put them together into "virtual grids" and test their operation before  requesting serious resource allocations. The End of Grid? One argument is that it is being subsumed by virtualization technologies that provide the foundations for service oriented infrastructure. In this model the challenge now is how to “dial in” the requirements of applications and services and organize some proportion of the infrastructure to accommodate these requirements. Grid is therefore just a way of organizing underlying virtual resources in a pattern that suits certain applications.  There is no enterprise grid – this has given way to more general service oriented infrastructure underpinned by the holy trinity of virtualization, provisioning and orchestration? Virtualization as a vehicle to realize the dream of grid computing? obtaining on-demand computational resources from distributed sources in the same simple and intuitive way we get  electricity today. Today to run a job on the grid a user has  to identify a set of platforms capable of running that job - the right installation of operating system, libraries etc Virtualization introduces a layer of abstraction that turns the  question around from "let's see what resources are available and  figure out if we can adapt our problem to use them" to "here is an  environment or workspace I need to solve my problem - I want to have it deployed on the grid as described."   It looks as if we will be able to use VMs/appliances - as well as distributed storage facilities and network overlays - to map such virtual workspace onto physical resources. Easy to define requirements, test, install, transport – and adjust on demand. By itself, the workspace service is a little bit like iTunes without  the music. Put them together into "virtual grids" and test their operation before  requesting serious resource allocations.
  • Transcript

    • 1. The 451 Group Grids: the means to what ends? Steve Wallage Director of Research William Fellows Principal Analyst
    • 2. <ul><li>The 451 Group </li></ul><ul><li>Technology industry analyst company </li></ul><ul><li>Agenda: enterprise IT innovation </li></ul><ul><li>Analysis that is timely; insight that is dynamic </li></ul><ul><li>Network of 700+ client organizations globally </li></ul><ul><ul><li>Vendors </li></ul></ul><ul><ul><li>Investors </li></ul></ul><ul><ul><li>Bankers </li></ul></ul><ul><ul><li>Early-adopters </li></ul></ul>
    • 3. Grid Adoption Research Service (GARS) <ul><li>Tracking 250+ enterprise early adopters </li></ul><ul><li>Across a range of sectors: </li></ul><ul><li>Financial services, telco, pharma, film and gaming, manufacturing, energy, hi-tech, healthcare </li></ul><ul><li>Common business and technology functions: </li></ul><ul><li>Measuring value, software licensing, data management, utility computing, application development/design, state of market </li></ul><ul><li>Enterprise Computing Strategy industry summits </li></ul>
    • 4. EARN-IT: Early Adoption Research Network - IT <ul><li>GARS - Grid Adoption Research Service </li></ul><ul><li>CAOS - Commercial Adoption of Open Source </li></ul><ul><li>Security, mobile enterprise… </li></ul>
    • 5. Our work with the EC <ul><li>FP6 GridEcon project looking at economic and business models for grid usage </li></ul><ul><li>Leading technical working group (TWG7) on business models and SLA for grids </li></ul><ul><li>European Grid Co-ordination Technical Committee </li></ul><ul><li>Member of NESSI </li></ul><ul><li>FP7…… </li></ul>
    • 6. 451 view of market - agenda <ul><li>Overall state of the market </li></ul><ul><li>Drivers </li></ul><ul><li>Challenges </li></ul><ul><li>Vertical differences </li></ul>
    • 7. Levels of deployment
    • 8. What to call it? <ul><li>70% of respondents said there is a better term than ‘grid’ to describe their distributed computing architecture: </li></ul>
    • 9. Drivers – GARS users 77% 57% 49% 41% 26% Time to Market Competition Do New Things Save Money Improved Performance
    • 10. Drivers – a broader look
    • 11. Drivers – proving the business case <ul><li>Tangible vs intangible </li></ul><ul><li>Buy-in </li></ul><ul><li>Proof of concept </li></ul><ul><li>Competitive advantage </li></ul>
    • 12. Challenges – GARS interviews 46% 33% 33% 31% 28% 20% 19% 19% 18% 18% 15% 14% 1% Semantic Web Skills Shortage App Dev Lack of Standards Prove ROI Grid to Utility Grid to SOA Grid Enabling Apps Security Data Mgmt Cultural Bandwidth Licensing
    • 13. Challenges – a broader look
    • 14. Challenges – experiences from a different perspective <ul><li>Sensitive data, sensitive apps (medical patient records) </li></ul><ul><li>Different organizations get different benefits </li></ul><ul><li>Accounting, who pays for what (sharing!) </li></ul><ul><li>Security policies: consistent and enforced across the grid </li></ul><ul><li>Lack of standards prevent interoperability of components </li></ul><ul><li>Current IT culture is not predisposed to sharing resources </li></ul><ul><li>Not all applications are grid-ready or grid-enabled </li></ul><ul><li>Open source is not equal open source (read the small print) </li></ul><ul><li>SLAs based on open source (liability?) </li></ul><ul><li>“ Static” licensing model don’t embrace grid </li></ul><ul><li>Protection of intellectual property </li></ul><ul><li>Legal and tax issues (FDA, HIPAA, multi-country grids) </li></ul>
    • 15. Cultural challenges <ul><li>Ownership and control </li></ul><ul><li>CxO buy-in </li></ul><ul><li>Importance of stakeholders </li></ul><ul><li>Internal SLAs </li></ul>
    • 16. Deployment – by vertical
    • 17. Vertical market - differences <ul><li>Software licensing </li></ul><ul><li>Range of applications </li></ul><ul><li>Use of desktop scavenging </li></ul><ul><li>Use of outsourcing </li></ul><ul><li>Use of open source </li></ul>
    • 18. Where are we going? William Fellows
    • 19. Levels of deployment
    • 20. Next - support broader IT objectives
    • 21. What do we know?
    • 22. The sweet spots of activity are: <ul><li>Enterprise utilities </li></ul><ul><li>Platform for shared services </li></ul><ul><li>In other words, a technology infrastructure and an application infrastructure. </li></ul>
    • 23. The key technology drivers <ul><li>Grid technologies </li></ul><ul><li>Virtualization </li></ul><ul><li>SOA, SOLE, SOIT, SOE…. </li></ul><ul><li>New approaches to power, performance, space </li></ul>
    • 24. Virtualization <ul><li>Enterprises are experiencing benefits from infrastructure virtualization </li></ul><ul><li>Virtualization is being applied at every layer of the IT stack - compute, network, data and apps </li></ul><ul><li>Concerns: sweeping complexity under the carpet, performance overheads, license costs, vendor lock-in, too many moving parts? </li></ul><ul><li>Virtual appliances rival SaaS? </li></ul><ul><li>Do grid and virtualization intersect, converge or collide? </li></ul>
    • 25. One approach: a layered view (from EGA reference model) Each physical layer provides abstraction to the layer above Each virtualized layer provides a flexible mapping/management Network Compute Storage Switches, Routers etc. Servers, Blades etc. Disks, Array Controller, SAN switches etc. Physical VLANs Hypervisors LUNs Virtualized Physical Network protocols e.g. TCP/IP, UDP Operating Systems e.g. Linux, Windows File systems e.g. NTFS, Ext3 Operating Environment Load balancing, Global IP, Virtual IP Virtual Machine Monitors, Solaris Containers, BSD Jails NFS, CIFS, SMB, NAS Virtualized Operating Environment Web Server App Server Database Platform Instance Server Farm Compute Grid Data Grid Virtualized Platform Customer Portal Risk Management Reference Data Business process / service
    • 26. Grid and virtualization: vectors intersect <ul><li>Virtualization - a vehicle to realize the dream of  grid computing? </li></ul><ul><li>Mapping virtual workspaces to physical resources - virtual grids </li></ul><ul><li>The end of grid? </li></ul><ul><li>Battle for control - vendors extending into other territories </li></ul>
    • 27. Grid and enterprise utility <ul><li>Leading adopters implementing ‘grid economy’ across shared resources </li></ul><ul><li>Requires willingness to participate in a shared IT infrastructure </li></ul><ul><li>Self-service is a driver </li></ul><ul><li>SaaS and open source are cost-effective and additive </li></ul><ul><li>Next steps - SLA monitoring, policy management, chargeback across heterogeneous resources </li></ul>
    • 28. Grid and public utility computing <ul><li>Grid delivers economies of scale for next-generation hosting providers = increased adoption </li></ul><ul><li>Are we ready for utility computing now? (Yes, but don't call it that) </li></ul><ul><li>So what is interesting? </li></ul><ul><li>Issues: multi-tenanted, per-drink pricing, software licenses, SaaS pricing complexity, lack of app services, loss of budget predictability </li></ul>
    • 29. Grid and public utility computing <ul><li>Users with enterprise utilities are more likely to examine other outsourcing options </li></ul><ul><li>Back in the conversation but won’t be an 'all or nothing' play </li></ul><ul><li>A lot of marketing, but not yet a market </li></ul><ul><li>Telcos become IT services providers. Google, Amazon, eBay take on incumbents (eBay financial markets?) </li></ul>
    • 30. IT as a utility <ul><li>80% culture change - 20% technology integration </li></ul><ul><li>Back to the future? </li></ul><ul><li>Charge to a business metric not CPU/hour - at the service delivered to the user not resources used at backend </li></ul><ul><li>Cheaper in-house? Outsourced CPU suppliers need better pricing models </li></ul>
    • 31. Rebirth of cool <ul><li>Enterprise datacenter sales used to be two dimensional - what is the performance and what is the cost? </li></ul><ul><li>Power consumption, heat dissipation, space and their SLAs are top of procurement conversations </li></ul><ul><li>Blades = less space but more more heat </li></ul><ul><li>Rebirth of mainframe cooling techniques - IBM cool door, HP cool fan, Green Grid.. </li></ul><ul><li>Other approaches: pooling/outsourcing for peak loads, multicore, FPGA, cell, GPUs, streaming CPUs </li></ul>
    • 32. Rebirth of cool <ul><li>US EPA Energy Star program: “every dollar spent on IT equipment, $3 to $4 is spent on operating it over its life” </li></ul><ul><li>Energy costs for UK businesses have increased by 57% during the last 12 months, and now form a significant element of operational expenses, often greater than IT equipment depreciation and sometimes greater than real-estate costs </li></ul><ul><li>How to factor into ROI? Return on Environment - new metric for technology innovation </li></ul><ul><li>451 Group report: ‘EcoEfficient IT’ </li></ul>
    • 33. Banks’ verdict: grid is good for… <ul><li>Looks capable of driving sustainable, long-term and linear cost savings and performance improvements </li></ul><ul><li>Use of grids to scale across the organization and support additional activities such as exotics </li></ul><ul><li>Can common approaches (above the waterline) drive differentiation and competitive advantage? </li></ul><ul><li>Return to spending on innovation instead of managing complexity </li></ul><ul><li>Utility, flexibility, scale - agility </li></ul><ul><li>Scale: “This year's exotic can easily become next year's flow.” </li></ul>
    • 34. Who do we know about?
    • 35. Data management <ul><li>Problem </li></ul><ul><li>Interface between compute grid and data grid/cache </li></ul><ul><li>File systems are a bottleneck – storage startups solve it? </li></ul><ul><li>Storage not kept up with compute power </li></ul><ul><li>Latency is a business issue not a technology issue - for faster business cycles the time to execute must be less than the time to act </li></ul><ul><li>Innovation </li></ul><ul><li>Storage/file systems (EMC, NetApp, Ibrix, Nirvana, Acopia, NeoPath, Isilon) database (Xkoto, Vertica), clustering (PolyServe, Panasas, Isilon, Oracle), caching (Tangosol, GemStone, GigaSpaces, Composite), data integration </li></ul><ul><li>Google BigTable, MapReduce, Sawzall; Microsoft Dryad </li></ul>
    • 36. Metering, billing, chargeback <ul><li>Problem </li></ul><ul><li>Measuring virtualized compute, network and storage resources </li></ul><ul><li>Allocation of resources and priority assessment </li></ul><ul><li>Rating, mediation </li></ul><ul><li>Policy enforcement </li></ul><ul><li>Unit of measure </li></ul><ul><li>Innovation </li></ul><ul><li>Evident Software, LeCayla, Provment, Iontas, Itheon, IBM CIMS, Digital Fuel </li></ul>
    • 37. Managing virtualization. Implementing SLA/policy <ul><li>Problem </li></ul><ul><li>Managing VMs </li></ul><ul><li>Automation of tasks/run book </li></ul><ul><li>Enforcing SLAs/policies </li></ul><ul><li>Performance analysis </li></ul><ul><li>Semantics </li></ul><ul><li>Innovation </li></ul><ul><li>VMware, Xen, Scalent, DataSynapse EverGrid, ToutVirtual, VirtualIron, IBM Meiosys, Platform, UD, Trigence, Dunes </li></ul><ul><li>OpsWare/iConclude, BladeLogic, Cassatt, Egenera, RealOps, Enigmatec, Opalis,Tideway, OpTier </li></ul><ul><li>Dtrace, SystemTap, Sawzall </li></ul>
    • 38. Applications <ul><li>Problem </li></ul><ul><li>Run existing applications unchanged, self-service </li></ul><ul><li>A platform for new app development or chopping up older applications? Levels 1 to 5… </li></ul><ul><li>New approaches to multi-threading, parallelism </li></ul><ul><li>Batch to interactive, real-time: mixed workloads </li></ul><ul><li>Innovation </li></ul><ul><li>Grid or fabric-aware application servers provide virtualized containers for apps and app servers </li></ul><ul><li>IBM XD, UD/SAP, Oracle, DataSynapse, Platform, BEA, Scalent, Appistry, Aspeed, 3Tera, Trigence, EverGrid </li></ul>
    • 39. Security <ul><li>Problem </li></ul><ul><li>Neglected by many users, believe protected within their own firewalls </li></ul><ul><li>Biggest threat is internal </li></ul><ul><li>External challenges - malicious usage, stealing algorithms, using the grid against its owner, using the grid for unauthorized programs </li></ul><ul><li>Trusting of resource brokers, other internal (can you trust another department ?) and external data sources </li></ul><ul><li>The 451 Group has formed a panel to develop security recommendations for organizations deploying grids </li></ul>
    • 40. Where are we going?
    • 41. ‘ grids’ not ‘The Grid’ <ul><li>Resurgence of grid </li></ul><ul><li>HPC or NGDC? Convergence - datacenter automation </li></ul><ul><li>Could use some some open standards - but waiting is too risky (getting left behind) </li></ul><ul><li>Requires maturity of processes </li></ul><ul><li>Some of today’s tools are sufficient - but we are in the inventory period in terms of usage </li></ul><ul><li>Business and senior management expectations exceed capabilities? </li></ul>
    • 42. Beyond using ‘Grid’ to solve HPC <ul><li>Define new workloads for grids </li></ul><ul><li>Platform to support SoA </li></ul><ul><li>Create shared service architecture </li></ul><ul><li>Enable collaboration </li></ul><ul><li>Standardized semantics </li></ul><ul><li>Build composite applications </li></ul><ul><li>Create virtual organizations </li></ul>
    • 43. grids - through 2010 <ul><li>Virtualization allows grid to be absorbed into to the enterprise fabric </li></ul><ul><li>Convergence of grids, multicore and virtualization will have a profound effect </li></ul><ul><li>Silos to horizontally integrated resources - enterprise utilities </li></ul><ul><li>Downstream of HPC: mixed workloads, risk management in other verticals, analytics, MDM, ERP </li></ul><ul><li>Batch and real-time/interactive blurring </li></ul><ul><li>Mitigate risk through flexibility </li></ul>
    • 44. grids - through 2010 <ul><li>Continued confusion between grid, SOA, virtualization and utility computing </li></ul><ul><li>Vendor execution and partnerships - more important than ‘vision’ </li></ul><ul><li>Latency is a business issue not a technology issue - for faster business cycles the time to execute must be less than the time to act </li></ul><ul><li>Users increasingly socialize their IT models </li></ul><ul><li>Innovation: companies can’t just cost-cut their way to prosperity </li></ul><ul><li>The end of grid? No. Grid is the means to many ends </li></ul>
    • 45. The 451 Group Grids: the means to what ends? Steve Wallage Director of Research William Fellows Principal Analyst
    • 46. Thankyou. Questions?

    ×