Revolutionizing IT Infrastructure: Embrace Enterprise Grid Computing

2. Bob ThomeSenior 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 EMAIL ERP DW

8. Example

9. Example: In December • Order Entry maxes out processing orders • Financials is idling below capacity Order Entry Financials

10. Example: In January • Order Entry drops off from season high • Financials maxes out on year end close Order Entry Financials

11. 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

12. 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

13. 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 Oracle Confidential 8

14. 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

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

16. 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

17. 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

18. Grid Computing Components • Storage • Database Servers • Application Servers • Provisioning andManagement Tools

19. Grid Computing Components • Storage • Database Servers • Application Servers • Provisioning andManagement Tools

20. Align Storage with Business • Islands of storage • “My storage is underutilized and growing 50% a year”

21. Align Storage with Business • Islands of data • “My storage is 30% utilized and growing 50% a year” • Disk farms of industry standard disks • Consolidate intoSAN or NAS • Provisionas needed

22. 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

23. Grid Computing Components • Storage • Database Servers • Application Servers • Provisioning andManagement Tools

24. Align Processing with the Business • Islands of computation • “15% utilization of CPU is exceptional”

25. 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

26. 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

27. Solution • Run database workload across clusters of multiple blades • Federated database • Shared database

28. Data Subsets 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 Federation Layer

29. 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 Listener/ Balancer All Data Oracle Real Application Clusters

30. 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

31. Data Subsets CPU Provisioning on Demand Shared database supports dynamic CPU provisioning Shared Database Federated Database Add blade while running Add blade, reload/repartition Drop blade while running Repartition/reload, drop blade Dynamically allocate CPU CPU allocation static All Data 21

32. 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 • Increase the allocated portionof the blade farm • Add blades or increasethe sandbox • Scale out automaticallyaccording to your priorities General Ledger Web Site

33. Example: In December • Order Entry maxes out processing orders • Financials is idling below capacity Order Entry Financials

34. Example: In January • Order Entry drops off from season high • Financials maxes out on year end close Order Entry Financials

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

36. 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

37. 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

38. Demo

39. 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

40. Grid Computing Components • Storage • Database Servers • Application Servers • Provisioning andManagement Tools

41. 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

42. Grid Computing Components • Storage • Database Servers • Application Servers • Provisioning andManagement Tools

43. 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

44. 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

45. 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

46. 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

47. 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

48. More Information • Grid on OTN • http://otn.oracle.com/grid/