1. 1 Use Cases Application provisioning (version control) Workload management/load-balancing (server consolidation) Data Federation/sharing E-utilities (provisioning on demand) Enterprise application integration (Boeing example) ------------------------------------------------------------------------------- No changes to applications Security - of course Multiple sites Multiple administrative domains Mutual distrust Frequent failure and needs for recovery Scalability Dynamic resource changes

2. 2 Technical Requirements Manage complexity Extensible Site autonomy Secure I/O Multi-language Scalable Fault-tolerance and exception management Simple - focus on what users know Legacy support Single namespace Resource management

3. 3 Workload management Run jobs - consolidate servers - sequential jobs and parallel jobs Improve utilization of resources - decrease costs, increase jobs per day Accounting by resource (CPU, application) and person/group Classic compute grid

4. 4 Data Federation Data at multiple sites Data changes Users (apps) want access to all authorized data Data must stay at home Performance is critical Coherence is critical Audit trail of updates BOTH flat files and RDBMS requirements - Query mostly on RDBMS

5. 5 Basic Grid Domain Interconnect Patterns - data Wide Area Data Distribution Multi-site Team Collaboration Data Licensing Partnerships Compute Farm Data Provisioning

6. 6 Interconnects and Collaboration Partner (Subscription Data) Partner B (Licensed Data) Genomics Group (Raleigh) Proteomics Group (San Diego) Server Farm (Cambridge) Partner (Contract Research) Partner A (Licensed Data) Companies, partners, and academic institutions want to collaborate Often, the nature of these collaborations must remain private Consequently, mediation by a 3 rd party is unacceptable Interconnects enable collaboration through federation Interconnects make sure all collaborations remain private

7. 7 E-utilities On-demand access to remote compute capability Performance guarantees

8. 8 Enterprise Application Integration Think of this like supply chain management - but with component simulations and data sets Couple application components that are proprietary and run in different companies Different data sets kept in different companies