[Pgi-wg] OGF PGI : Draft PGI Specification

Riedel, Morris m.riedel at fz-juelich.de
Fri Dec 18 06:15:10 CST 2009


Hi Steven,

 thanks for your valuable comments - I put their discussion on the agenda for today.

Take care,
Morris

________________________________________
Von: pgi-wg-bounces at ogf.org [pgi-wg-bounces at ogf.org] im Auftrag von Steven Newhouse [Steven.Newhouse at cern.ch]
Gesendet: Freitag, 18. Dezember 2009 09:44
An: pgi-wg at ogf.org
Betreff: Re: [Pgi-wg] OGF PGI : Draft PGI Specification

All,

Some good progress seems to be being made on the specification and the draft is beginning to become coherent. A few thoughts emerged following a quick read through.

* ChangeActivityState
This reminded me of discussions we had in the late stages of BES. A similar operation was moved in  & out of the draft before finally being removed. There was discomfort as to the amount of influence an end-user agent could have on the underlying state machine. A user could not force a job to execute if it was queued if there were not processes available. With the expanded state model that is now proposed there is more scope for user control - fine. You have the notion of legal and illegal state change requests but I could not see these documented on the state diagram. I would certainly propose changing this to 'RequestActivityStateChange' to make it clear that this is an initiation and that it make take some time for the underlying state engine to change. You effectively acknowledge this in your estimated time to change return value.

I can see it being useful to have a 'this has already been done' option in the return body. I'm not sure how useful any value other than zero effectively is here. To me you are effectively saying this has either been done or you need to set up a notification or a poll to check back to see when it has completed. The estimate itself does not seem to be that valuable...

* Partitioning
The three port types all seem sensibly scoped. I have great concerns about the AGU-JSDL section. I'm not sure if this is just a place holder at the moment. I would be VERY concerned if this AGU-JSDL forks away from the JSDL activity. JSDL has gained considerable traction and is being further developed in the JSDL 2.0 discussions. I would have thought PGI would be better placed supporting a MINIMAL extension to JSDL to support its immediate needs, and feeding the other improvements it could see being needed into the broader JSDL discussions.

* Delegation & Information PortTypes
This must have broader use than just beyond PGI. If there are opportunities to do this why not put these into separate specifications even if they are still done through the PGI-WG.

Cheers,

Steven

Dr Steven Newhouse
EGEE Technical Director
Interim EGI.eu Director
Contact Details: http://cern.ch/Steven.Newhouse


> -----Original Message-----
> From: pgi-wg-bounces at ogf.org [mailto:pgi-wg-bounces at ogf.org] On Behalf
> Of Etienne URBAH
> Sent: 17 December 2009 23:33
> To: Morris Riedel; pgi-wg at ogf.org
> Cc: edges-na3 at mail.edges-grid.eu; lodygens at lal.in2p3.fr
> Subject: Re: [Pgi-wg] OGF PGI : Draft PGI Specification
>
> Morris and all,
>
> I have updated the 'Draft PGI Specification' with version 0.38 at
> http://forge.gridforum.org/sf/go/doc15839?nav=1 with following
> improvements :
>
> -  Exclude internal states.
>
> -  Second level Job states are also mandatory.
>
> -  Inside the 'Submitted' state :
>     - The Execution Service may already allocate resources,
>     - Rename 'Waiting' substate as 'Validated',
>     - Add 'Hold' substate.
>
> Best regards.
>
> -----------------------------------------------------
> Etienne URBAH         LAL, Univ Paris-Sud, IN2P3/CNRS
>                        Bat 200   91898 ORSAY    France
> Tel: +33 1 64 46 84 87      Skype: etienne.urbah
> Mob: +33 6 22 30 53 27      mailto:urbah at lal.in2p3.fr
> -----------------------------------------------------
>
>
> On Thu, 17 Dec 2009, Riedel, Morris wrote:
> > Hi team,
> >
> >    here another update on one action item:
> >
> >> - A - action (Morris): copy strawman rendering doc to drafts
> >
> > Done.
> >
> > The actual draft specification (version 0.37) is now accessible in
> GridForge via:
> > Doucments - Root Folder - Drafts - Specification Direct link:
> >
> http://forge.gridforum.org/sf/docman/do/downloadDocument/projects.pgi-
> > wg/docman.root.drafts.specification/doc15839
> >
> > So far, I kept a copy within the Input Document Section since I
> propose a renaming of the document within drafts to:
> >
> > "Draft PGI Specification"
> >
> > It is neither a strawman document nor a concrete rendering - it's
> just a draft specification from PGI.
> >
> > However, of course, I seek to discuss this tomorrow in the telcon
> with all of you.
> >
> > Your co-chair,
> > Morris
> >
> > ---------------------------------------------------------------------
> -
> > --------------------------
> > ---------------------------------------------------------------------
> -
> > --------------------------
> > Forschungszentrum Juelich GmbH
> > 52425 Juelich
> > Sitz der Gesellschaft: Juelich
> > Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
> > Vorsitzende des Aufsichtsrats: MinDir'in Baerbel Brumme-Bothe
> > Geschaeftsfuehrung: Prof. Dr. Achim Bachem (Vorsitzender), Dr. Ulrich
> > Krafft (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt, Prof. Dr.
> > Sebastian M. Schmidt
> > ---------------------------------------------------------------------
> -
> > --------------------------
> > ---------------------------------------------------------------------
> -
> > --------------------------
_______________________________________________
Pgi-wg mailing list
Pgi-wg at ogf.org
http://www.ogf.org/mailman/listinfo/pgi-wg


More information about the Pgi-wg mailing list