29 Sep
2006
29 Sep
'06
3:08 a.m.
Hi all,
The following is a proposed agenda for OGSA-WG telecon on Oct. 2nd
Monday from 5pm to 7pm (CDT).
The dial-in number for Monday;
US: +1 718 3541071 (New York) or
+1 408 9616509 (San Jose)
UK: +44 (0)207 3655269 (London)
Japan: +81 (0)3 3570 8225 (Tokyo)
PIN: 4371991
See more information:
- https://forge.gridforum.org/sf/go/wiki1477?nav=1
Screen share service will be provided.
URL: http://ogsa.glance.net
Session key: 1002
See more explanation:
https://forge.gridforum.org/sf/go/wiki1584?nav=1
1) Early discussion (20 min)
Note taker assignment
Roll call
Telecon minutes approval (Sept. 25)
- https://forge.gridforum.org/sf/go/doc13903?nav=1
Action Items status review (see the bottom of this email)
Agenda bashing
2) Information/data modeling Xquery (Ellen, 30 min)
Minutes from GGF18:
> generate 3 to 5 queries that might be issued; would like to use as a
> starter set for usefulness of XML document and to show how it would
> look like in XQuery.
3) Separation of service/info model (Tom, 30 min)
Minutes form Sept. 25:
> - Another open issue is how does the Information Model work (in
> context of DMTF) comes together with the EGA reference model
> (dags).
> - A possible viewpoint is that the EGA Reference Model is the
> overarching model:
> - With specific/concrete stuff mapping to CIM
> - But some more abstract stuff do not map to CIM easily
> - There is some more abstract work in the SMIS space and this
> will end up at some point in DMTF schema
> - So the DMTF might be an eventual consumer for some of this work
>
Tom will send a note to the list (to: Ellen S and Fred M)
on why the current separation of service/info model may
not be quite right.
4) Removal of container model from BES spec appendix (Ellen, 10 min)
Ellen's email:
> The intent of this appendix is to provide the container model as an
> 'informational' appendix so it can be submitted to DMTF as concrete
> proposal for inclusion in the DMTF CIM and a context for why a container
> model is necessary.
>
> The inclusion of the model in the BES spec does not imply that OGSA must
> implement this CIM container model to implement BES; it is merely an
> abstraction for a general container model where BES can provide context
> for the need and implementation of a specific container model. If this
> point doesn't come across in the appendix text, I have no problem
> modifying the text.
5) Wrap up (10 min)
AOB
<*NEXT CALL*>
https://forge.gridforum.org/sf/go/wiki1477?nav=1
Oct. 5 (Thu): Security, secure channel profile review
Oct. 9 (Mon): EGA reference model, OGSA roadmap
Oct. 12 (Thu): <No call?>
Oct. 16 (Mon): Information/data modeling
Oct. 19 (Thu): Security, secure channel profile review
Oct. 23 (Mon): EGA reference model, OGSA roadmap
<*ACTION ITEMS*>
https://forge.gridforum.org/sf/go/wiki1569?nav=1
> From Sept. 25 call.
AI-0925a: Hiro to setup wiki page with names of people who have
expressed interest in the security team
AI-092625b: Jem to pull definitions together and produce a new
merged first draft.
- Send a mail to the ogsa list about this work
- Set Oct. 9 as the target for the first Glossary draft
AI-0925c: Hiro to ask Alan Clark to ask EGA TC member who want to
contribute to join the OGSA list and this convergence work. -
Members may have changed but organizations have not
AI-0925d: Paul Strong to send EGA Glossary MS-Word file to Jem
Treadwell
AI-0925e: Hiro to talk with Andrew Grimshaw and Mark Morgan and
bring back a concrete proposal for the HPC Profile use
case as a convergence candidate.
AI-0925f: Hiro to talk with Ellen Stokes and add more items in DMTF
register in the context of this convergence work
AI-0925g: Tom will send a note to the list (to: Ellen S and Fred M)
on why the current separation of service/info model may
not be quite right.
> From Sept. 21 call.
AI-0921b: Security members to discuss the BoF proposal(s) further
- For example, one outcome could be some standards
activity to mirror CAOPS activities and tie-in to OGSA
AI-0921c: Dave S (as Standards VP) to talk to the next
Security AD (when one is selected) about the Security Area
task list.
AI-0921d: Dave S to collect additional material in order to identify
security issues better.
- (AI-0921e is an issue instance)
AI-0921i: Dave S to provide an agenda for the next security call.
- Draft agenda items for Oct. 5th:
- What needs to be done to achieve simple interop
generally and to bootstrap more
- Profile to get authentication information from a
secure channel for authentication
- Profile for other methods to get authentication
informatin for authorization
> From Sept. 15 OGSA F2F
AI-0915a: (A Savva, S McGough): Set up a telephone conference to
collect workflow (BPEL) experience
AI-0915b: Ellen to check the status of the items on the
DMTF work register: report which have been done, and what
DMTF is doing for the rest.
AI-0915c: Ellen to propose new text to update the DMTF register
AI-0915d: Tom will post BP base faults issue to tracker
AI-0915e: Hiro to talk with OGF Editor to start an errata process
> From Sept. 14 OGSA F2F
AI-0914a (Andreas Savva): Integrate the simple Data scenario just
presented into the scenarios document
AI-0914f (Fred Brisard and Hiro Kishimoto): Fix the location of the
next F2F and inform the group vial the mailing list
> From GGF18 EMS session (Sept. 13)
AI-0913a: Andreas to update function names of BES.
AI-0913b: Andrew to write-up a couple of such JM functionalities
(short paragraph for each, e.g. time constraint as JSDL
extension.)
AI-0913c: Andreas to add another scenario to use this “terminate”
method of activity interface.
AI-0913e: Andreas to separate un-deployment as a separate scenario.
AI-0913f: Andreas to describe relation between ACS and CDDLM.
AI-0913g: Donal to provide his proposal on
"ActivityExecutionCandidate."
> From Sept. 7 call
AI-0907b: Takuya will search for an external reliable source of
strong (or deprecated) ciphers to reference.
AI-0907c: Andreas will revise the explanatory text and send the new
version to Takuya.
AI-0907d: Takuya will update the documents and issue a final call
on the list. (Probably during GGF18.)
> From Aug. 31 call
AI-0831e: (A Savva) Talk to ACS working group for refining this
scenario.
AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch
Scenarios document
> From Aug. 17 call
AI-0817a: Dave Berry and Jay Unger will approach groups (GIN,
Globus, etc) that have implemented practical grids and
start a discussion on how they handle data:
- how data is treated as a resource that can be scheduled
- how transfers are modeled
- how files are advertised
- how applications find files (query, by knowledge,?)
(Due Oct. 9)
> From Aug. 3 call
AI-0803e: Jun will provide an example of the CDL mechanism and why
using ID/IDREF is not a good idea.
AI-0803f: Jun will update the CDL document to remove the Environment
variables
> From July 20 F2F
- EGR-WG (Ravi) will contact Geoffrey Fox and invites him to
contribute use cases.
- Andreas to go through the minutes and formulate a reply mail to
Geoffrey on each artifact covered in these minutes.
----
Hiro Kishimoto