1. LEAD Project Discussion Presented by: Emma Buneci for CPS 296.2: Self-Managing Systems Source for many slides: Kelvin Droegemeier, Year 2 site visit presentation.

2. 2 Mesoscale Weather

3. 3 What Weather & IT Today Do …

4. 4 Radars Do Not Adaptively Scan

5. 5

6. 6

7. 7

8. 8

9. 9

10. 10 The Case for Dynamic Adaptation 1.Adaptation in Time 2.Adaptation in Space 3.Ensemble Forecasting 4.Adaptive Observing Systems 5.Adaptive Cyber-infrastructure 6.Managing Forecast and Simulation Process

11. 11 Adaptation in Time

12. 12 Adaptation in Space

13. 13 Ensemble Forecasting

14. 14 Adaptive Observing Systems

15. 15 Adaptive Cyberinfrastructure

16. 16 Managing the Forecast & Simulation Process Current State: 50,000 lines of Perl code. In Progress: LEAD Workflow Environment

17. 17

18. 18

19. 19 LEAD Service Oriented Architecture Why A Service-Oriented Architecture? Flexible and malleable Platform independence (emphasis on protocols, not platforms) Loose integration via modularity Evolvable and re-usable (e.g. Java) Interoperable by use of standards  robustness Distributed Resources Computation Specialized Applications Steerable Instruments Storage Data Bases Resource Access Services GRAM Grid FTP SSH Scheduler LDM OPenDAP Generic Ingest Service User Interface Desktop Applications IDV WRF Configuration GUI LEAD Portal Portlets Visualization Workflow Education Monitor Control Ontology Query Browse Control Crosscutting Services Authorization Authentication Monitoring Notification Configuration and Execution Services Workflow Monitor MyLEAD Workflow Engine/Factories VO Catalog THREDDS Application Resource Broker (Scheduler) Host Environment GPIR Application Host Execution Description WRF, ADaM, IDV, ADAS Application Description Application & Configuration Services Client Interface Observations Streams Static Archived Data Services Workflow Services Catalog Services RLS OGSA- DAI Geo-Reference GUI Control Service Query Service Stream Service Ontology Service Decoder/ Resolver Service Transcoder Service/ ESML Source: LEAD Team

20. 20

21. 21

22. 22

23. 23

24. 24 Some Discussion Points Complexity of the infrastructure to support LEAD –Lesson learned: viable solution where small number of services are persistent; remaining are on-demand Challenges for the system administrators –Large scale networks, supercomputers; different for sys. Admins in industry setting? What lessons from this experiment will apply to building similar infrastructures in other domains Future impact of LEAD

25. 25