26 Sep
2006
26 Sep
'06
2:34 a.m.
Hi all,
The following is a proposed agenda for OGSA-WG telecon on Sept. 28th
Thursday from 8:30am - 10:30am (CDT).
Dial-in numbers for Thursday:
Free: +1-888-452-0308
Intl/Toll: +1-484-644-0505
PIN: 71815
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: 0928
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 (if available)
Action Items status review (see the bottom of this email)
Agenda bashing
2) OGSA roadmap v1.1 status update (Chris Jordon, 30 min)
> From Chris Jordan's email:
> I had some issues with Word destroying my latest draft of the
> document, but I've uploaded a less-recent version with some schedule
> and status updates. It is incomplete, but I'm mostly interested at
> this point in feedback on how I'm currently handling documents which
> have been released as GFDs and which don't have definite plans for
> future versions yet.
>
> So if you'd like to discuss the roadmap document in todays call,
> please take a look specifically at the OGSA Architecture and glossary
> sections, along with other documents in a similar state, such as JSDL
> 1.0. Not all documents have updated status in this version, but I
> left track changes on so you can see what I have updated in this
> version.
>
> Latest roadmap draft:
>
> https://forge.gridforum.org/sf/go/doc13733?nav=1
Chris will fix broken draft and upload it to gridforge
before the call.
3) Security Profile final review (Takuya, 60 min)
Takuya will revise two security profiles before the call.
4) Wrap up (10 min)
AOB
<*NEXT CALL*>
https://forge.gridforum.org/sf/go/wiki1477?nav=1
Oct. 2 (Mon): Information/data modeling
Oct. 5 (Thu): Security
Oct. 9 (Mon): EGA reference model, OGSA roadmap
Oct. 12 (Thu): <TBD>
<*ACTION ITEMS*>
https://forge.gridforum.org/sf/go/wiki1569?nav=1
> From Sept. 21 call.
AI-0921a: Andreas to ask Greg to setup a tracker for change requests
to the OGF template document.
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-0921f: Dave S to ask Richard C to put the security topic
on the agenda of the first Interoperability call and to
also ask that the teleconference announcements be sent to
the OGSA list
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-0914b (D Snelling, D Merrill): Set up an OGSA Security design
team
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