airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasandeep Singh (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AIRAVATA-2542) Orchestrate all Airavata components
Date Fri, 29 Sep 2017 19:15:00 GMT

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

Prasandeep Singh updated AIRAVATA-2542:
---------------------------------------
     Attachment: Design.png
    Description: Individual components should be separated and put inside separate VMs. Communication
and configuration of VMs should occur through a single command. Orchestration of components
could be achieved through Docker Swarm, Mesos, or Kubernetes which suits best. Dependencies
and order of deployment should be handled in order to achieve successful deployment of all
components

> Orchestrate all Airavata components
> -----------------------------------
>
>                 Key: AIRAVATA-2542
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2542
>             Project: Airavata
>          Issue Type: Task
>            Reporter: Prasandeep Singh
>            Assignee: Prasandeep Singh
>         Attachments: Design.png
>
>
> Individual components should be separated and put inside separate VMs. Communication
and configuration of VMs should occur through a single command. Orchestration of components
could be achieved through Docker Swarm, Mesos, or Kubernetes which suits best. Dependencies
and order of deployment should be handled in order to achieve successful deployment of all
components



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message