Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[ptp-user] Re: Summary for PBS/RM model-def


On Thu, Apr 1, 2010 at 1:40 PM, Albert L. Rossi <arossi@xxxxxxxxxxxxx> wrote:
I would only add that we ought to check out the server stat call Greg mentioned to see what it provides to the proxy.

Greg, do you mean "pbs_statjob"? I understand the documentation that this command return the same information as the user tool "qstat". This is, a list of the attributes of the running jobs.

The problems in using this information for the model-def information is:
- it does not contain the attribute data-type
- it does not list all possible attributes - but only those of running jobs

Thus if no job at all is running one doesn't get any information. And even if jobs are running, valid attributes not set for any of the currently running jobs, wouldn't be discovered.

Roland


*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
"History does not repeat itself, but often it rhymes." (attr. Mark Twain)

----- Roland Schulz <roland@xxxxxxx> wrote:
> Hi,
>
> my understand what we decided for PBS and the RM model definition:
>
> All possible PBS attributes (both standard + resource) are in a
> configuration file, which is stored with the proxy. It is
> in internal configuration file which we don't expect the user to change. By
> not defining it in Java code, but in a configuration file, we make it easier
> to adapt it to other RMs. This configuration file is distributed with PTP
> and uploaded to the server when the RM is uploaded.
>
> The configuration file contains all the information which is contained in
> the attribute definition according to the proxy protocol: Id, Type, Name
> (the name displayed - not necessarily equal to the xml attribute name),
> Description, Default. Additional it should include mapping between the names
> used in the XML and those we want to display. This include the XML attribute
> name  and for data-type enumerated the list of XML values and the displayed
> value.
>
> In the Model-Def phase the content of this phase is sent to the client.
> While this communication wouldn't be needed for PBS (the configuration file
> has to be available on the client to be uploaded to the proxy) it allows the
> java proxy to be adapted easily to RMs which provide a mechanism to discover
> this list of attributes. Since this communication is only happening at
> start-up it doesn't hurt the performance.
>
> We will add to the RM wizard base class (and thus to all RM wizards) a test
> of the proxy connection and this test connection will include the Model-Def
> phase. This way the RM wizard knows about all possible attributes. We also
> add a page to the RM wizard where the user can select which attributes are
> displayed both in the job view and in the run-configuration dialog. The user
> can do this selection both by individually selecting attributes and by
> selecting a predefined template (Abe, Cray, ...).
>
> Because it doesn't make sense to communicate attributes the user does't want
> to display in the job view, the client sends the selection of attributes to
> the proxy using the filter command. For this the filter command is extended
> to allow also filtering of attributes.
>
> Did I understand everything correctly and is this the way we want to go?
>
> Roland
>
> --
> ORNL/UT Center for Molecular Biophysics cmb.ornl.gov
> 865-241-1537, ORNL PO BOX 2008 MS6309




--
ORNL/UT Center for Molecular Biophysics cmb.ornl.gov
865-241-1537, ORNL PO BOX 2008 MS6309

Back to the top