You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ariatosca.apache.org by "Ran Ziv (JIRA)" <ji...@apache.org> on 2017/05/12 15:23:04 UTC
[jira] [Updated] (ARIA-255) Reusable non-Python operation scripts
[ https://issues.apache.org/jira/browse/ARIA-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ran Ziv updated ARIA-255:
-------------------------
Description:
Plugins (operations, workflows) in ARIA currently have to be implemented in Python.
ARIA already has the execution-plugin which knows how to execute arbitrary scripts for running operations. However, sharing such scripts across service-templates won't work at this time, since the execution-plugin only looks for the scripts in the service-template's resources.
One way around this would be to allow managing global resources (see linked JIRA issue), but a better way would probably be by adjusting the execution-plugin to be able to look under a specific plugin directory as well.
This way, users could write non-Python plugins (which will be a collection of scripts and a yaml file mapping operations to the scripts), and by providing the execution plugin with the plugin name (as a configuration [dependency input] in the operation implementation) the execution plugin could locate the script and run it.
was:
Plugins (operations, workflows) in ARIA currently have to be implemented in Python.
ARIA already has the execution-plugin which knows how to execute arbitrary scripts for running operations. However, sharing such scripts across service-templates won't work this time, since the execution-plugin only looks for the scripts in the service-template's resources.
One way around this would be to allow managing global resources (see linked JIRA issue), but a better way would probably be by adjusting the execution-plugin to be able to look under a specific plugin directory as well.
This way, users could write non-Python plugins (which will be a collection of scripts and a yaml file mapping operations to the scripts), and by providing the execution plugin with the plugin name (as a configuration [dependency input] in the operation implementation) the execution plugin could locate the script and run it.
> Reusable non-Python operation scripts
> -------------------------------------
>
> Key: ARIA-255
> URL: https://issues.apache.org/jira/browse/ARIA-255
> Project: AriaTosca
> Issue Type: Story
> Reporter: Ran Ziv
> Priority: Trivial
>
> Plugins (operations, workflows) in ARIA currently have to be implemented in Python.
> ARIA already has the execution-plugin which knows how to execute arbitrary scripts for running operations. However, sharing such scripts across service-templates won't work at this time, since the execution-plugin only looks for the scripts in the service-template's resources.
> One way around this would be to allow managing global resources (see linked JIRA issue), but a better way would probably be by adjusting the execution-plugin to be able to look under a specific plugin directory as well.
> This way, users could write non-Python plugins (which will be a collection of scripts and a yaml file mapping operations to the scripts), and by providing the execution plugin with the plugin name (as a configuration [dependency input] in the operation implementation) the execution plugin could locate the script and run it.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)