SourceForge : Post

Project: Editor Discussion > REC:OGSA Basic Execution Service v 1.0 > Comments on the draft > List of Posts

Forum Topic - Comments on the draft: (2 Items)

View: as

05/15/2007 7:12 AM

post5822

Comments on the draft

Some suggestions:

* I would suggest adding "SetActivityDocuments" to the BES-Factory operations,
    which would add steering capabilities to the services.

---------------------
* page: 8  -> states terminated and failed could be joined into one. In my opinion 
    there is no big difference between those two, but it would simplify the basic
    state model.

* page: 9 -> figures 2,3 could be improved - arrows are crossing the state borders.

* page: 10 Figure 3 caption could be on the same page as figure itself.

* page: 14 [Stop|Start]AcceptingNewActivities operations could fail to start/stop 
    BES service.

* page: 17, CPUCount, CPUSpeed, PhysicalMemory, VirtualMemory are also defined
    in JSDL (GFD-R.056, 7. Nov. 2005)

* page 19, InvalidRequestMessageFault is described several times during the 
    document - you could just reference to the first description (in section 1.2.1.3)

* page 20, 1.2.3.1 A vector of zero or more EPRs -> what is the purpose of accepting   
    empty set of EPRs?

* page 21, missing header, but this was already reported.

* page 21, 1.2.3.3 last sentance "if the submitter wishes to access..." -> The 
    message of the sentence is not clear to me.

Steven Newhouse

06/26/2007 8:20 AM

post5839

Re: Comments on the draft

> * I would suggest adding "SetActivityDocuments" to the BES-Factory operations,
>     which would add steering capabilities to the services.

The JSDL document has been designed for submission not steering of jobs. If an activity needed to be steered the 'best' 
way of doing this would probably be by providing an activity specific BES-Activity port-type. This has been clarified in
 the document.

> ---------------------
> * page: 8  -> states terminated and failed could be joined into one. In my 
> opinion 
>     there is no big difference between those two, but it would simplify the 
> basic
>     state model.

An actvity that has failed has got into this state by an internal action - due to a missing file, binary, etc. An 
activity in the terminated state has got there through the Terminate activity state. These are very different scenarios 
and deserve a different state.
 
> * page: 9 -> figures 2,3 could be improved - arrows are crossing the state 
> borders.

Fixed.
 
> * page: 10 Figure 3 caption could be on the same page as figure itself.
> 
> * page: 14 [Stop|Start]AcceptingNewActivities operations could fail to start/
> stop 
>     BES service.

Fixed.
 
> * page: 17, CPUCount, CPUSpeed, PhysicalMemory, VirtualMemory are also defined
> 
>     in JSDL (GFD-R.056, 7. Nov. 2005)

Reference added to JSDL document.
 
> * page 19, InvalidRequestMessageFault is described several times during the 
>     document - you could just reference to the first description (in section 1
> .2.1.3)

Not changed... but noted.
 
> * page 20, 1.2.3.1 A vector of zero or more EPRs -> what is the purpose of 
> accepting   
>     empty set of EPRs?

Altered to accetp one or more.
 
> * page 21, missing header, but this was already reported.

Fixed.
 
> * page 21, 1.2.3.3 last sentance "if the submitter wishes to access..." -> The
>  
>     message of the sentence is not clear to me.

Fixed.

Thank you for your comments.

Steven

Return