[Pgi-wg] OGF PGI : EMI Execution Service Specification

[Michaela Barth]

Dear all,

Since it was also my task to have a look through the EMI ES 
Specification, here my comments.

* I would back up Etienne, that a chapter referring to Use Cases and 
Requirements would indeed be useful.

* For the ordering I also felt that some things would have been more 
useful earlier on, especially the current chapter 8 "Resource and 
Activity representation and the current chapter 10 "Security 
Considerations" (especially with 10.3 therein)


* The EMI ADL (chapter 9) would need a motivation why to start here from 
scratch and not just define an extension to something similar already 
existing.


* The name of the Resource subelement NetworkInfo (9.3.5.3) could be 
chosen better, something like NetworkInfoInternal to emphasize that the 
network connection inside the computing element is meant.

* 9.3.5.13 Benchmark is refering to BenchmarkType. That one is missing. 
Shouldn't Benchmark be a sub-element of BenchmarkType?

* 9.3.6 RunTimeEnvironment is generally a sensible idea, but will be 
heavy on the service descriptions. This maybe needs more discussion with 
reference to 10.2.

* The lines in Figure 1 should not go through the text.

* The text is currently very hard to read, it needs at least a native 
speaker and a grammar nazi to fill in all the missing the, a, to,,,., 
and get rid of additional spaces. Some of the sentences are in best case 
misleading.

My favorites were:
7/49 XML Validation: Chech whether XML is a valid XML document (i.e. 
well-formed and such like)
30/45, 9.3.5.8:
If it is not defined that the user not interested to access session 
directory remotely (default is false).
--> .. it is assumed that the user is... ?
9.3.5.2 Platform:
Multiplicity is one or one.



Minor things:
p 7/45: Extensions marked as "must" must be understood, ..
-> MUST
p25/45: "critical": it is  hard requirement. The service MUST provide 
this feature, satisfy the requirement otherwise the activity must be 
rejected (during the validation phase)
--> "critical": it is a hard requirement. The service MUST provide this 
feature and satisfy the requirement, otherwise the activity MUST be 
rejected (already during the validation phase).

p 19/45: In case of renewal the server must re-use the  previous 
delegation ID submitted in the request.
--> In case of renewal the server MUST re-use the previous DelegationID 
submitted in the request.


End of chapter 7.1: Missing internal reference


Cheers,
Michaela

-- 
Michaela Barth
EGI.eu Coordination of Interoperations between NGIs and with other DCIs
PDC Center for High Performance Computing
CSC School of Computer Science and Communication
KTH Royal Institute of Technology
SE-100 44 Stockholm, Sweden

Tel: +468-790 7891
SIP: caela at kth.se
XMPP: caela at kth.se