Mailing-List: contact dev-help@ariatosca.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ariatosca.incubator.apache.org
Date: Thu, 13 Apr 2017 11:39:41 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: dev@ariatosca.incubator.apache.org
Message-ID: <JIRA.13039447.1485952048000.274970.1492083581715@Atlassian.JIRA>
In-Reply-To: <JIRA.13039447.1485952048000@Atlassian.JIRA>
References: <JIRA.13039447.1485952048000@Atlassian.JIRA> <JIRA.13039447.1485952048188@jira-lw-us.apache.org>
Subject: [jira] [Commented] (ARIA-92) Execution plugin operations default
 mappings
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 13 Apr 2017 11:39:46 -0000


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

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

Github user ran-z commented on a diff in the pull request:

    https://github.com/apache/incubator-ariatosca/pull/95#discussion_r111368446
  
    --- Diff: tests/resources/service-templates/tosca-simple-1.0/node-cellar/node-cellar.yaml ---
    @@ -98,8 +98,8 @@ topology_template:
                   #token: { get_property: [ HOST, flavor_name ] }
           interfaces:
             Maintenance:
    -          enable: juju > charm.maintenance_on
    -          disable: juju > charm.maintenance_off
    +          enable: juju \> charm.maintenance_on
    --- End diff --
    
    :+1: 


> 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)