2. Bob Thome Senior Manager, Grid Computing

3. Enterprise Grid Computing

4. The best thing about the Grid is that it is unstoppable. The Economist, June 21, 2001 2

5. Top 10 Grid Computing Lies 10. The grid will be unreliable because power grid failed last year 9. The grid is 5 years away 8. The grid is just for research and academic users 7. The grid requires multiple administrative domains 6. Al Gore invented the grid

6. Top 10 Grid Computing Lies 5. You need to rewrite your apps to take advantage of the grid 4. There is only one Grid 3. You need to move everything to the grid at once 2. Oracle 10g is a grid in a box 1. The grid only runs on PowerPoint

7. Problem with Today’s IT Infrastructure  Statically Assigned Islands of Computing Resource – Some are melting down – Some are almost idle  High Costs – Hardware – Labor – Software  Hard to Align with Business Priorities ERP DW EMAIL

8. Proof: The Experts Say… “CIO’s report that server utilization is only 60%” - Forrester Research “75% of costs come from staffing & maintenance.” - Business Week “IT infrastructure is massively underutilized” - IDC “Companies can save 20% or more through consolidation” - Giga Research

9. Example

10. Example: In December  Order Entry maxes out processing orders  Financials is idling below capacity Order EntryFinancials

11. Example: In January  Order Entry drops off from season high  Financials maxes out on year end close Order EntryFinancials

12. What is Grid Computing? “In basic terms, grids are clusters of interconnected servers, enabling shared computing resources utilization” “Defining Grid Computing”, Giga Research, Agosto 2002

13. Grid Computing Vision  Computing as a utility – A network of clients and service providers  Client-side: Simplicity – Request computation or information and receive it  Server-side: Sophistication – Availability, load balancing, utilization – Information sharing, data management  Virtualization – Clients see a large virtual server – Underlying infrastructure hidden

14. Benefits of Grid Computing  Better information faster – Perform more work with fewer resources – Spread work across resources – Access to resources on demand  Faster response to changing business priorities – Instantly and dynamically realign IT resources as business needs change  Reduced IT costs – Improve utilization of existing resources – Utilize less expensive commodity platforms 8 Oracle Confidential

15. Technology Trends  Blades: Every vendor offering them – Huge cost advantages – Software vendors have to enable usage – Dell PowerEdge, HP Proliant BL, Sun Fire Blades, Fujitsu Primergy BL  Linux: Fastest growing OS – Commodity OS – Ready for blades today – Linux and blades naturally complement each other  NAS, SAN, and IB provide storage access from any blade 6

16. Grid Computing Evolution Desktop Computing Grids Collaborate Example: SETI@home Shared Server Grids Share Example: CERN Enterprise Grids Dedicated Servers In a Data Center Example: Electronic Arts Oracle Corp. Outsourcing

17. A Real Example of Grid Adoption  Oracle Embraces the Grid: – (Phase 1-- 1999): We tried to get more cycles for development by running tests on idle workstations – (Phase 2 -- 2000): We tried to harness disparate machines throughout the development org, but couldn’t overcome political obstacles – (Phase 3 -- 2001): We considered pooling machines to implement a “server farm”, but found blades to be more effective  Today, Oracle uses the Grid to build the Oracle Database 15

18. The Final Phase: Outsourcing  Problem: – Many apps are already standardized – Replicating admin knowledge to administer standard components is not cost effective – SMB does not have scale to realize grid benefits  Solution: – Buy the application as a service  Implementation: – Available today from many vendors, especially for SMB – Potentially explosive in under-automated economies and industries…remember cell phones? 14

19. Enterprise Grid Computing  Standardization – Standard blade servers, Linux – Fast interconnects for storage and network  Virtualization and provisioning – Resources dynamically assigned – Realign IT resources as business needs change  Scale out – Add additional resources to grow capability of system

20. Utility Computing Mainframe/Big SMP  Partitioning a big server  Expensive and high quality components  Complete, integrated, proprietary  Enterprise service at high cost Grid Computing  Sharing many small servers  Cheap and high quality, modular components  Complete, integrated, open  Enterprise service at low cost

21. Grid Computing Components  Storage  Database Servers  Application Servers  Provisioning and Management Tools

22. Grid Computing Components  Storage  Database Servers  Application Servers  Provisioning and Management Tools

23. Align Storage with Business  Islands of storage – “My storage is underutilized and growing 50% a year”

24. Align Storage with Business  Islands of data – “My storage is 30% utilized and growing 50% a year”  Disk farms of industry standard disks – Consolidate into SAN or NAS – Provision as needed

25. Storage Grid  Oracle Automatic Storage Manager – Provisions storage capacity automatically to Oracle 10g as needed – Stripes and Balances I/O – Mirrors: Immune to disk failure

26. Grid Computing Components  Storage  Database Servers  Application Servers  Provisioning and Management Tools

27. Align Processing with the Business  Islands of computation – “15% utilization of CPU is exceptional”

28. Align Processing with the Business  Islands of computation – “15% utilization of CPU is exceptional”  Standardize resources – Blades provide lowest cost, highest performance – Not Self-healing, Disposable  Share virtual resources  Provision resources as required  Scale out

29. Issues  Blades typically 1-4 CPUs  Many databases require greater than 4 CPUs  Platform must scale to meet future/peak demand  Databases may require more memory or I/O than many blades provide

30. Solution  Run database workload across clusters of multiple blades – Federated database – Shared database

31. Federated Database  Partition large database into many small subsets  Provide a federated (union) view of all data  Strengths: scalable, extensible  Challenges: inflexible, limited application support, availability Data Subsets Federation Layer

32. Shared Database  Multiple blades access a single database  Any instance access any data  Strengths: High availability, broad application support, dynamic scalability  Challenges: Requires shared disk, fast interconnect AllData Listener/ Balancer Oracle Real Application Clusters

33. Databases on the Grid  Database clustering with shared disk – Low cost – highest quality of service – Scalability AND availability  Add/drop servers as needs change  Automatically balance load across servers  Proven – Hundreds of customers running enterprise applications

34. CPU allocation staticDynamically allocate CPU Repartition/reload, drop bladeDrop blade while running Add blade, reload/repartitionAdd blade while running Federated DatabaseShared Database CPU Provisioning on Demand AllData Data Subsets 21 Shared database supports dynamic CPU provisioning

35. CPU Provisioning on Demand  Quarter end sale on the website – Web site load serviced by blades  Quarter ends, GL closes the books – GL higher priority, add nodes – Capacity on Demand  Scale out automatically according to your priorities  Increase the allocated portion of the blade farm – Add blades or increase the sandbox General LedgerWeb Site

36. Example: In December  Order Entry maxes out processing orders  Financials is idling below capacity Order EntryFinancials

37. Example: In January  Order Entry drops off from season high  Financials maxes out on year end close Order EntryFinancials

38. Example: With Grid Computing  Load balance based on a policy to optimize around both of these peak load conditions Order Entry & Financials

39. Policy based CPU Provisioning  Specify service levels – Response time – CPU utilization  Monitor service levels  Automatically add/drop resources to meet service level objectives  Frees administrator from provisioning activities

40. Resonance  Automatically provision CPU between databases as loads change – Completely automatic and policy driven – Automatically add/drop instances servicing a RAC database  Load-based session management and migration – Automatically migrate sessions to rebalance workload across RAC instances – Intelligently direct sessions to instances – Service-based  Transparent to applications – No application code changes required

41. Demo

42. Provision Data  Move data to available cpu – Access on demand – Replicate – Move  Provision data in bulk or incrementally with Streams  Build a CPU rich analytic farm – Provision data in for processing – Maintain it or throw it away

43. Grid Computing Components  Storage  Database Servers  Application Servers  Provisioning and Management Tools

44. Application Server Grid  Complete, integrated application server clusters  End-to-end transparent application fail-over – Fast fault recovery in seconds  Application-specific load balancing policies – Schedules – Runtime metrics

45. Grid Computing Components  Storage  Database Servers  Application Servers  Provisioning and Management Tools

46. Managing the Grid  Application Security  Self management  Tools

47. Grid Security & Identity Management  Centrally provision and revoke users – Centrally manage identities and access privileges – Provide single sign-on access to applications – Share security policies across the infrastructure  Savings increase as the grid grows – Lower administration cost – Better security

48. Self-managing Software  Oracle Database 10g – Built-in intelligent infrastructure  code instrumentation captures statistics – Automatic database diagnostic monitor  diagnostic engine in the database  tells administrator how to improve performance – Automatic tuning optimizer  SQL Profile to tune packaged applications – Automated storage management

49. Management Tools  Enterprise Manager Grid Control – Manage sets of systems as one – Application service level management – Policy-based standardization – Automated provisioning of Oracle components – Automated administration

50. Provisioning Tools  Many third-parties (systems vendors) provide provisioning tools  Designed to manage an entire heterogeneous grid  Create virtual lans, clusters, and application sandboxes on demand  Must interoperate with applications and application specific provisioning infrastructure

51. Transition to Grid Computing  Enterprises want to preserve investments – Run existing applications on grid – Moves data to new platforms without downtime  Start by – Standardizing server and storage components – Consolidating onto clusters in a data center – Automate data center management  Incrementally scale out

52. Transition to Grid Computing  Start small – Move an application – Get experience – Establish standard components – Create standard procedures and patterns – Create “known good” configurations – Continue moving things

53. Scale Out  When you run out of capacity, buy more – Clone components – Gain economies of scale – Never make a big capital investment – Never take a risk  Savings and flexibility increase as Grid grows

54. Enterprise Grid Computing  Enterprises can realize the benefits of grid computing now  New technologies make it easy – Standardize on modular low-cost hardware components – Pool resources across applications – Provision resources as required – Scale out to add resources

55. Network Oracle Grid Computing Clustered database Instances SAN 1SAN 2SAN 3SAN 4 Blade Rack

56. Unstoppable  Commercial computing faces significant problems – Silos of applications and resources – Inflexible, expensive infrastructures  These problems create a drive towards standardization and consolidation – Most companies have already begun the move  Grid technology provides the best implementation of standardization and consolidation – Lowest cost and most flexible  These factors make commercial grids unstoppable

57. More Information  Grid on OTN – http://otn.oracle.com/grid/