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

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_r109886404
  
    --- Diff: aria/modeling/service_instance.py ---
    @@ -529,6 +524,32 @@ def validate_capabilities(self):
                     satisfied = False
             return satisfied
     
    +    def find_host(self):
    +        def _find_host(node):
    +            if node.type.role == 'host':
    +                return node
    +            for the_relationship in node.outbound_relationships:
    +                if (the_relationship.target_capability is not None) and \
    +                    the_relationship.target_capability.type.role == 'host':
    +                    host = _find_host(the_relationship.target_node)
    +                    if host is not None:
    +                        return host
    +            for the_relationship in node.inbound_relationships:
    +                if (the_relationship.target_capability is not None) and \
    +                    the_relationship.target_capability.type.role == 
'feature':
    +                    host = _find_host(the_relationship.source_node)
    +                    if host is not None:
    +                        return host
    +            return None
    +
    +        self.host = _find_host(self)
    --- End diff --
    
    why is this dynamic? are we expecting this to change for an existing node?


> 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