Return-Path: X-Original-To: apmail-oodt-dev-archive@www.apache.org Delivered-To: apmail-oodt-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 0656618328 for ; Tue, 29 Sep 2015 16:59:10 +0000 (UTC) Received: (qmail 99874 invoked by uid 500); 29 Sep 2015 16:59:00 -0000 Delivered-To: apmail-oodt-dev-archive@oodt.apache.org Received: (qmail 99840 invoked by uid 500); 29 Sep 2015 16:59:00 -0000 Mailing-List: contact dev-help@oodt.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@oodt.apache.org Delivered-To: mailing list dev@oodt.apache.org Received: (qmail 99827 invoked by uid 99); 29 Sep 2015 16:59:00 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Sep 2015 16:59:00 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 9FA97C0252 for ; Tue, 29 Sep 2015 16:58:59 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.12 X-Spam-Level: X-Spam-Status: No, score=-0.12 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 4uh1nx89wZTI for ; Tue, 29 Sep 2015 16:58:51 +0000 (UTC) Received: from mail-pa0-f42.google.com (mail-pa0-f42.google.com [209.85.220.42]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id F260C20596 for ; Tue, 29 Sep 2015 16:58:50 +0000 (UTC) Received: by pacex6 with SMTP id ex6so11353001pac.0 for ; Tue, 29 Sep 2015 09:58:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=user-agent:date:subject:from:to:message-id:thread-topic:references :in-reply-to:mime-version:content-type:content-transfer-encoding; bh=qwtwbx2ZpAzfehwtcTnZ5QMBhb2Cu5BFjiov1YhmmkU=; b=iFVf7UR5Oc2XiMJ5MVYBU7bgxNFw97hEeulZ93Na0mjUdE9eKz3avR4SdFcLtGVCp4 vIWDAiRJILuRFoYgqKElsDDbc0UpcU9WeLR5gGgQBDKMEalodCkRxwm5VEWkEOYeptxk ZBZ+QgOpkZ6UqDm76J29MszlpYcTEvNVWTMhvpfusLW6uJTZsyxUo3MuQ3SNHxzkW84R Q8ahRceNGsQO8gvR+aWb8FSg3AFtMtqJfAVMyu0H75H+Hp6Ep1AJS5c2R/DiMW4xjD4B nCq27VsfMr+mpcbeKzLeGPyYPdti8wkjgwWucn91xSMdFVgzVCO/f27Br4chrW9a5wIu bWMQ== X-Received: by 10.66.141.42 with SMTP id rl10mr34066912pab.18.1443545930606; Tue, 29 Sep 2015 09:58:50 -0700 (PDT) Received: from [137.78.80.81] ([137.78.80.81]) by smtp.gmail.com with ESMTPSA id la4sm26549054pbc.76.2015.09.29.09.58.47 for (version=TLSv1/SSLv3 cipher=OTHER); Tue, 29 Sep 2015 09:58:49 -0700 (PDT) User-Agent: Microsoft-MacOutlook/14.5.5.150821 Date: Tue, 29 Sep 2015 09:58:41 -0700 Subject: Re: file staging question From: Chris Mattmann To: Message-ID: Thread-Topic: file staging question References: <49ddae7c5bc14dcaaf57cc5f40f2756f@aplex01.dom1.jhuapl.edu> In-Reply-To: <49ddae7c5bc14dcaaf57cc5f40f2756f@aplex01.dom1.jhuapl.edu> Mime-version: 1.0 Content-type: text/plain; charset="UTF-8" Content-transfer-encoding: quoted-printable No problem Val. The fileStaging feature was sort of half baked, however it does work and here is the basic concept behind it. If you have files in your CAS-PGE job that need to be copied from controlled access storage and staged into the job directory for the running CAS-PGE job, the fileStager is the way to do it. You give it a FM query that defines what files to select, and then it uses the File Manager configured data transferer to copy the file(s) from controlled access storage to the PGE job working dir. Another way to accomplish this is simply in your CAS-PGE exe block and cmd blocks is to add a cp or remote staging command (rsync, scp, etc.) that accomplishes the same thing. Cheers, Chris =E2=80=94 Chris Mattmann chris.mattmann@gmail.com -----Original Message----- From: "Mallder, Valerie" Reply-To: Date: Tuesday, September 29, 2015 at 9:51 AM To: "dev@oodt.apache.org" Subject: file staging question >Hi All, > >I have a question related to the file staging feature in a PGE Task. >Basically, how are you using this feature and what exactly does it do for >you? > >Does it just move some files from one place to another? If so, does the >destination directory have to exist or does it get created? And, does >the destination directory structure need to be the same as the source >directory structure? > >When does the 'staging' take place? Does it execute before the >section of the PGE? > > >Thanks, >Val > >P.S. I have read every line of ever file in OODT that contains the word >'staging' and it is still not clear to me what this feature actually does >or how I can configure my PGE config file to use it. But, I did find >some totally awesome documentation in the curator J But, it made it >sound like the directory you set up as your 'staging' directory is the >directory that files get ingested from. Whereas, I was under the >impression that the directory you specify as your directory is >the directory that files get ingested from. So, it was confusing. L >Wonderfully thorough documentation, just confusing for my case. > > >Valerie A. Mallder > >New Horizons Deputy Mission System Engineer >The Johns Hopkins University/Applied Physics Laboratory >11100 Johns Hopkins Rd (MS 23-282), Laurel, MD 20723 >240-228-7846 (Office) 410-504-2233 (Blackberry) >