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 8A0B917EAC for ; Fri, 30 Oct 2015 05:43:52 +0000 (UTC) Received: (qmail 61943 invoked by uid 500); 30 Oct 2015 05:43:52 -0000 Delivered-To: apmail-oodt-dev-archive@oodt.apache.org Received: (qmail 61908 invoked by uid 500); 30 Oct 2015 05:43:52 -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 61896 invoked by uid 99); 30 Oct 2015 05:43:52 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Oct 2015 05:43:52 +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 AB4B7C0FEF for ; Fri, 30 Oct 2015 05:43:51 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.9 X-Spam-Level: ** X-Spam-Status: No, score=2.9 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, 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-east.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id tbvZpiOjzk-N for ; Fri, 30 Oct 2015 05:43:40 +0000 (UTC) Received: from mail-io0-f181.google.com (mail-io0-f181.google.com [209.85.223.181]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 64A40439B6 for ; Fri, 30 Oct 2015 05:43:40 +0000 (UTC) Received: by iodd200 with SMTP id d200so69333301iod.0 for ; Thu, 29 Oct 2015 22:43:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=QYoSjqdLKh3KixYUIZ9ePq+qevFj/TE7mbDxh4KV44U=; b=KWBdbJYU8w/BJbW+3F3Al4K3RgG/YbvpSSS2yLoPdxjosvV35Vz7gy2ed6BAauFhsi cL+5IcTw3rg7+8pmxNMTB/7ejDl+caWaurGuSTAUO3NfHHZlZK9d8V+3uD5i4a4QxGV0 awPgUn2K4ra3FVgmRFLWmChMKQDs4H+nk8TBUbwEXchst5QVWDrXWNnfDDOEKolq4YjM R+DlSoD6iUf+HqoNun2v1G+PZxZxJ2PUV+AZ1Lwq1QjVR1GmMJWe8TnyOUSF/xkkuXBK i3j+Z20rHwg2kaRAVV4JgylkX3CnUjK20QDxl7ukZtUONQsaExqZA8IyaKGnW9cVfLDZ K7IA== MIME-Version: 1.0 X-Received: by 10.107.46.142 with SMTP id u14mr7558155iou.165.1446183819998; Thu, 29 Oct 2015 22:43:39 -0700 (PDT) Received: by 10.36.93.70 with HTTP; Thu, 29 Oct 2015 22:43:39 -0700 (PDT) In-Reply-To: References: Date: Thu, 29 Oct 2015 22:43:39 -0700 Message-ID: Subject: Re: OODT File Manager - Airavata Integration Document From: Lewis John Mcgibbney To: "dev@oodt.apache.org" Cc: Airavata Dev Content-Type: multipart/alternative; boundary=001a113ad1bcdf296c05234be81f --001a113ad1bcdf296c05234be81f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Supun, 1) Do you have a test file that you can share and I will try? 2) How long is it taking? 3) Can you make your log available with DEBUG mode turned on so I can see what is going on? Thanks, Lewis On Mon, Oct 26, 2015 at 11:52 AM, Supun Nakandala wrote: > OODT Devs, > > I'm experiencing unacceptable slowness when ingesting some what large > files(>10MB) using OODT file manager. When I check the OODT server side > logs I see multiple attempts to overwrite the same input file again and > again and failing. I am > using org.apache.oodt.cas.filemgr.ingest.StdIngester. > > Any clue on what I am doing wrong here? > > Thanks > > On Mon, Oct 12, 2015 at 4:58 PM, Chris Mattmann > wrote: > > > Yep it can do either. > > > > 1. Use Product.STRUCTURE_HIERARCHICAL for directories. > > This feature works, and also with data movement, but it=E2=80=99s prefe= rred > > to do option 2. > > 2. Manage the hierarchy simply with Product.STRUCTURE_FLAT products, > > but with versioning to place and co-locate the files according to the > > organized hierarchy, and then link them with metadata keys. > > > > Make sense? > > > > Cheers, > > Chris > > > > =E2=80=94 > > Chris Mattmann > > chris.mattmann@gmail.com > > > > > > > > > > > > > > -----Original Message----- > > From: Suresh Marru > > Reply-To: > > Date: Monday, October 12, 2015 at 1:47 PM > > To: , > > Subject: Re: OODT File Manager - Airavata Integration Document > > > > >Thanks Chris this is helpful to get a clarification. The only reason w= e > > >want to do at a service level so we can have more fine grain control > based > > >on users/groups and their roles. We will start by looking at the tomca= t > > >layer and will ask more questions along the way. > > > > > >Paraphrasing Supun: Seems like OODT currently supports files organized > in > > >a > > >flat structure. Any suggestions on how to support data products > organized > > >in hierarchal directories. As an example, say an Experiment has a > Workflow > > >which runs bunch of simulations all organized as inputs and outputs > under > > >a > > >parent experiment. Can we point the file manager to such a organizatio= n > or > > >is it expected that the hierarchy be managed outside (through metadata > key > > >value pairs or otherwise)? > > > > > >Thanks, > > >Suresh > > > > > >On Mon, Oct 12, 2015 at 4:32 PM Chris Mattmann < > chris.mattmann@gmail.com> > > >wrote: > > > > > >> Hey Suresh, > > >> > > >> Sure. Right now I would recommend not trying to do auth/auth > > >> at the File Manager Level, and instead using e.g., Tomcat or > > >> something to set up like an OAuth realm, and doing it that way. > > >> Is there a specific need to lock it down at the service level? > > >> At their core they are XML-RPC, and I think it will be more difficul= t > > >> to implement there than trying to do in an app server that sits > > >> in front. > > >> > > >> Cheers, > > >> Chris > > >> > > >> =E2=80=94 > > >> Chris Mattmann > > >> chris.mattmann@gmail.com > > >> > > >> > > >> > > >> > > >> > > >> > > >> -----Original Message----- > > >> From: Suresh Marru > > >> Reply-To: > > >> Date: Monday, October 12, 2015 at 1:09 PM > > >> To: , > > >> Subject: Re: OODT File Manager - Airavata Integration Document > > >> > > >> >OODT Dev's, > > >> > > > >> >Can we plugin custom authentication to CAS File Manager? I see that > you > > >> >could potentially use the OODT single sign on package and have it > talk > > >>to > > >> >a > > >> >LDAP but wondering if we could do OAuth2 like authentication and > > >> >authorization. > > >> > > > >> >Thanks, > > >> >Suresh > > >> > > > >> >On Tue, Sep 1, 2015 at 12:03 AM DImuthu Upeksha > > >> > > > >> >wrote: > > >> > > > >> >> Hi Chris, > > >> >> > > >> >> Thank you for your feedback. This is a POC level implementation > done > > >>by > > >> >>me > > >> >> and there is a lot of room for improvement. It would be great if > both > > >> >> Airavata and OODT teams can go through the design and decide > whether > > >> >> Airavata can be integrated with OODT File manager. But my idea is= , > > >>yes > > >> >>it > > >> >> is possible. > > >> >> > > >> >> Thanks, > > >> >> Dimuthu > > >> >> > > >> >> On Tue, Sep 1, 2015 at 5:07 AM, Mattmann, Chris A (3980) < > > >> >> chris.a.mattmann@jpl.nasa.gov> wrote: > > >> >> > > >> >>> Great work Dimuthu! > > >> >>> > > >> >>> So this means now Airavata and OODT=E2=80=99s File Manager are i= ntegrated? > > >> >>> :=3D) > > >> >>> > > >> >>> CC/dev@oodt.a.o > > >> >>> > > >> >>> Cheers, > > >> >>> Chris > > >> >>> > > >> >>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++= ++ > > >> >>> Chris Mattmann, Ph.D. > > >> >>> Chief Architect > > >> >>> Instrument Software and Science Data Systems Section (398) > > >> >>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > > >> >>> Office: 168-519, Mailstop: 168-527 > > >> >>> Email: chris.a.mattmann@nasa.gov > > >> >>> WWW: http://sunset.usc.edu/~mattmann/ > > >> >>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++= ++ > > >> >>> Adjunct Associate Professor, Computer Science Department > > >> >>> University of Southern California, Los Angeles, CA 90089 USA > > >> >>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++= ++ > > >> >>> > > >> >>> > > >> >>> > > >> >>> > > >> >>> > > >> >>> -----Original Message----- > > >> >>> From: DImuthu Upeksha > > >> >>> Reply-To: "dev@airavata.apache.org" > > >> >>> Date: Saturday, August 29, 2015 at 1:27 AM > > >> >>> To: "dev@airavata.apache.org" > > >> >>> Subject: OODT File Manager - Airavata Integration Document > > >> >>> > > >> >>> >Hi all, > > >> >>> > > > >> >>> > > > >> >>> >Please find the document [1] that describes the steps followed = in > > >>the > > >> >>> >attempt of integrating OODT File Manager and AIravata. This set= up > > >>is > > >> >>> >currently working on gw77. > > >> >>> > > > >> >>> > > > >> >>> >[1] > > >> >>> > > > >> >>> > > >> >>> > > >> > > https://docs.google.com/document/d/1mr3k_OmgEweeVhJtuMTvofL__v9uPwyWbWr= P > > >> >>>-M > > >> >>> >OFUDw/edit?usp=3Dsharing > > >> >>> > > > >> >>> > > > >> >>> >Thanks > > >> >>> >Dimuthu > > >> >>> > > > >> >>> > > > >> >>> >-- > > >> >>> >Regards > > >> >>> >W.Dimuthu Upeksha > > >> >>> >Undergraduate > > >> >>> >Department of Computer Science And Engineering > > >> >>> >University of Moratuwa, Sri Lanka > > >> >>> > > > >> >>> > > > >> >>> > > > >> >>> > > >> >>> > > >> >> > > >> >> > > >> >> -- > > >> >> Regards > > >> >> > > >> >> W.Dimuthu Upeksha > > >> >> Undergraduate > > >> >> Department of Computer Science And Engineering > > >> >> > > >> >> University of Moratuwa, Sri Lanka > > >> >> > > >> > > >> > > >> > > > > > > > > > -- > Thank you > Supun Nakandala > Dept. Computer Science and Engineering > University of Moratuwa > --=20 *Lewis* --001a113ad1bcdf296c05234be81f--