1. OGSA-WG Session #2 Program Execution Services
GGF10 Berlin
March. 10, 2004
3:30-5pm Senate Hall

2. GGF Intellectual Property Policy
All statements related to the activities of the GGF and addressed to the GGF are subject to all provisions of Section 17 of GFD-C.1 ( .pdf), 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-WG Program Execution Services

3. Session Agenda Architecture for program execution related services
High level naming service: WS-naming
Andrew Grimshaw, AD, University of Virginia
OGSA-WG Program Execution Services

4. NB
We use the terms OGSI, GSH, GSR, etc. below. For the next release will update these to the appropriate WS-RF terms.
OGSA-WG Program Execution Services

5. GGF10 Sessions Session Date/Time Room Organizer Program Execution
Mar. 10 Wed
3:30-5pm
Senate Hall
Andrew Grimshaw
Ravi Subramaniam
Data
Information
Mar. 11 Thu
10:30am-noon
Audimax
Jay Unger
Hiro Kishimoto
Management
2-3:30pm
Fred Maciel
OGSA logging system WG - BoF
Mar. 12 Fri
3092
Bill Horn
OGSA-WG Program Execution Services

6. Abstract names (identities)
OGSA “Names”
Distributed systems have traditionally had two or three level name schemes
Human usable names
Abstract names (identities)
Addresses
The mapping (binding) of a higher to lower level is used for either indirection or simplicity. Indirection has been used to implement the “transparencies”: access, location, migration, failure, replication, implementation, behavioral, concurrency, and so on.
OGSA-WG Program Execution Services

7. “Human” names Two forms dominate
“path” names that allow grouping and categorization by directories and sub-directories (DAG’s)
By attribute – e.g., an information service that allows querying for a set of results, e.g., “hosts with more than four processors and BLAST installed”
We already have “attribute” searching in our information services
OGSA-WG Program Execution Services

8. Abstract names & addresses
In OGSI a GSH could be an abstract name – i.e., no location, type, or number information.
GSH’s were bound to addresses – GSR’s.
GSH’s could be long and too complex for humans to manipulate
OGSA-WG Program Execution Services

9. WS-RF and renewable references
Renewable references implement bottom two levels (more or less)
Identity is main remaining issue
OGSA-WG Program Execution Services

10. OGSA-Naming Path names, name service instances
Global, user-friendly name space
e.g.,
/genomes/mouse/pir31.sqf
../fred/datafile
./mpi_tasks/task1
/hosts/san_diego/blue_horizon
Both relative and “absolute”
Absolute is really relative to a “root” directory
Services may have a “root” and a “current working directory”
OGSA-WG Program Execution Services

11. directory services basically a table of <string, GSH>
insert(string, GSH)
lists are multilists, e.g., “file1” may occur twice
<string, GSH>* lookup(string)
string may include “*”, “?”, with escapes
“/” is default path separator
string_list reverse_lookup(GSH)
delete(string)
delete(GSH)
“.” is defined, as may “..”
OGSA-WG Program Execution Services

12. Example – Data Mapped to the Global Namespace
Links directories and files from source location to data grid directory and user-specified name
Generates location independent grid name
Presents unified view of the data across platforms, locations, firewalls, administrative domains, and data owners
OPTIONAL FOR SALES
Windows
2000
Solaris
Linux
Partner
Enterprise
OGSA-WG Program Execution Services
IT Departments
User Departments