[Iplant-api-dev] agave:// Scheme for Archive Paths

[Dennis Roberts]

No worries. I’ll use the archiveSystem setting.

Thanks,
Dennis

On Jun 13, 2014, at 3:40 PM, Rion Dooley <dooley at tacc.utexas.edu> wrote:

> I apologize…long day.  Job requests accept separate parameters for archivePath and archiveSystem. I just verified with a couple jobs that it was honoring this to different systems. I understand the root of the question, though. The archivePath should accept a URL as well as a path and there isn’t much point for the archiveSystem parameter if we support URL’s. This is primarily an artifact of Foundation and pre-systems support.
> 
> --
> Rion
> 
> 
> 
> 
> On Jun 13, 2014, at 5:23 PM, Dennis Roberts <dennis at iplantcollaborative.org> wrote:
> 
>> I apologize for not checking that, but the job still fails even with another URI referencing a directory that does belong to ipctest. I’ll try Matt’s suggestion.
>> 
>> Thanks,
>> Dennis
>> 
>> On Jun 13, 2014, at 3:06 PM, Rion Dooley <dooley at tacc.utexas.edu> wrote:
>> 
>>> Looks like the message was correct. That file is owned by a different account despite being in the ipctest user’s tree
>>> 
>>> $ files-pems-list -V -S data.iplantcollaborative.org /ipctest/analyses/blarg_bang_quux
>>> Calling curl -sk -H "Authorization: Bearer c12b615895a49d74531bf4b79a892" https://agave.iplantc.org/files/v2/pems/system/data.iplantcollaborative.org//ipctest/analyses/blarg_bang_quux?pretty=true
>>> {
>>>   "status" : "success",
>>>   "message" : null,
>>>   "version" : "2.0.0-SNAPSHOT-rb73c3",
>>>   "result" : [ {
>>>     "username" : "ipcservices",
>>>     "internalUsername" : null,
>>>     "permission" : {
>>>       "read" : true,
>>>       "write" : true,
>>>       "execute" : true
>>>     },
>>>     "_links" : {
>>>       "parent" : {
>>>         "href" : "https://agave.iplantc.org/files/v2/pems/system/data.iplantcollaborative.org//ipctest/analyses/blarg_bang_quux"
>>>       },
>>>       "file" : {
>>>         "href" : "https://agave.iplantc.org/files/v2/media/system/data.iplantcollaborative.org//ipctest/analyses/blarg_bang_quux"
>>>       },
>>>       "profile" : {
>>>         "href" : "https://agave.iplantc.org/profiles/v2/ipcservices"
>>>       }
>>>     }
>>>   } ]
>>> }
>>> 
>>> Let’s get a second opinion just so we feel good about it...
>>> 
>>> $ ils -A /iplant/home/ipctest/analyses/blarg_bang_quux
>>> /iplant/home/ipctest/analyses/blarg_bang_quux:
>>>         ACL - ipcservices#iplant:own   g:rodsadmin#iplant:own   
>>>         Inheritance - Disabled
>>>   C- /iplant/home/ipctest/analyses/blarg_bang_quux/blarg_bang_quux
>>> 
>>> You have admin on that system, so I’d go in and just recursively grant the ipcuser access to his home directory and try again. One small suggest for what it’s worth. I find that when I’m walking through these exercises, it’s helpful to create a different user account so I don’t run into issues like these from previous development work.
>>> 
>>> --
>>> Rion
>>> 
>>> 
>>> 
>>> 
>>> On Jun 13, 2014, at 4:55 PM, Dennis Roberts <dennis at iplantcollaborative.org> wrote:
>>> 
>>>> agave://data.iplantcollaborative.org/ipctest/analyses/blarg_bang_quux
>>> 
>> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.iplantcollaborative.org/pipermail/iplant-api-dev/attachments/20140613/bb69cbf0/attachment-0001.html