headers
Peter Tröger | 7 Jul 2010 00:16
Picon

Re: Minutes from Conference call - Jun 23th

Hi,

>> 2. Monitoring jobs not submitted by DRMAA - final decision
>
> - Important to be able to obtain information about non-DRMAA
>  jobs which have not ended.
>
> - Desirable to obtain information about non-DRMAA jobs which
>  have recently ended, where "recently" is DRM-defined.
>
> - Importance (and ability to obtain) information about jobs
>  submitted by others unclear.  Agreed that if there is support
>  for obtaining information about other's jobs, must support a
>  filter to limit to current user's jobs.
>
> - Desirable to obtain information about non-DRMAA jobs using
>  APIs similar to those used for jobInfo.  Use Dictionary type
>  to support DRM-specific info.

After some thinking, I decided to put that into the JobSession  
interface:

=== snip ===
interface JobSession {
  readonly attribute string contact;
  readonly attribute string sessionName;
  Job getJob(string jobId);
  sequence<Job> getSessionJobs(JobInfo filter);
  sequence<Job> getAllJobs(JobInfo filter);
  Job runJob(in DRMAA::JobTemplate jobTemplate) raises (???);
(Continue reading)

Permalink | Reply | 5 comments |
headers
Peter Tröger | 7 Jul 2010 00:19
Picon

Re: Conference call - Jun 23th - 19:00 UTC

Oh wow, I missed this one. Seems like we have a dedicated job  
monitoring part in the MonitoringSession now - which is good. I wonder  
how the current JobSession design maps to this. Good topic for the  
call ....

Best,
Peter.

Am 23.06.2010 um 22:20 schrieb Daniel Templeton:

> As promised on the call, here's the summary of the monitoring  
> discussion.  Please add your comments and corrections.
>
> o The monitoring session is should provide parallel functionality to  
> the job session's job monitoring for monitoring all jobs in the  
> cluster.
> o The job monitoring capability for the monitoring session should  
> support a query filter
> o The job monitoring capability for the monitoring session will  
> return a set of job objects that contain a set of core information  
> and a dictionary of optional information that will be "standardized"  
> through the drmaa.org site.
> o The job monitoring capability should be able to return jobs from  
> any/all users.
> o The DRM or DRMAA implementation is at liberty to restrict the set  
> of returned jobs based on site or system policies, such as security  
> settings.
> o The job monitoring model will assume that the DRM system has three  
> job information states: running, buffered, purged.  Only information  
> for jobs that are still running or are still held in the buffer of
(Continue reading)

Permalink | Reply | 0 comments |
headers
Peter Tröger | 7 Jul 2010 10:07
Picon

Call today ?

Hi,

I just wanted to ask around who would join the call today. I promised my son to see the Germans win the soccer
match, and Roger is on vacation. Any problems with deferring the call by one week ?

Best,
Peter.
Permalink | Reply | 2 comments |
headers
Daniel Gruber | 7 Jul 2010 10:22
Picon

Re: Call today ?

Ok, lets have the call next week.

Daniel

Am Mittwoch, den 07.07.2010, 10:07 +0200 schrieb Peter Tröger:
> Hi,
> 
> I just wanted to ask around who would join the call today. I promised my son to see the Germans win the soccer
match, and Roger is on vacation. Any problems with deferring the call by one week ?
> 
> Best,
> Peter.
> 
> --
>   drmaa-wg mailing list
>   drmaa-wg <at> ogf.org
>   http://www.ogf.org/mailman/listinfo/drmaa-wg

--
  drmaa-wg mailing list
  drmaa-wg <at> ogf.org
  http://www.ogf.org/mailman/listinfo/drmaa-wg
Permalink | Reply | 0 comments |
headers
Mariusz Mamoński | 7 Jul 2010 11:00
Picon

Re: Call today ?

Hi,

 For me also it would be better not to have the DRMAA telco today.

Cheers,

On 07/07/2010, Peter Tröger <peter <at> troeger.eu> wrote:
> Hi,
>
> I just wanted to ask around who would join the call today. I promised my son
> to see the Germans win the soccer match, and Roger is on vacation. Any
> problems with deferring the call by one week ?
>
> Best,
> Peter.
>
> --
>   drmaa-wg mailing list
>   drmaa-wg <at> ogf.org
>   http://www.ogf.org/mailman/listinfo/drmaa-wg
>

--

-- 
Mariusz
--
  drmaa-wg mailing list
  drmaa-wg <at> ogf.org
  http://www.ogf.org/mailman/listinfo/drmaa-wg
Permalink | Reply | 0 comments |
headers
AMARNATH, Balachandar | 7 Jul 2010 12:11
Favicon

Condor DRMAA Python

 Is DRMAA  python implementation for condor is available?

With thanks and regards
Balachandar

The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other
than the addressee. Access to this e-mail by anyone else is unauthorised.
If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.
Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent
over public networks. If you have any concerns over the content of this message or its Accuracy or
Integrity, please contact Airbus immediately.
All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you
should take whatever measures you deem to be appropriate to ensure that this message and any attachments
are virus free.
Permalink | Reply | 1 comment |
headers
Enrico Sirola | 7 Jul 2010 12:18
Picon
Gravatar

Re: Condor DRMAA Python

Hello,

Il 07/07/10 12.11, AMARNATH, Balachandar ha scritto:
>  Is DRMAA  python implementation for condor is available?

drmaa-python should work on condor. Find it on
http://drmaa-python.googlecode.com, or install it with

easy_install drmaa

please report bugs in the issue tracker.
I hope it helps,
e.
Permalink | Reply | 0 comments |
headers
Daniel Templeton | 7 Jul 2010 20:52
Picon
Favicon

Re: Minutes from Conference call - Jun 23th

Not sure I like that in the JobSession.  I mean, it *is* the 
*Job*Session, but that would mean writing a monitoring tool would 
require keeping two sessions open.

As for the filtering, it should be possible to filter on any job 
attribute.  We have not yet discussed job owner as a job attribute, but 
now that we've opened the possibility of monitoring other users' jobs, I 
think we have to consider it.  I don't see an issue with it.  If it's a 
security problem, then the DRM is free to hide anything that shouldn't 
be exposed.

And I still don't see any resolution for the problem of getting back a 
list of several hundred thousand jobs.  I think we've had this 
discussion before.  Anyone have notes on what we decided?

Daniel

On 07/06/10 15:16, Peter Tröger wrote:
> Hi,
>
>>> 2. Monitoring jobs not submitted by DRMAA - final decision
>>
>> - Important to be able to obtain information about non-DRMAA
>>   jobs which have not ended.
>>
>> - Desirable to obtain information about non-DRMAA jobs which
>>   have recently ended, where "recently" is DRM-defined.
>>
>> - Importance (and ability to obtain) information about jobs
>>   submitted by others unclear.  Agreed that if there is support
(Continue reading)

Permalink | Reply | 4 comments |
headers
Peter Tröger | 12 Jul 2010 22:04
Picon

Re: Minutes from Conference call - Jun 23th


Am 07.07.2010 um 20:52 schrieb Daniel Templeton:

> Not sure I like that in the JobSession.  I mean, it *is* the
> *Job*Session, but that would mean writing a monitoring tool would
> require keeping two sessions open.

Completely agreed. The method is now in MonitoringSession.

> As for the filtering, it should be possible to filter on any job
> attribute.  We have not yet discussed job owner as a job attribute,  
> but
> now that we've opened the possibility of monitoring other users'  
> jobs, I
> think we have to consider it.  I don't see an issue with it.  If  
> it's a
> security problem, then the DRM is free to hide anything that shouldn't
> be exposed.

Good that we already solved that ;-) We decided earlier to perform  
filtering on the job list from JobSession with the JobInfo structure.
Since the structure already contains the job owner information, the  
problem is solved.

> And I still don't see any resolution for the problem of getting back a
> list of several hundred thousand jobs.  I think we've had this
> discussion before.  Anyone have notes on what we decided?

We also discussed that, and basically agreed on trusting in the OO  
language's scalability capabilities.
(Continue reading)

Permalink | Reply | 3 comments |
headers
Daniel Templeton | 12 Jul 2010 22:19
Picon
Favicon

Re: Minutes from Conference call - Jun 23th

On 7/12/10 1:04 PM, Peter Tröger wrote:
>
> Am 07.07.2010 um 20:52 schrieb Daniel Templeton:
>
>> And I still don't see any resolution for the problem of getting back a
>> list of several hundred thousand jobs.  I think we've had this
>> discussion before.  Anyone have notes on what we decided?
>
> We also discussed that, and basically agreed on trusting in the OO 
> language's scalability capabilities.

That's what I was afraid of.  Let me go stew about that a little, and 
I'll be ready to argue about it on the next call. ;)

Daniel

>
> Best,
> Peter.
>
>
>>
>> Daniel
>>
>> On 07/06/10 15:16, Peter Tröger wrote:
>>> Hi,
>>>
>>>>> 2. Monitoring jobs not submitted by DRMAA - final decision
>>>>
>>>> - Important to be able to obtain information about non-DRMAA
(Continue reading)

Permalink | Reply | 0 comments |

Gmane