OGSA Information Abdeslem Djaoui OGSA Information, OGSA-WG #11

Slides:



Advertisements
Similar presentations
© 2006 Open Grid Forum Ellen Stokes, IBM Michel Drescher, Fujitsu Information Model, JSDL and XQuery: A proposed solution OGF-19 Chapel Hill, NC USA.
Advertisements

© 2006 Open Grid Forum Network Services Interface Introduction to NSI Guy Roberts.
© 2006 Open Grid Forum OGF19 Federated Identity Rule-based data management Wed 11:00 AM Mountain Laurel Thurs 11:00 AM Bellflower.
© 2007 Open Grid Forum JSDL-WG Session OGF27 – General Session 10:30-12:00, 14 October 2009 Banff, Canada.
© 2006 Open Grid Forum Joint Session on Information Modeling for Computing Resources OGF 20 - Manchester, 7 May 2007.
© 2007 Open Grid Forum JSDL-WG Session OGF21 – Activity schema session 17 October 2007 Seattle, U.S.
© 2008 Open Grid Forum Resource Selection Services OGF22 – Boston, Feb
© 2006 Open Grid Forum Network Services Interface OGF29: Working Group Meeting Guy Roberts, 19 th Jun 2010.
Feb OGF22NML-WG: Welcome and Introduction Welcome and Introduction Paola Grosso - UvA Martin Swany - UDelaware.
© 2006 Open Grid Forum JSDL Optional Elements OGF 24 Singapore.
© 2006 Open Grid Forum Joint Session on Information Modeling for Computing Resources (OGSA Modeling Activities) OGF 21 - Seattle, 16 October 2007.
© 2006, 2007 Open Grid Forum Michel Drescher, FujitsuOGF-20, Manchester, UK Andreas Savva, FujitsuOGF-21, Seattle, US (update) Extending JSDL 1.0 with.
OGSA-WG Session #4 Usecase Document Overview Platform Service Next Step Discussion GGF10 Berlin March. 11, :30pm Audimax.
1 ©2013 Open Grid Forum OGF Working Group Sessions Security Area – FEDSEC Jens Jensen, OGF Security Area.
© 2006 Open Grid Forum DCI Federation Protocol BoF Alexander Papaspyrou, TU Dortmund University Open Grid Forum March 15-18, 2010, Munich, Germany.
© 2005 Global Grid Forum The information contained herein is subject to change without notice Leading the pervasive adoption of grid computing for research.
© 2007 Open Grid Forum Data Grid Management Systems: Standard API - community development Arun Jagatheesan, San Diego Supercomputer Center & iRODS.org.
© 2006 Open Grid Forum Service Level Terms Andrew Grimshaw.
OGF DMNR BoF Dynamic Management of Network Resources Documents available at: Guy Roberts, John Vollbrecht.
© 2006 Open Grid Forum Network Services Interface OGF 32, Salt Lake City Guy Roberts, Inder Monga, Tomohiro Kudoh 16 th July 2011.
© 2006 Open Grid Forum FEDSEC-CG Andrew Grimshaw and Jens Jensen.
OGSA-RSS Face-to-Face Meeting Sunnyvale, CA, US Aug 15-16, 2005.
© 2006 Open Grid Forum OGSA-WG: EGA Reference Model GGF18 Sept. 12, 4-5:30pm, #159A-B.
Leading the pervasive adoption of grid computing for research and industry © 2005 Global Grid Forum The information contained herein is subject to change.
© 2006 Open Grid Forum Grid High-Performance Networking Research Group (GHPN-RG) Dimitra Simeonidou
© 2005 Global Grid Forum The information contained herein is subject to change without notice Leading the pervasive adoption of grid computing for research.
© 2006 Open Grid Forum NML Progres OGF 28, München.
Leading the pervasive adoption of grid computing for research and industry © 2005 Global Grid Forum The information contained herein is subject to change.
© 2007 Open Grid Forum OGF Management Area Meeting OGF20 7 May, am-12:30pm Manchester, UK.
© 2006 Open Grid Forum Grid Resource Allocation Agreement Protocol GRAAP-WG working session 1 Thursday, 5 March, 2009 Catania, Sicily.
Leading the pervasive adoption of grid computing for research and industry © 2005 Global Grid Forum The information contained herein is subject to change.
© 2006 Open Grid Forum 1 Application Contents Service (ACS) ACS-WG#1 Monday, September 11 10:30 am - 12:00 am (158A-B) ACS-WG#2 Wednesday, September 13.
© 2008 Open Grid Forum Production Grid Infrastructure WG State Model Discussions PGI Team.
Leading the pervasive adoption of grid computing for research and industry © 2005 Global Grid Forum The information contained herein is subject to change.
OGSA Data Architecture WG Data Transfer Session Allen Luniewski, IBM Dave Berry, NESC.
Leading the pervasive adoption of grid computing for research and industry © 2005 Global Grid Forum The information contained herein is subject to change.
© 2007 Open Grid Forum JSDL-WG Session OGF26 – General Session 11:00-12:30, 28 May 2009 Chapel Hill, NC.
Network Services Interface
Mark Morgan February, 2006 (GGF16 in Athens)
SLIDES TITLE Your name Session Name, OGSA-WG #nn
GGF Intellectual Property Policy
OGSA Information Management Services status
Welcome and Introduction
RISGE-RG use case template
Hiro Kishimoto, OGSA-WG co-chair GGF16 in Athens February 17, 2006
OGSA Session #1 Execution Management Services
OGSA Data Architecture WG Data Transfer Discussion
OGSA-WG EMS Architecture
Grid Resource Allocation Agreement Protocol
Service Virtualization via a Network Appliance….
OGF session PMA, Florence, 31 Jan 2017.
OGSA-WG Session #2 Program Execution Services
WS-Agreement Working Session
Sessions 1 & 3: Published Document Session Summary
Grid Scheduling Architecture – Research Group
Hiro Kishimoto, OGSA-WG co-chair GGF16 in Athens February 13, 2006
Sharing Topology Information
Network Services Interface
Network Services Interface Working Group
OGSA-Workflow OGSA-WG.
Naming service BoF #2 & report session
Information Model, JSDL and XQuery: A proposed solution
Network Measurements Working Group
WS Naming OGF 19 - Friday Center, NC.
Activity Delegation Kick Off
Network Services Interface Working Group
Introduction to OGF Standards
Proposed JSDL Extension: Parameter Sweeps
UR 1.0 Experiences OGF 24, Singapore.
OGF 40 Grand BES/JSDL Andrew Grimshaw Genesis II/XSEDE
Presentation transcript:

OGSA Information Abdeslem Djaoui OGSA Information, OGSA-WG #11 30 June, 2005 (GGF14 in Chicago) 7:30-9:00am

GGF Intellectual Property Policy All statements related to the activities of the GGF and addressed to the GGF are subject to all provisions of Appendix B of GFD-C.1, which grants to the GGF and its participants certain licenses and rights in such statements. Such statements include verbal statements in GGF meetings, as well as written and electronic communications made at any time or place, which are addressed to any GGF working group or portion thereof, Where the GFSG knows of rights, or claimed rights, the GGF secretariat shall attempt to obtain from the claimant of such rights, a written assurance that upon approval by the GFSG of the relevant GGF document(s), any party will be able to obtain the right to implement, use and distribute the technology or works when implementing, using or distributing technology based upon the specific specification(s) under openly specified, reasonable, non-discriminatory terms. The working group or research group proposing the use of the technology with respect to which the proprietary rights are claimed may assist the GGF secretariat in this effort. The results of this procedure shall not affect advancement of document, except that the GFSG may defer approval where a delay may facilitate the obtaining of such assurances. The results will, however, be recorded by the GGF Secretariat, and made available. The GFSG may also direct that a summary of the results be included in any GFD published containing the specification.

OGSA Information introduction and status RSS – relation to OGSA Info Session Agenda Housekeeping GGF IP Signing sheet Note taker OGSA Information introduction and status Abdeslem Djaoui RSS – relation to OGSA Info Mathias Dalheimer OGSA Information architecture skeleton

OGSA Information Introduction and Status

OGSA Information V1.0 and beyond Set of scenarios Wide range of capabilities Naming Discovery Monitoring Message delivery Logging Since then Naming just moved to its own WG Logging BOF at GGF12, but no current activity Since GGF13 OGSA-F2F Work on InfodD specification

So What do we mean by OGSA information? The term is used generically to refer to Any data used for the following: Discovery Monitoring Such data relates to: Resources (storage, networks, …) Grid Services Grid Applications OGSA-Info capabilities allow for moving information around (message delivery) “matching” of sources and sinks of that information Defining new types of information Exact meaning of that information is dependent on the usage (logging, monitoring, auditing, …), but underlying capabilities are the same

OGSA-Info – one cloud Client publishers use OGSAProducer interface to publish information Client consumers use OGSAConsumer interface to request and receive information Information from Publishers is dynamic and scattered throughout the Grid Publishers and consumers do not necessarily know about each other before hand Client Publisher Client Publisher OGSAProducer OGSAProducer OGSA-Information OGSAConsumer OGSAConsumer Client Consumer Client Consumer

Advantages OGSA Producer/Consumer interfaces Provide a simple and common way for users to put information into the Grid and to retrieve information from the Grid Hide complexity of information system from end-users Abstract differences between available specification Example: WSN Consumer and InfoD Consumer For consumers it creates impression that you have one “Virtual” data base which they can query through OGSAConsumer interface How this is achieved is being worked out in InfoD

Typical Consumer Queries “For every node N, how many computers connected to N have currently a cpu-load of no more than 30%?” “Yesterday, between which nodes was the average transportation time for 1 MB packets higher than than 0.… seconds?” “Show me the (average) cpu-load of computers at CERN and RAL!”

Combined Consumer/Publisher - CCP Used to consume and then re-publish data To co-locate information to speed up queries To reduce network traffic To use different publisher properties P CCP OC OP P OC OC P P – Publisher OC – OGSAConsumer OP - OGSAProducer

Some requirements – Publishers and Producers Publishers have no prior knowledge of potential consumers Producers may have different properties/QoS. Persistency Retention period Delivery guarantees The information system should not impose limits on the number of publishers Monitoring data should carry a timestamp A user must be able to publish data (via a Producer) even if the type of this data is not previously known to the system Critical data needs to be secured

Some requirements - Consumers Consumers have no prior knowledge of relevant producers Consumers may have different properties/QoS. Persistency Retention period Delivery guarantees The information system should not impose limits on the number of consumers A Consumer should be able to obtain information from a Publisher on a one off basis or as a stream Critical data needs to be secured A consumer should return an answer within an acceptable amount of time

Relation of information services to rest of OGSA leverage OGSA infrastructure Basic Profile Be leveraged For Discovery purposes By Execution Management Services By problem determination services By resource reservation services By resource usage services By application monitoring services

RSS - Mathias

OGSA Info architecture skeleton

Approach 1: The Data Warehouse Straight forward: store all data about the Grid status into a huge database or file or … and query it Not realistic: Loading takes time Data occupy space Connections to the warehouse may fail Often information flows as data streams, and queries ask for data streams as output

Approach 2: A “Virtual” distributed data warehouse The Grid Monitoring Architecture (GMA) of the Global Grid Forum distinguishes between: Distributed Consumers of information Distributed Producers of information Directory Service Producers register their supply Consumers register their demand Consumer Producer Monitoring- Application Data Base Sensor Directory Service find/ register GMA separates matching of consumers to producers and delivery of data from producers to consumers

Vocabulary management questions In which language do producers register their supply and consumers their demand XML, Xpath, Xquery Relational, SQL?? Domain specific?? How to create and delete types of publications dynamically How to create new vocabularies and how to advertise and discover them Are Vocabulary transformations supported Synchronization

An example implementation - Relational Grid Monitoring Architecture Publish Tuples Producer application Producer Service Register SQL “INSERT” Registry Service Query Tuples SQL “SELECT” Locate Mediator Send Query Consumer application Consumer Service Receive Tuples SQL “CREATE TABLE” Schema Service Vocabulary Manager An implementation of the GGF Grid Monitoring Architecture (GMA) All data modelled as tables: a single schema gives the impression of one virtual database for VO

R-GMA Registry/Schema: A Virtual Data Warehouse enabler Language of producers and consumers: relational queries (SQL) Vocabulary: Relations in a global schema Consumer DB-Producer Global Schema S DB Stream Producer Sensor V1 V2 . . . Vn V Views on S Registry Query Consumer: poses queries over global schema Producer: has a type (stream p., database p.) publishes relations R1, … ,Rk for every R, registers a simple view V on the global schema

Pub/Sub model WSN Infrastructure Producers Consumers Subscribers Publishers Combined Consumers/Publishers Topics

INFOD pushes the envelop by Beyond WSN - INFOD INFOD pushes the envelop by Specifies an ObjectRegistry (GMA directory) Supports matching of publishers and consumers Allows definition of publication Type schema (Simple Vocabulary Management) Allows more than one Vocabulary Vocabularies are domain specific (R-GMA, NextGrid, SensorNet, …) More control on the publisher side Support creation of messages based on events or even state changes Support publishers in the dissemination of messages Allows subscribers to have more control of what is published

INFOD Message Creation Publishers States Events Messages State changes can cause events which in turn can cause messages to be produced which are then delivered to consumers Not all publishers allow to control the creation of messages based on events or even state Consumers

Summary OGSA information services address the following basic capabilities: p/c matchmaking message delivery Elementary Vocabulary management Additional capabilities are layered (extend) or composed on top of OGSA info OGSA-Info need to address Common interface independent of implementation Either use or abstract existing interfaces from InfoD and WSN Syntactic interoperability Standard or common schema/vocabulary Semantic interoperability

How to materialize this architecture skeleton Need participation from grid projects To produce architecture document Some open Issues: registry/Schema replication, federation, p2p, fine-grained authorization, …. Important to reach consensus on Producer/Consumer interfaces taking into account InfoD and WSN Interface to Schema and ObjectRegistry services? Join OGSA-WG Information design team Send email to OGSA-WG or A.DJAOUI@RL.AC.UK Join InfoD WG