[ogsa-wg] Proposed agenda for Nov. 30th call
Hiro Kishimoto
hiro.kishimoto at jp.fujitsu.com
Wed Nov 29 08:02:01 CST 2006
Hi all,
The following is a proposed agenda for OGSA-WG telecon on Nov. 30th.
Thursday from 7am - 9am (CST).
** attention: new international number **
Dial-in numbers for Thursday:
Free: +1-888-452-0308
Intl/Toll: +(210) 234-7446
PIN: 71815
See more information:
- https://forge.gridforum.org/sf/go/wiki1477
Screen share service will be provided.
URL: http://ogsa.glance.net
Session key: 1130
See more explanation:
https://forge.gridforum.org/sf/go/wiki1584
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) Information/data modeling (Ellen and Fred, 40 min)
> Info model & Service Integration
> ================================
> - The group discusses the details of Profile work
> -- THere are diffferences in how the term Profile is actually used between
> different organisaitons such as DMTF, OGF, etc.
> - Tom Maguire proposes to use the BES specification as an exmple and how to
> do serviice integration.
> - Tom outlines the process how DMTF creates profiles
> - How does this impact OGSA-WG as of what to do next?
> -- Two options:
> --- Update the service model in DMTF (which is at best tangential if
> not parallel to OGSA-WG work)
> --- Take the Container model and turn it into a normative specification
> ---- on a service interface and a profiled information model
> -- A new document is added to the list of group deliverables
> --- Information Model Profile: BES Container document, in style of DMTF
> ---- Ellen Stokes, Tom Maguire
> ---- No particular document type, rather a proof-of-concept
> --- Take BES as a protocol specification, and add an information model
> profile as message specification
> --- The document is actually a profile on the Information Model, with
> associated protocol binding documents.
> -- There needs explanation within the OGF community what this document effort
> assumes to produce
> - The group reaches consensus that this said document will probably inform
> the "Information Modelling in OGSA" work effort, or even provide contents
> for this
Ellen will write up first draft before the call.
3) OGSA workflow discussion (Andrew, 40 min)
Minutes from Nov. 10 am F2F
> <ASM> Can we propose that we have multiple approaches and how to do each of these?
> - <AG> Set up a design team to look into this?
> - Do we have consensus for this (design team)?
> -<DS> Should be short lived design team
> - <JU> Don't do the work just figure out what can be done
> - <ASM> Sort out what is out there and what could potentially be done
> - <AG> to lead
> - Initial deadline - preliminary report for January meeting
https://forge.gridforum.org/sf/go/doc14033
4) Wrap up (10 min)
AOB
<*NEXT CALL*>
https://forge.gridforum.org/sf/go/wiki1477
Dec. 4 (Mon) <No call> Management Developer Conference
Dec. 7 (Thu) <No call> GFSG F2F meeting
Dec. 11 (Mon) EGA reference model(Hiro Kishimoto and Paul Strong)
Roadmap document (Chris Jordan)
EMS Arch scenarios document review (Andreas Savva)
Dec. 14 (Thu) Information/data modeling (Ellen and Fred)
OGSA security (Alan Sill and Andrew Grimshaw)
OGSA workflow (Andrew Grimshaw)
<*ACTION ITEMS*>
https://forge.gridforum.org/sf/go/wiki1569
> From Nov. 9 am F2F.
AI-1109am-a: Ellen and Tom will review the error code/faults issue
further with a view to put a proposal forward to DMTF.
> From Nov. 9 pm F2F.
AI.11.09.pm-a: Ellen and Tom to write up a "Information Model
profile document: BES Container"
AI.11.09.pm-c: Andrew to produce a document drafting the definition
of QoS
AI.11.09.pm-d: Andrew to contact the HPCP WG regarding future
involvement to create profile(s) on, e.g. BES, JSDL
etc.
> From Nov. 10 am F2F
AI-1110am-a: Ellen to look into WS-Policy and relationships to
what has been defined so far
Tom to Look at how to avoid overlap with WS-Policy
group
> From Nov. 2nd call.
AI-1102a: Hiro to ask whole group by email if it is OK to have
one-way (presentation only, no discussion)
SML session on future telecon.
> From Oct. 30 call.
AI-1030a: Ellen will contact the DAIS-WG chairs and request they
arrange a review DSP0225
> From Sept. 15 OGSA F2F
AI-0915d: Tom will post BP base faults issue to tracker
> 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 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.
Postponed:
Until next reference model call (Nov. 20):
AI-1023c: Tom volunteered to review Hiro's HPC Cluster use case
slides and make appropriate changes to indicate where the
CIM Profile would fit in and how it would link into the
Reference Model.
AI-1023g: Hiro will look at other parts of slide 5 and identify
further possible refinements of this use case.
Until next EMS call (Nov. 2):
AI-0914a (Andreas Savva): Integrate the simple Data scenario just
presented into the scenarios document
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."
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
----
Hiro Kishimoto
More information about the ogsa-wg
mailing list