1 / 15

Grid of Grids Information Management Meeting

This meeting aims to build a net-centric core enterprise service in fashion that is compatible with GGF/OGF and industry standards. Key additional services, including those for sensors and GIS, will be added. The meeting will also discuss the support of Systems of Systems through federating grids of grids and the development of a tool for easy construction of grids of grids.

carolinegarza
Download Presentation

Grid of Grids Information Management Meeting

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Grid of Grids Information Management Meeting AnabasOctober 12 2006

  2. General Goal • Build Net Centric Core Enterprise Services in fashion compatible with GGF/OGF and Industry • Add key additional services including those for sensors and GIS • Support Systems of Systems by federating Grids of Grids supporting a heterogeneous software production model allowing DoD greater sustainability and choice of vendors • Build tool to allow easy construction of Grids of Grids

  3. SS Database SS SS SS SS SS SS SS Raw Data  Data  Information  Knowledge  Wisdom AnotherGrid Decisions AnotherGrid SS SS SS SS FS FS OS MD MD FS Portal Portal OS OS FS OS SOAP Messages OS FS FS FS AnotherService FS FS MD MD OS MD OS OS FS Other Service FS FS FS FS MD OS OS OS FS FS FS MD MD FS Filter Service OS AnotherGrid FS MetaData FS FS FS MD Sensor Service SS SS SS SS SS SS SS SS SS SS AnotherService

  4. The Grid and Web Service Institutional Hierarchy 4: Application or Community of Interest (CoI)Specific Services such as “Map Services”, “Run BLAST” or “Simulate a Missile” XBMLXTCE VOTABLE CML CellML 3: Generally Useful Services and Features (OGSA and other GGF, W3C) Such as “Collaborate”, “Access a Database” or “Submit a Job” OGSA GS-*and some WS-* GGF/W3C/….XGSP (Collab) 2: System Services and Features (WS-* from OASIS/W3C/Industry) Handlers like WS-RM, Security, UDDI Registry WS-* fromOASIS/W3C/Industry 1: Container and Run Time (Hosting) Environment (Apache Axis, .NET etc.) Apache Axis.NET etc. Must set standards to get interoperability

  5. The Ten areas covered by the 60 core WS-* Specifications

  6. Activities in Global Grid Forum Working Groups

  7. Net-Centric Core Enterprise Services

  8. Produce the Needed Core Services • We can classify services in many ways and following 2 charts are one way; slightly changed from proposal as NCOW and our work changed a little. • Green is “in hand”; we know a lot • Orange is “in hand” with outside but available solutions • Red has problems – Security does not have industry consensus while current Scheduling work does not address DoD real-time service and network requirements

  9. The Core Features/Service Areas I

  10. The Core Feature/Service Areas II

  11. Additional Services • Sensors have low level support listed as FS3; higher level integration using SensorML and Filters well understood. Some work in phase I • GIS Grid services pioneered by team and already shown in phase I • Mediation (Interoperability) Services needed to link Grids (defined as a collection of ≥ 1 Services) • Need to generalize existing solutions for Sensor Grids and for MQSeries-SOAP Mediation • View NaradaBrokering as a SOAP Intermediary

  12. Out of Scope for Phase II • Many areas are still evolving significantly • Mediation/Interoperation • Security • Scheduling of non-compute Resources • Data/Information Federation • Semantic Grid and management • We will not test scalability on large number of services, sensors and component Grids • Integrating legacy systems not addressed • Grid of Grids building tool is “new idea” – can expect will benefit from further work

  13. Research Tasks • The R&D Effort is divided into five major tasks: • Task 1: Implementation of Collaboration Grid Middleware • Task 2: Enhanced NCOW Core Enterprise Services (NCES) • with Enterprise Control Services and Metadata Services • Task 3: Design and implementation of Grid of Grids mediation • algorithms and NCOW services • Task 4: Design and Implementation of Net-Centric • Collaboration Grid Builder Tool • Task 5: Technology Demonstration

  14. Grid of Grids Building Tool • This will provide a graphical interface to build grids from existing libraries of Services and Grids • Meta-data (provenance) needs to be specified • Grids (services) need to be linked • This will be built by extending an existing workflow engine which is aimed at a more tightly couple version of the builder problem • We will consider HPSearch (CGL), Taverna (Open source from UK OMII), BPEL with user interface (OMII or IU LEAD project), Eclipse • Semantic Grid provenance “add-ons” • We have experience with all these approaches

  15. Applications • Indiana University will apply to Earthquake Science and Emergency Response • Ball Aerospace will apply to DoD applications using possibly Matrix to support people involved • But a key problem is how do we package results? • Looks perhaps that GridBuilder is key • Take above 3 (or other?) applications and make scenarios as to how to use GridBuilder • Who will use GridBuilder – DoD or contractors building software

More Related