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

ASF GitHub Bot commented on ARIA-92:
------------------------------------

Github user tliron commented on a diff in the pull request:

    https://github.com/apache/incubator-ariatosca/pull/95#discussion_r109952876
  
    --- Diff: aria/modeling/service_template.py ---
    @@ -1544,11 +1547,24 @@ def as_raw(self):
     
         def instantiate(self, container):
             from . import models
    +        from ..orchestrator import context
    +        plugin = None
    +        if self.plugin_specification is not None:
    +            try:
    +                workflow_context = context.workflow.current.get()
    +                plugin = 
self.plugin_specification.find_plugin(workflow_context.model.plugin.list())
    +            except context.exceptions.ContextException:
    +                pass
    +                # TODO
    --- End diff --
    
    Yes, we need to talk about this. :) I don't know how else to find other 
models. Is there a current context for SQLAlchemy?


> Execution plugin operations default mappings
> --------------------------------------------
>
>                 Key: ARIA-92
>                 URL: https://issues.apache.org/jira/browse/ARIA-92
>             Project: AriaTosca
>          Issue Type: Story
>            Reporter: Ran Ziv
>            Assignee: Tal Liron
>
> The execution plugin serves as the default plugin, i.e. if no other plugin 
> was specified, it'll be used to execute scripts in operations.
> These scripts will currently only execute locally. The execution plugin also 
> supports running scripts on remote machines (via SSH).
> One option is to have the parser recognize whether the node in question is 
> contained inside a host node, in which case the script should be executed 
> remotely (by default, yet overridable by specifying the full plugin operation 
> mapping), and if not then it should be executed locally.
> Another option is to have the user specify it using special syntax, e.g.:
> "local > script.sh" and "remote > script.sh"



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

Reply via email to