> I also considered making it part of the existing scheduler service, > but wasn't sure how to add a "time-delayed" message to the scheduler queue > for the follow-up. If that's possible, then there would not need to be a > separate service; the scheduler can simply follow up itself.
Unless the scheduler dies. These sorts of long running processes have to be controlled by an external state machine. It's a well solved problem using business process modeling/workflow orchestration. -S _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp This email may include confidential information. If you received it in error, please delete it. _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
