The difference in code to support these other patterns is negligible. Having support for forks, joins, splits, merges and sub-processes are table stakes I think.
Sure, we could start with an easier model, but if this one does both out of the gate ... yee haa. I'm curious to see how it deals with persistence and how we'd prevent workflow updates coming in from multiple orchestration workers. Likely a bitkeeper problem I suspect ... likely out-of-scope for Ziad's eval. -S On 04/04/2012 12:47 AM, Yun Mao wrote: > Hi Ziad, > > Thanks for taking the effort. Do you know which ones out of the 43 > workflows patterns are relavant to us? I'm slightly concerned that > SpiffWorkflow might be an overkill and bring unnecessary complexity > into the game. There was a discussion a while ago suggesting that > relatively simple sequential execution pattern: > https://lists.launchpad.net/nova-orchestration/msg00043.html > > Thanks, > > Yun > _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
