[#JET-143] Extend installpath to be an URI to make ot possible to grab files from other computers - Kenai.com JIRA

jet

Extend installpath to be an URI to make ot possible to grab files from other computers

Created: 25/Jan/12 08:25 AM Updated: 15/Feb/12 02:02 PM

Component/s:

JETBatch

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

Tags:

Description

« Hide

Today installpath may only point to local files. This does not suit all environments.
A nice feature would be to extend installpath to handle different protocols like http, ssh and ftp.

Example

jet.installpath.xxxx=ftp://somecomputer/foo/bar

Use case: Multiplatform testing in an non-nfs-based environment

Sort Order:

[ Permalink | « Hide ]

bernt added a comment - 15/Feb/12 01:49 PM

It would be sufficient that we defined a JAG URI and that only files on hosts with a JAG is reachable.
This could also be utilized to optimize copying, so that if an installpath is defined to point to hostA, then on hostA the copying could be done locally and not through the computer where JETBatch is running.

[ Permalink | « Hide ]

bernt added a comment - 15/Feb/12 02:02 PM

See http://en.wikipedia.org/wiki/URI_scheme#Generic_syntax

Proposal:

<jag-installpath-uri> ::= [jag://<hostspec>/]<path>

<hostspec> ::= <host>[,<hostspec>]

<hostpattern> ::= pattern that matches one or more of the hosts in jet.clientmachines and jet.servermachines

<path> ::= some working path an the given hosts

If jag://<hostspec>/ is omitted, it defaults to the host running JETbatch.

Examples:

jag://*//foo/bar – path is valid on all hosts (e.g. some NFS-mounted directory)
jag://winbox*/Z:/FOO/BAR – useful for some path valid on a set of computers (winbox1, winbox2, windbox3)
jag://onehost//foo/bar – a path valid on only one host