[Swift-devel] simple executable staging

[Michael Wilde]

I like the idea of executable staging. I feel that while it can start 
small and simple, it should eventually encompass these things in a clean 
elegant model:

- versioning of apps and connecting that back to provenance
- some way to specify app version from app() to tc.data
- some notion of "package" for namespace management
   (we should re-examine the old VDL concept of namespace::name:version 
as a general name specification for app and proc names.
- some way to manage the set of app() declarations that specify the 
"entry points" into an application
- management of app PATHs and install dirs
- retaining of installed apps (vs copy every time) - both should be possible
- some connection to / generalization of ADEM, including both binary and 
src/build installs

On 4/13/09 8:00 AM, Ben Clifford wrote:
> You can do it now without too much hassle but its not as beautiful as it 
> could be. I thought I had added an example to the userguide but turns out 
> I haven't.
> 
> To do it now, make the analysis script an input data file and launch it 
> using /bin/sh (so /bin/sh is what does into the tc.data file, not your 
> actual application).
> 
> Some (?skenny) does similar stuff with a script Rinvoke (that is mapped in 
> tc.data) that launches R on an input script.
> 
> But I'd like that to look more elegant.
> 
> On Mon, 13 Apr 2009, Glen Hocky wrote:
> 
>> This could be potentially very useful for data analysis esp. if the analysis
>> were performed with standard tools (e.g. perl, python, awk and gnuplot). If
>> you could make simple changes to your analysis script and then push the data
>> and analysis tools out for number crunching that would be great.
>>
>> Ben Clifford wrote:
>>> I've seen enough simple (conceptually, not in run size) uses of Swift (2)
>>> and heard enough from OSG Engage people about it being useful that I think
>>> Swift should have an option to stage an executable instead of finding it
>>> remotely.
>>>
>>> This seems more useful in some fields and less so in others (for example,
>>> where people are writing numeric code in C and so have few library
>>> dependencies).
>>>
>>> It can be done in Swift in a round-about way at the moment, but I think it
>>> should be better supported.
>>>
>>>   
>> _______________________________________________
>> Swift-devel mailing list
>> Swift-devel at ci.uchicago.edu
>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>>
>>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel