Hi, Eswar,
In case you're interested, there is another choice of 'workflow
engine' you can refer to: http://docs.openstack.org/developer/mistral/
Hope you'll find it interesting :-)
On Sat, Jan 9, 2016 at 10:33 AM, ESWAR RAO wrote:
> Thanks Joshua for the clear
I also updated https://wiki.openstack.org/wiki/DistributedTaskManagement
to denote that said wiki is no longer active (it was an attempt to back
a taskflow engine[1] with celery); although if u are interested in
continuing down this path feel free.
Hopefully that clears up some 'confusion'
ESWAR RAO wrote:
Hi Joshua,
Thanks for the response.
As you mentioned, I went through below which has taskflow as celery
front end:
https://etherpad.openstack.org/p/TaskFlowWorkerBasedEngine
https://blueprints.launchpad.net/taskflow/+spec/distributed-celery
I think the idea way-back-when
Hi Joshua,
Thanks for the response.
As you mentioned, I went through below which has taskflow as celery front
end:
https://etherpad.openstack.org/p/TaskFlowWorkerBasedEngine
https://blueprints.launchpad.net/taskflow/+spec/distributed-celery
I guess if we have a job = task1 + task2 ; if we
Thanks Joshua for the clear explanation.
On Sat, Jan 9, 2016 at 6:24 AM, Joshua Harlow wrote:
> ESWAR RAO wrote:
>
>> Hi Joshua,
>>
>> Thanks for the response.
>>
>> As you mentioned, I went through below which has taskflow as celery
>> front end:
>>
>>