1. © 2007 UC Regents1 Rocks – Present and Future The State of Things Open Source Grids and Clusters Conference Philip Papadopoulos, Greg Bruno Mason Katz, Anoop Rajendra

2. Personal Thanks  Thanks to everyone who is here.  Without users, we have no reason to build software  Special Thanks to Steve Tuecke. This conference/workshop would not have happened without him.  Many thanks Laura Kesselman-Jones. She has made sure that everything from registration to AV has worked © 2007 UC Regents2

3. YOUR role  Ask questions! This is a workshop. We don’t want to be “Send-only Mode”  Take advantage of the “Grill the Guru’s” session.  Come talk one-on-one with Rocks, Globus, and SGE developers to solve your problems © 2007 UC Regents3

4. 4 The Goal of Rocks Enable domain scientists (non-specialists) to trivially build clusters of all functions and sizes (Put in DVDs and Start Computing) Rocks easily handles more than just MPI /HPC Clusters

5. © 2007 UC Regents5 Our Original Goal: Support the Traditional “Beowulf” Frontend Node Public Ethernet Private Ethernet Network Application Network (Optional) Node Power Distribution (Net addressable units as option)

6. © 2007 UC Regents6 The Modern “Cluster” Architecture is more Interesting

7. © 2007 UC Regents7 And Rocks Supports other types Clusters  Cluster of GPUs  OpenGL machine  Not an MPI machine  Massive Pixel Walls  60 MegaPixels  Full rate HDTV  Software  SAGE  DMX  Chromium

8. Rocks Today  Open-source Active development for 7+ years  Demonstrated Scalability from 2 – 1000 nodes. Several 1000 Clusters Worldwide  ~1800 Users on our discussion list  About 450 Messages/Month  Commercial support available, in addition.  Redhat Enterprise 4/5 compatible.  Core to many NSF/NIH-funded grants  Funding from NSF for core through 2010 © 2007 UC Regents8

9. Big Clusters, Little Clusters, and Everything in Between © 2007 UC Regents9

10. What Rocks Solves  You are building a [compute, web, database, visualization, ??] cluster  What software should I select ?  How should it be configured?  How long will it be before I start useful work ?  I like your cluster configuration, but I have a different HW vendor, how do I re-create what you have already done?  I’d rather drink coffee than configure software © 2007 UC Regents10

11. Rolls: Our Extension Mechanism  Rolls define the “macro” components of your cluster  Contain: Packages AND how to Automatically Configure/Localize  Can and are built by others  Many examples:  Grid (Globus), SGE  Condor, Torque, Moab  Java, Area51, Intel Compiler, Viz,  … (+Several Commercial ) © 2007 UC Regents11

12. Rocks Base HPC Sched uler GridBIRN Project-Specific Extension Rolls Define the Complete Stack

13. Rocks Version 5.0 (V)  Released 4/30/08.  Support RHEL/CentOS 5.1  Xen-based virtualization  Define, Start, Stop, Move Virtual Machines Identical description mechanism for real/virtual systems  Low-Level, but Important features  Programmatic partitioning (“infinite customization”)  Flash BIOS via PXE  Many SW Version Updates © 2007 UC Regents13

14. Virtualization is Having Positive and Widespread Impact, but beware  The VM Image is  One big bucket of Bits  Not Replicable if you don’t know how it was built  Not easily extensible if you don’t how it was built  Giving complete OS Power to the User runs the following Risks  Turn Every Scientist into a System Administrator  Unpatched/Vulnerable OS installations, on “well- cared” for machines © 2007 UC Regents14

15. Predictions  In 3 Years, Many Users Will Run Their HPC/Parallel Applications Exclusively inside of VMs  Irrespective of where the hardware is located (local, utility, etc)  In 5 years, Huge Computing Facilities (Like Teragrid) will be Mandated to Host User-defined VMs as Standard Procedure  All Performance Inadequacies Will be Deemed “Acceptable”  Rigorous Software Integration will far outweigh hardware concerns  (We’re working to make Rocks More Adaptable) © 2007 UC Regents15

16. © 2007 UC Regents16