airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nipun Udara (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRAVATA-1041) [GSOC] Porting EC2 support in new airavata
Date Mon, 03 Mar 2014 06:48:20 GMT

    [ https://issues.apache.org/jira/browse/AIRAVATA-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13917779#comment-13917779
] 

Nipun Udara commented on AIRAVATA-1041:
---------------------------------------

Hi all

According to what I found from the preliminary study, Airavata  EC2 provider in the GFac backend
allows airavata to use amazon clouds ,allows user to do EC2 instance managment using XBaya
GUI including launching  ,terminating and monitor instances and compose workflows in an AMI.
 EC2 provider allows to add EC2 hosts, register applications installed in AMI as an application
in airavata. The main components in  gfac-ec2 module, EC2provider class which is resposible
for EC2 job execution and termination , AmazonSecurityContext class to add support for multiple
security context. I would be grateful if you can let me know more about the project requirements.


Regards 
Udara

> [GSOC] Porting EC2 support in new airavata
> ------------------------------------------
>
>                 Key: AIRAVATA-1041
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-1041
>             Project: Airavata
>          Issue Type: Improvement
>          Components: Airavata Orchestrator, GFac
>            Reporter: Lahiru Gunathilake
>
> After moving to new airavata-data-model and new orchestrator we are not currently supporting
EC2 job submission or monitoring.
> So we want to support EC2 job registering, submission and monitoring with Airavata.
> After the successful project users should be able to use the airavata-client and register
an EC2 job with registry and submit a project and monitor the status. Project owner should
write a working sample with above functionality.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message