Update of /cvsroot/fura/FuraSrc/Portal/WebApps/ResourcesWeb/doc/userGuide
In directory sc8-pr-cvs17.sourceforge.net:/tmp/cvs-serv8372/FuraSrc/Portal/WebApps/ResourcesWeb/doc/userGuide
Modified Files:
groups2.html
Log Message:
cvssync-20080903232636
Index: groups2.html
===================================================================
RCS file: /cvsroot/fura/FuraSrc/Portal/WebApps/ResourcesWeb/doc/userGuide/groups2.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** groups2.html 16 Jul 2008 06:55:23 -0000 1.2
--- groups2.html 3 Sep 2008 21:27:14 -0000 1.3
***************
*** 79,83 ****
assigned to the group during the group working hours.</li>
<li><b>Use this group as queue</b>: You can configure a group of Agents to work as a queue. If you do, the following group properties (restrictions of queues) will be set automatically. 1) Groups used as queues are always active (their working schedule is 24x7); 2) they can only accept tasks specifically assigned to them; and 3) they can only execute one task at a time --the rest of tasks assigned to one queue will be put in a waiting list, being the next one to be assigned dependent upon the order of arrival and its priority.
! <li><b>Walltime required</b>: This property implies that this group can only accept tasks that have walltime. Task walltime is the maximum amount of time a task (not a microtask) can be running since the moment a resource starts executing it.<br> If you schedule a task, assign it to a queue, and you set a walltime for it, then you now exactly when all the resources in that queue are guaranteed to be done executing that task.
<li><b>Working times</b>: this feature permits defining the timeframe during which the
--- 79,83 ----
assigned to the group during the group working hours.</li>
<li><b>Use this group as queue</b>: You can configure a group of Agents to work as a queue. If you do, the following group properties (restrictions of queues) will be set automatically. 1) Groups used as queues are always active (their working schedule is 24x7); 2) they can only accept tasks specifically assigned to them; and 3) they can only execute one task at a time --the rest of tasks assigned to one queue will be put in a waiting list, being the next one to be assigned dependent upon the order of arrival and its priority.
! <li><b>Walltime required</b>: This property implies that this group can only accept tasks that have walltime. Task walltime is the maximum amount of time a task (not a microtask) can be running since the moment a resource starts executing it.<br> If you schedule a task, assign it to a group used as a queue, and you set a walltime for it, then you know exactly when all the resources in that queue are guaranteed to be done executing that task.
<li><b>Working times</b>: this feature permits defining the timeframe during which the
|
