Re: [ptp-dev] more on RM XML

[Greg Watson <g.watson@xxxxxxxxxxxx>]

On Jan 25, 2011, at 11:26 AM, Albert L. Rossi wrote:

> 
> ----- Greg Watson <g.watson@xxxxxxxxxxxx> wrote:
>> Al,
>> 
>> The problem with your original approach is that you were assuming that the RM is remote and coding this explicitly into the RM configuration. However the remoteness (or otherwise) is a property of the RM instance, not the configuration, so should not be assumed in the commands. Otherwise you'd need a different configuration for a local PBS RM than for a remote PBS RM, for example.
> 
> Yes, I suppose I had assumed a local version to have a different configuration file.
> 
>> 
>> In my view, a property like ${script} should be managed automatically. When ${script} is used in the launch tab configuration, it is assumed to be local, so would expand to the local path of the script. When ${script} is used in a command, it can be either local or remote, so will expand to the location of the script in a staged directory. Copying the script from the local to the staged directory would take place automatically using the remote information obtained from the RM instance.
> 
> Put this way, it seems like script should be a special element of the RM (minOccurs="0") rather than just a property.  

Perhaps that's the best way to go. That way you could add attributes like delete-after-use or something.

> 
>> 
>> A property like ${executable} is slightly different as it needs to refer to the location of the executable on the target system. What is different is that when it is chosen in the launch configuration tab, the file browser must show the files on the target system, rather than the local system. A widget such as <target-browser> or something would probably be sufficient for this.
> 
> Well, the mechanism for this one I believe is already there, no?  It's the Application Tab.  At least that is what I was thinking.  The placeholder ${executablePath} inside the submitted batch script already works this way in PBS.

True. I wasn't sure if there was a case for this on the resources tab or not.

> 
>> 
>> IMHO it's better not to be explicit about copying and deleting files as it will just be an opportunity for someone to misconfigure the RM and leave files accumulating somewhere. Unless you can think of a situation where copy-the-script-prior-to-running-the-command and remove-the-script-after-running-the-command is not sufficient?
> 
> I cannot, but was just trying to design in the eventuality that there was an RM that needed to do something special -- or perhaps had other files that needed to be staged.  Do we need to have a special set of properties, "files", which the RM looks at and copies if it is remote?

That's what I was thinking. Something like:

<file-staging-location>${remote.home}/.eclipse</file-staging-location>
<managed-file create="true" delete-after-use="true">submitScript</managed-file>
<managed-file delete-after-use="false">fileThatShouldBeLeftForSomeReason</managed-file>

The RM would create these files (if necessary) and copy them to the staging location prior to executing any commands. 

Greg