You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by "Raminderjeet Singh (Created) (JIRA)" <ji...@apache.org> on 2012/03/01 20:23:59 UTC

[jira] [Created] (AIRAVATA-326) Gram and GridFTP ERP's are not populated in XRegistry entries transfer

Gram and GridFTP ERP's are not populated in XRegistry entries transfer
----------------------------------------------------------------------

                 Key: AIRAVATA-326
                 URL: https://issues.apache.org/jira/browse/AIRAVATA-326
             Project: Airavata
          Issue Type: Sub-task
            Reporter: Raminderjeet Singh


Transfered objects does not have Gram and GridFTP Endpoints mapped. In  Gram4 jobs you need to have job type also.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Assigned] (AIRAVATA-326) Gram and GridFTP ERP's are not populated in XRegistry entries transfer

Posted by "Heshan Suriyaarachchi (Assigned) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AIRAVATA-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Heshan Suriyaarachchi reassigned AIRAVATA-326:
----------------------------------------------

    Assignee: Heshan Suriyaarachchi
    
> Gram and GridFTP ERP's are not populated in XRegistry entries transfer
> ----------------------------------------------------------------------
>
>                 Key: AIRAVATA-326
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-326
>             Project: Airavata
>          Issue Type: Sub-task
>            Reporter: Raminderjeet Singh
>            Assignee: Heshan Suriyaarachchi
>             Fix For: 0.4-INCUBATING
>
>
> Transfered objects does not have Gram and GridFTP Endpoints mapped. In  Gram4 jobs you need to have endpoint type also.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (AIRAVATA-326) Gram and GridFTP ERP's are not populated in XRegistry entries transfer

Posted by "Heshan Suriyaarachchi (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AIRAVATA-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Heshan Suriyaarachchi updated AIRAVATA-326:
-------------------------------------------

    Component/s: XRegistry Migration
    
> Gram and GridFTP ERP's are not populated in XRegistry entries transfer
> ----------------------------------------------------------------------
>
>                 Key: AIRAVATA-326
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-326
>             Project: Airavata
>          Issue Type: Sub-task
>          Components: XRegistry Migration
>            Reporter: Raminderjeet Singh
>            Assignee: Heshan Suriyaarachchi
>             Fix For: 0.4-INCUBATING
>
>
> Transfered objects does not have Gram and GridFTP Endpoints mapped. In  Gram4 jobs you need to have endpoint type also.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Closed] (AIRAVATA-326) Gram and GridFTP ERP's are not populated in XRegistry entries transfer

Posted by "Raminderjeet Singh (Closed) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AIRAVATA-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Raminderjeet Singh closed AIRAVATA-326.
---------------------------------------


verified for ultrascan objects
                
> Gram and GridFTP ERP's are not populated in XRegistry entries transfer
> ----------------------------------------------------------------------
>
>                 Key: AIRAVATA-326
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-326
>             Project: Airavata
>          Issue Type: Sub-task
>          Components: XRegistry Migration
>            Reporter: Raminderjeet Singh
>            Assignee: Heshan Suriyaarachchi
>             Fix For: 0.4-INCUBATING
>
>
> Transfered objects does not have Gram and GridFTP Endpoints mapped. In  Gram4 jobs you need to have endpoint type also.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (AIRAVATA-326) Gram and GridFTP ERP's are not populated in XRegistry entries transfer

Posted by "Raminderjeet Singh (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AIRAVATA-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Raminderjeet Singh updated AIRAVATA-326:
----------------------------------------

    Description: Transfered objects does not have Gram and GridFTP Endpoints mapped. In  Gram4 jobs you need to have endpoint type also.  (was: Transfered objects does not have Gram and GridFTP Endpoints mapped. In  Gram4 jobs you need to have job type also.)
    
> Gram and GridFTP ERP's are not populated in XRegistry entries transfer
> ----------------------------------------------------------------------
>
>                 Key: AIRAVATA-326
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-326
>             Project: Airavata
>          Issue Type: Sub-task
>            Reporter: Raminderjeet Singh
>             Fix For: 0.4-INCUBATING
>
>
> Transfered objects does not have Gram and GridFTP Endpoints mapped. In  Gram4 jobs you need to have endpoint type also.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (AIRAVATA-326) Gram and GridFTP ERP's are not populated in XRegistry entries transfer

Posted by "Heshan Suriyaarachchi (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AIRAVATA-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Heshan Suriyaarachchi resolved AIRAVATA-326.
--------------------------------------------

    Resolution: Fixed
    
> Gram and GridFTP ERP's are not populated in XRegistry entries transfer
> ----------------------------------------------------------------------
>
>                 Key: AIRAVATA-326
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-326
>             Project: Airavata
>          Issue Type: Sub-task
>            Reporter: Raminderjeet Singh
>            Assignee: Heshan Suriyaarachchi
>             Fix For: 0.4-INCUBATING
>
>
> Transfered objects does not have Gram and GridFTP Endpoints mapped. In  Gram4 jobs you need to have endpoint type also.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira