Return-Path: X-Original-To: apmail-airavata-dev-archive@www.apache.org Delivered-To: apmail-airavata-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 07E5A1087E for ; Mon, 13 Jan 2014 17:15:50 +0000 (UTC) Received: (qmail 53678 invoked by uid 500); 13 Jan 2014 16:16:09 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 52791 invoked by uid 500); 13 Jan 2014 16:14:40 -0000 Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airavata.apache.org Delivered-To: mailing list dev@airavata.apache.org Received: (qmail 52419 invoked by uid 99); 13 Jan 2014 16:14:06 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Jan 2014 16:14:06 +0000 Received: from localhost (HELO [10.0.1.4]) (127.0.0.1) (smtp-auth username smarru, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Jan 2014 16:14:06 +0000 Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) Subject: Re: Predefined parent working directory for jobs From: Suresh Marru In-Reply-To: Date: Mon, 13 Jan 2014 11:14:03 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <98D718CF-FAC7-46EE-BBA3-BBDAACC85F2D@apache.org> References:

To: Airavata Dev X-Mailer: Apple Mail (2.1827) Saminda, Lahiru, Why not use the staticWorkingDirectory option within Application = Deployment Description [1]? The intention of this option was, within the = provider, if this is provided, it ignores the scratchWorkingDirectory = and always uses a static working directory location.=20 Also, if I re-read Saminda=92s original request, is it not the normal = GFac behavior? I mean, within the specified directory = scratchWorkingDirectory=3Dfoo on host A and scratchWorkingDirectory=3Dbar = on hostB, all new sub-directories will be created. What is the precise = difference from this behaviour?=20 Suresh [1] - = https://svn.apache.org/repos/asf/airavata/trunk/modules/commons/gfac-schem= a/src/main/resources/schemas/ApplicationDeploymentDescription.xsd On Jan 13, 2014, at 9:53 AM, Lahiru Gunathilake = wrote: > Hi Saminda, >=20 > You can do this easily by writing another Handler and make sure you = call this handler after AppDescriptorCheckHandler. You can have = properties in your handler configuration and read those properties and = configure different hosts with different base directory locations. So = your handler configuration could looks like this. >=20 > > > > > > =20 > > With handler properties you do not have to hard-code the host specific = directories or create another configuration file. >=20 > Hope this helps ! >=20 > Regards > Lahiru >=20 >=20 > On Fri, Jan 10, 2014 at 3:35 PM, Saminda Wijeratne = wrote: > A specific gateway will have access to the directory location "foo" in = a certain remote host A. Therefore the gateway would like to have all = the working directories for the jobs running in remote host A to be = located inside "foo". Similarly for jobs running in remote host B, all = the working directories should be created inside the directory location = "bar" of which the gateway has access. >=20 > The reason why the working directories needs to be located in = locations accessible to the gateways is because the gateway may perform = manual data transfer. >=20 > Thanks, > Saminda >=20 > On Fri, Jan 10, 2014 at 2:04 PM, Raminder Singh = wrote: > Hi Saminda, >=20 > Do you want all the jobs should use same working directory? = AppDescriptorCheckHandler in GFAC handles working directory, = input-output directory in GFAC. You can control these configuration by = customizing this input handler. Please describe the use case and i will = be able to provide better input.=20 >=20 > Thanks > Raminder >=20 > On Jan 10, 2014, at 1:14 PM, Saminda Wijeratne = wrote: >=20 >> Hi Devs, >>=20 >> I want the parent directory of each working directory of the jobs to = be a predefined path defined for each remote host. What is the easiest = way to do this? >>=20 >> Thanks, >> Saminda >=20 >=20 >=20 >=20 >=20 > --=20 > System Analyst Programmer > PTI Lab > Indiana University