Recent changes to bugs

The besserver crashes to JSDL including the "Environment" el

2009-11-06T07:09:40Z

The besserver crashed by the Segmentation fault when the besclient sent the JSDL file that contained the "Environment" element.

---
In __bes__CreateActivity...
ActivityDocument
-JobDefinition
--JobDescription
---JobIdentification
----JobName = Sleep
---Application
----HPCProfileApplication
-----Executable = sleep
-----Argument = 1800
-----Output = /dev/null
-----WorkingDirectory = /tmp
-----UserName = tem
-----Environment
Segmentation fault
----

This problem was found by the project of NAREGI.

wrong status terminating an activity

2008-05-23T15:08:04Z

The expected value when terminating an activity should be 'Terminated' (status 'EXIT' on LSF), but besserver returns 'Finished' (status 'DONE' on LSF)

Activity does not contain any HPCProfileApplication tag

2008-05-22T14:37:57Z

Hi, I'm testing sleep.jsdl sample with your besclient + besserver implementation, where the <HPCProfileApplication> extension should be supported for the job submission. But, when I call the activity service on besclient the <Application> tag seems to be empty. Why?

activity response:

<Response xmlns="http://schemas...">
<ActivityIdentifier>
<Address xmlns="http...">https://192.168.1.106/607</Address>
</ActivityIdentifier>
<JobDefinition>
<JobDescription xmlns="http...">
<JobIdentification>
<JobName>Sleep</JobName>
<JobProject>default</JobProject>
</JobIdentification>

<Application></Application>

<Resources>
<CandidateHosts>
<HostName>acubuntu</HostName>
</CandidateHosts>
<TotalCPUCount>
<Exact>1</Exact>
</TotalCPUCount>
</Resources>
</JobDescription>
</JobDefinition>
</Response>

sleep.jsdl namespace and "-g" argument

2008-05-09T16:28:21Z

Hi Chris, I've tested your besserver and besclient together and I've found some possible troubles in the code and/or in samples deployed with it:

1) sleep.jsdl: the namespace should be changed in <HPCProfileApplication xmlns="http://schemas.ggf.org/jsdl/2006/07/jsdl-hpcpa">

2) the "-g" argument in besserver seems to be mandatory: without it besserver bomb out with a seg fault.

Hope this can help you.

Best Regards
Andrea

Implementation does not follow latest specification of BES

2007-09-04T18:44:54Z

The current BES implementation is based on the WSDL and schema as it was before November 2006. Since then, the schema and WSDL have changed, but the implementation does not reflect this. For example, the XML representation of the state of the activity is different in the specification.

The OGF specification for BES, JSDL, HPC Profile and HPC Profile Application extension can be found on the OGF website here:

http://www.ogf.org/gf/docs/?final

The relevant GFD numbers are 56, 108, 111 and 114.

Add proper user authentication support

2007-09-04T18:35:35Z

Currently, the BES is implemented to run all jobs as a single user id, and uses a built-in password to authenticate requests from the web. This was fine for the prototype, but the BES needs to properly authenticate users using the WS-Security UsernameToken against the UNIX password database (i.e. using getpwnam()). Once a user is authenticated, all operations to the back end resource manager must be performed as this authenticated user, so that jobs are submitted/controlled as this user, etc.