Proxy tasks for worker-based engine

Registered by Ivan Melnikov on 2014-03-31

In certain deployment scenarios it would be good when some code is available only at workers, but not at "master machine" that runs taskflow engine. To enable such scenarios taskflow shoud provide "proxy tasks" that do not have actual code in execute and/or revert method but contain all correct meta-information needed to schedule the task properly.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Low
Drafter:
Ivan Melnikov
Direction:
Approved
Assignee:
None
Definition:
Discussion
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

That would mean that we'll have to untie task class identity from fully-qualified class name. We might want to provide a property like e.g. 'class_name' in BaseTask or Atom, that will return its fully-qualified class name by default, but might be overriden.

Obviously, with simple implementation of this blueprint it would not be possible to run the flows with proxy tasks in it on any engine but WBE. Of course, it is possible to write some code that will instantiate real task and run it when proxy task is scheduled in any 'local' engine if we want to do that.

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.