Gridforum.nl Annual Business Day 2008

1. Eindhoven Edition

3. How do we know when e-Science has succeeded? Not just accelerated but new A. When everyone is using the Grid B. When there are routine scientific advances that would not have happened otherwise

4. How do we move from heroic scientists doing heroic science with heroic infrastructure to everyday scientists doing science they couldn’t do before? humanists archaeologists geographers musicologists ... researchers! research It’s the democratisation of e-Research 

5. scientists Digital Libraries Graduate Students Undergraduate Students experimentation Data, Metadata Provenance Workflows Ontologies The social process of science Local Web Repositories Virtual Learning Environment Technical Reports Reprints Peer-Reviewed Journal & Conference Papers Preprints & Metadata Certified Experimental Results & Analyses

17. Note to Reader. The next slides are not intended to be anti-grid. Everyone working on Grid is doing great work.

19. e-Science Pipeline e-Science Technology Creators & Integrators Applications Research EE Research Socio-economic & Commercial Innovation e-Science bespoke tailoring Mass Use by Researchers 5 years 5 years 5 years CS Research e-Science 10s of integrators 100s of embedded consultants 1000s of research users The Arrow Problem Malcolm Atkinson NB This isn’t wrong!

21. Web Services RESTful APIs cmd lines ssh http Web Browser Mobile phone iPod Car Equipment PDA P2P OeRC mashups workflows services applications Subject ICT experts Computer Scientists Software Companies Workflow tools Ruby on Rails ecosystem Scientists open source Software Engineers nesc

26. use Web 2.0 here? Grid

27. use Web 2.0 here? Grid

28. use Web 2.0 here Grid Grid cloud HPC

29. A utility is a directly and immediately useable service with established functionality, performance and dependability, illustrating the emphasis on user needs and issues such as trust Services are knowledge-assisted (‘semantic’) to facilitate automation and advanced functionality, the knowledge aspect reinforced by the emphasis on delivering high level services to the user The architecture comprises services which may be instantiated and assembled dynamically, hence the structure, behaviour and location of software is changing at run-time Service-Oriented Knowledge Utility semanticgrid.org/NGG3

30. If you peel back the label and its says “Grid” or “OGSA” underneath… its not a cloud. If you need to send a 40 page requirements document to the vendor then… it is not cloud. If you can’t buy it on your personal credit card… it is not a cloud If they are trying to sell you hardware… its not a cloud. If there is no API… its not a cloud. If you need to rearchitect your systems for it… Its not a cloud. If it takes more than ten minutes to provision… its not a cloud. If you can’t deprovision in less than ten minutes… its not a cloud. If you know where the machines are… its not a cloud. If there is a consultant in the room… its not a cloud. If you need to specify the number of machines you want upfront… its not a cloud. If it only runs one operating system… its not a cloud. If you can’t connect to it from your own machine… its not a cloud. If you need to install software to use it… its not a cloud. If you own all the hardware… its not a cloud. James Governor

31. Multicore chips will offer so much performance that we need not cobble together heterogeneous resources but rather can deploy simple powerful systems Geoffrey Fox

33. N 2 N N

34. One Middleware 2N N N

35. Middleware ? N N Middleware Middleware Middleware Middleware Middleware Polynomial involving N1, N2 and M

36. www.myexperiment.org

39. 40 Taverna downloads per day taverna.sourceforge.net 2007 2006 2005 2004 2003

41. Kepler Triana BPEL Ptolemy II

44. Google Gadget

45. Ownership and Attribution

46. 24/5/2007 | myExperiment | Slide

47. ` Enactor HTML XML Snapshot map of resources with their relationships and versions users descriptions groups friendships tags blobs workflows

48. scientists Graduate Students Undergraduate Students experimentation Data, Metadata Provenance Workflows Ontologies Digital Libraries The social process of science 2.0 Local Web Repositories Virtual Learning Environment Technical Reports Reprints Peer-Reviewed Journal & Conference Papers Preprints & Metadata Certified Experimental Results & Analyses

51. Provenance Harvesting myExperiment metadata bus ORE Encapsulated myExperiment Object (EMO) Metadata RDF Store

53. Anatomy of an EMO EMO Metadata creator, modified, rights URIs into myExperiment(s) with types and comments workflow, data, description URIs to external resources, with alternates, types, comments, versions Optional annotations of URIs and their relationships

54. Linked Data

57. Malcolm Atkinson