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

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_r109843083
  
    --- Diff: aria/modeling/orchestration.py ---
    @@ -200,15 +200,52 @@ class PluginBase(ModelMixin):
     
     class TaskBase(ModelMixin):
         """
    -    A Model which represents an task
    +    Represents the smallest unit of stateful execution in ARIA. The task 
state includes inputs,
    +    outputs, as well as an atomic status, ensuring that the task can only 
be running once at any
    +    given time.
    +
    +    Tasks may be "one shot" or may be configured to run repeatedly in the 
case of failure.
    +
    +    Tasks are often based on :class:`Operation`, and thus act on either a 
:class:`Node` or a
    +    :class:`Relationship`, however this is not required.
    +
    +    :ivar node: The node actor (optional)
    +    :vartype node: :class:`Node`
    +    :ivar relationship: The relationship actor (optional)
    +    :vartype relationship: :class:`Relationship`
    +    :ivar plugin: The implementing plugin (set to None for default 
execution plugin)
    +    :vartype plugin: :class:`Plugin`
    +    :ivar inputs: Parameters that can be used by this task
    +    :vartype inputs: {basestring: :class:`Parameter`}
    +    :ivar implementation: Python path to an ``@operation`` function
    +    :vartype implementation: basestring
    +    :ivar max_attempts: Maximum number of retries allowed in case of 
failure
    +    :vartype max_attempts: int
    +    :ivar retry_interval: Interval between retries (in seconds)
    +    :vartype retry_interval: int
    +    :ivar ignore_failure: Set to True to ignore failures
    +    :vartype ignore_failure: bool
    +    :ivar due_at: Timestamp to start the task
    +    :vartype due_at: datetime
    +    :ivar execution: Assigned execution
    +    :vartype execution: :class:`Execution`
    +    :ivar status: Current atomic status ('pending', 'retrying', 'sent', 
'started', 'success',
    +                  'failed')
    +    :vartype status: basestring
    +    :ivar started_at: Timestamp for when task started
    +    :vartype started_at: datetime
    +    :ivar ended_at: Timestamp for when task ended
    +    :vartype ended_at: datetime
    +    :ivar retry_count: How many retries occurred
    +    :vartype retry_count: int
         """
     
         __tablename__ = 'task'
     
         __private_fields__ = ['node_fk',
                               'relationship_fk',
                               'plugin_fk',
    -                          'execution_fk',
    --- End diff --
    
    ?


> 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