Uploaded image for project: 'AriaTosca'
  1. AriaTosca
  2. ARIA-239

Allow each task to define its own executor

    XMLWordPrintableJSON

Details

    • Story
    • Status: Open
    • Trivial
    • Resolution: Unresolved
    • None
    • None
    • None
    • None

    Description

      Currently, the task executor granularity is at the execution level - all tasks use the same executor (except for stub tasks, but that's a separate topic).

      It should be made possible for users to define (possibly in the service-template, workflow, or both) which executor they'd like to execute a specific operation with.

      For example, the execution plugin, which is built-in, can use the ThreadExecutor (in theory; it might actually run into concurrency issues since Fabric's environment is not thread-safe) even if operations that use custom plugins can't, and thereby increase performance etc.

      Attachments

        Issue Links

          blocks

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ARIA-240 Workflow tasks

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Open

          Activity

            People

              Unassigned Unassigned
              ran Ran Ziv
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: