http://www.clusterresources.com/bugzilla/show_bug.cgi?id=67
--- Comment #14 from Simon Toth <SimonT at mail.muni.cz> 2010-07-07 04:11:21 MDT ---
(In reply to comment #13)
> (In reply to comment #12)
> > (In reply to comment #11)
> > > I think I finally understand what you are trying to do. If select is to work we
> > > need to be able to distribute resources such as mem which currently are only
> > > job wide resources instead of node level (contrary to the documentation). Let
> > > me qualify that. It is a job wide resource on the server.
> > >
> > > However, I think it would be better to just store the resource information
> > > directly from each node and not create arbitrary information the way we do with
> > > np. We do not even need to have a server parameter. We can change the pbsnode
> > > structure to store these values.
> >
> > OK I probably need to brush up my English :-)
> >
> > Yes, that is exactly it. You can only request resources for the whole job in
> > Torque. That's OK for resources that have no location (like licenses). Not so
> > much for resources that belong to nodes.
> >
> > The patch is a modification of the pbsnode structure (two resource attributes).
> > The server parameters are just a convenience, but the whole point of the patch
> > is to be able to specify resources, that are not reported by the nodes. This is
> > extremely useful because it allows admins to very quickly specify new counted
> > resources (for example: disk space, special hardware...).
>> I see the utility in administrators having the ability to just set values for
> resources which may not be reported by the nodes. But how do you attach a value
> to a specific node with this syntax?
Using qmgr:
set node (some_node) resources_total.(some_resource) = (some_value)
example:
set node clusterNode123 resources_total.ncpus=4
--
Configure bugmail: http://www.clusterresources.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.