Expected meeting output/goal proposal 29 July, 2003 OGSA-WG interim meeting Hiro Kishimoto, Ph.D.
What we agreed at GGF8 Use cases Analyze & Extract Requirements Commercial Data Center Analyze & Extract Requirements (Functions) Data Sharing OGSA-WG Evaluate & Prioritize Mechanism (Services) Data Management Dispatch OGSA-DAI interface DAIS-WG Existing or new WGs
What we agreed at GGF8 Want to breakdown Into two Function requirements High level requirements Important and apparently broadly relevant characteristics of Grid environments and applications Will be described in “OGSA Platform document” Services (implementations) Features and associated behaviors that provide the above functions Will be also described in “OGSA Platform document” Interfaces portType detailing the above services Actual Specifications that will be defined by the other WGs
Taxonomy and Factoring Requirements (Functions) Evaluate and extract Service taxonomy OGSA user’s view Factoring and prioritize Services Broker Service hierarchy OGSA provider’s view Infrastructure CMM OGSI
We would like to add these 2 groups Jay’s OGSA Services Good taxonomy Represents the OGSA user's point of view Service endpoints Core Services Data Services Program Execution Services Resource Management Services Autonomic Services We would like to add these 2 groups
Taxonomy output Identify and grouping services Day 2 am session Domain Specific Services Data Program Resource Autonomic Core Services
Service Factoring What is common functionality across services How things are put together between OGSI and the upper level services (core, data, etc) OGSA-WG need to offer more direction in the lower concept area Guide other groups doing OGSA work Avoid duplication of effort Each group re-discovering/re-defining things in different ways
Factoring Examples CMM and OGSI-Agreement OGSA-DAI GT3 implementation Address the area between OGSI and upper level services OGSA-DAI Trying to define both high level services (e.g., distributed query) and also the low level concepts They are trying to decide what is fundamental and what is not GT3 implementation Represents one factoring between OGSI and its higher level services
Andreas’s Factoring Used Jay's taxonomy as starting point Divided it into two parts Infrastructure Not full-blown services Used as building blocks by higher level services Services Keeps most of Jay's structure Add some extra categories Resource management and Autonomic Adds some services that are present in the use cases/platform. fault handling, etc
Relationship types "Extends" is used to show relations between the higher level services and the infrastructure bits "Extends" in some cases may be better read as "Uses" E.g., accounting "extends“ ogsi-info but probably "uses" "ogsi-storage" Other relationships may also exist
Hierarchy Output Day 2 pm session Program Execution Job Submission Workflow service Job queuing Services Management Discovery Directories Metering Accounting Naming Services CMM OGSI Agreement Service Orchestration Index & Abs.Registry OGSI Info OGSI storage OGSI Infrastructure
Platform Document ToC draft Introduction Use case analysis 2.1 Usecases Description of each usecase 2.2 Functionality requirements List of requirements Service taxonomy Service grouping from user’s point of view Service hierarchy Service grouping from provider’s point of view OGSA services Description of each services