Mailing-List: contact dev-help@ariatosca.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ariatosca.incubator.apache.org
Date: Wed, 10 May 2017 09:37:04 +0000 (UTC)
From: "Ran Ziv (JIRA)" <jira@apache.org>
To: dev@ariatosca.incubator.apache.org
Message-ID: <JIRA.13070735.1494408977000.175028.1494409024339@Atlassian.JIRA>
In-Reply-To: <JIRA.13070735.1494408977000@Atlassian.JIRA>
References: <JIRA.13070735.1494408977000@Atlassian.JIRA> <JIRA.13070735.1494408977385@jira-lw-us.apache.org>
Subject: [jira] [Created] (ARIA-234) Isolated workflows execution
 environment
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 10 May 2017 09:37:08 -0000

Ran Ziv created ARIA-234:
----------------------------

             Summary: Isolated workflows execution environment
                 Key: ARIA-234
                 URL: https://issues.apache.org/jira/browse/ARIA-234
             Project: AriaTosca
          Issue Type: Story
            Reporter: Ran Ziv
            Priority: Trivial


Workflows in ARIA are currently run from the main process.
This means that any custom workflows code which is executed has its modules etc. remain in memory, and there's no isolation in between user code and the main process.

In standalone-ARIA (i.e. CLI) this doesn't matter much as the process is unique for the workflow execution, however this might affect users of ARIA which consume the workflow engine directly - it'd require them to handle the isolation themselves as opposed to benefiting from having this mechanism built-in in ARIA.

One option to resolve this is to handle workflows similarly to the way we handle operation plugins, and execute the workflow code in a subprocess.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)