airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ajinkya (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AIRAVATA-2147) Improve File Transfer Component
Date Tue, 01 Nov 2016 17:45:59 GMT

     [ https://issues.apache.org/jira/browse/AIRAVATA-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ajinkya updated AIRAVATA-2147:
------------------------------
       Priority: Minor  (was: Major)
    Description: 
Currently, airavata supports scp transfer only. Moving forward we are planning to introduce
SFTP, HTTP and GRIDFTP alongside scp. File transfer module is kind of hard coded for scp only.
Before implementing new protocols, we need to clean up and generalize current implementation
to accommodate further changes as they come.

Also, current design does not support combining different file transfer protocols along the
path. i.e. fetch file using HTTP and send to remote location using SCP and so on.

Please refer below link where we have discussed possible solution
https://docs.google.com/document/d/1fuKqQgtlS1qjmDeGugbIm_lD-0Q40blWH8kSDoq1E4c/edit?ts=5818b806

Please request for access if you do not have enough privileges.

     Issue Type: Improvement  (was: Bug)

> Improve File Transfer Component
> -------------------------------
>
>                 Key: AIRAVATA-2147
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2147
>             Project: Airavata
>          Issue Type: Improvement
>            Reporter: Ajinkya
>            Assignee: Ajinkya
>            Priority: Minor
>
> Currently, airavata supports scp transfer only. Moving forward we are planning to introduce
SFTP, HTTP and GRIDFTP alongside scp. File transfer module is kind of hard coded for scp only.
> Before implementing new protocols, we need to clean up and generalize current implementation
to accommodate further changes as they come.
> Also, current design does not support combining different file transfer protocols along
the path. i.e. fetch file using HTTP and send to remote location using SCP and so on.
> Please refer below link where we have discussed possible solution
> https://docs.google.com/document/d/1fuKqQgtlS1qjmDeGugbIm_lD-0Q40blWH8kSDoq1E4c/edit?ts=5818b806
> Please request for access if you do not have enough privileges.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message