ViewVC logotype

Contents of /nl.nikhef.pdp.dynsched-pbs-plugin/branches/REL-2.2.1/RELEASE

Parent Directory Parent Directory | Revision Log Revision Log

Revision 2197 - (show annotations) (download)
Tue Feb 15 14:53:54 2011 UTC (11 years, 7 months ago) by templon
File size: 5446 byte(s)
update release info.

1 This file contains release notes and a change history for the
2 pbs/torque and maui plugins for the lcg-info-dynamic-scheduler information provider.
3 The notes are most recent first.
5 Release 2.2.1
7 Dependencies changed back to the original set, so that this version's RPM
8 dependencies are compatible with those of previous versions (and also
9 with the lcg-info-dynamic-scheduler-generic package).
11 Release 2.2.0
12 Moved to new repository format and changed RPM name. Rather large changes in two areas. First, in the logFileParser
13 part of the pbsServer.py code. The new "account" field printed in the torque accounting logs broke the old parser,
14 this is fixed in the current release. The second set of changes have to do with how the LiveServer code parses
15 the 'qstat -f' output. When present (recent versions of torque), the code now uses 'startTime' as the start time
16 of the job, and uses the 'euser' and 'egroup' as the user and group of the job. If these fields are not present,
17 the code reverts to the old behavior. Using startTime will give slightly different results, since startTime
18 is present immediately upon job start, whereas walltime (used in the old calculation) is only updated once per
19 mom update interval, meaning there were always a few jobs in the system that were in state "running" but that had
20 no startTime. This will no longer be the case.
22 Three user-visible changes: there are two new job attributes in the "Job" object. One is the walltime used by the job,
23 the other is the 'startAnchor' field which tells you whether the code has used the 'startTime' to find the start time,
24 or has done it the old way by subtracting the walltime used from the current time. These data are both printed
25 by lrmsinfo-pbs. Those two changes are in principle user-visible, but only for those users directly using lrmsinfo-pbs.
26 Finally, vomaxjobs-maui accepts an argument '-k' to provide a key-file to the diagnose command. This is needed for
27 e.g. installations where the diagnose client cmd is on RHEL4 and the maui server is on RHEL5 (different build = different key).
29 Information below this point refers to older versions of the package, under the older naming
30 scheme.
32 Release 2.1.0
33 - Remove support for specifying hostname on command line (savannah bug 35662)
35 Release 2.0.1
36 - fix LICENSE, otherwise no change.
38 Release 2.0.0
39 - uses new lrms.py, otherwise no changes.
41 Release 1.6.1
42 - update documentation and examples to be consistent with 2.0 release
44 Release 1.6.0
46 - some changes to build system (three targets increases aggravation)
47 - some changes to pbsServer classes to assist in debugging.
48 - some changes to vomaxjobs-maui to assist in debugging/testing;
49 also fixed various unreported bugs discovered during testing.
50 - Change mapping of pbs/torque job states in pbs classes; up til now
51 was either queued (Q) or running (any other states). Now we have:
53 From the qstat (torque 2.0.0p4) man page:
55 C - Job is completed after having run (mapped to 'done')
56 E - Job is exiting after having run. (mapped to 'running')
57 H - Job is held. (mapped to 'pending')
58 Q - job is queued, eligible to run or routed. (mapped to 'queued')
59 R - job is running. (mapped to 'running')
60 T - job is being moved to new location. (mapped to 'pending')
61 W - job is waiting for its execution time (mapped to 'queued')
63 Release 1.5.2:
65 pbs package: Fix to vomaxjobs-maui to deal with cases where there is
66 extra 'warning' output near the top of the command output from diagnose -g.
68 Release 1.5.1:
70 fix dependency problems with RPMs.
72 Release 1.5.0
74 in vomaxjobs-maui, adapt to handle MAXPROC specifications like
75 MAXPROC=soft,hard The code reports the 'hard' limit, since
76 this is relevant when the system is not full, and this is when
77 it's needed. Maui uses the soft limit on a full system, but
78 in this case the info provider will drop FreeSlots to zero as
79 soon as jobs remain in the queued state instead of executing
80 immediately.
82 Release 1.4.2
84 in pbsServer.py: included Steve Traylen's patch to deal with jobs for which the
85 uid/gid printed by 'qstat' is not listed in the in running machine's
86 pw DB. This can happen when the CE is not the same physical
87 machine as the actual LRMS server.
89 Estimated Response Time Info Providers (v 1.4.1)
90 ------------------------------------------------
92 This information provider is new in LCG 2.7.0 and is
93 contained in two RPMs, lcg-info-dynamic-scheduler-generic
94 and lcg-info-dynamic-scheduler-pbs. Sites using torque/pbs
95 as an LRMS and Maui as a scheduler are fully supported by
96 this configuration; those using other schedulers and/or
97 LRMS systems will need to provide the appropriate back-end
98 plugins.
100 For sites meeting the following criteria, the system should
101 work out of the box with no modifications whatsoever:
103 LRMS == torque
104 scheduler == maui
105 vo names == unix group names of that vo's pool accounts
107 Documentation on what to do if this is not the case can be
108 found in the file
110 lcg-info-dynamic-scheduler.txt
112 in the doc directory
114 /opt/lcg/share/doc/lcg-info-dynamic-scheduler
116 There is also documentation in this directory indicating
117 the requirements on the backend commands you will need to
118 provide in the case that you are using a different
119 scheduler or LRMS. Tim Bell at CERN can help for people
120 using LSF.


Name Value
svn:keywords Id URL

ViewVC Help
Powered by ViewVC 1.1.28