I'm unsure why oslo.messaging would have a concepts of tasks. I didn't think it did.
Other projects building on-top of oslo.messaging imho should have a concept of tasks, oslo.messaging should seem like it should provide a reliable messaging layer. Wondering why u think this should be coupled with oslo.messaging? Taskflow[1] in particular has some of these semantics and it will use oslo.messaging when oslo.messaging achieves py3 compat. [1] http://docs.openstack.org/developer/taskflow/ -Josh From: John Wood <[email protected]<mailto:[email protected]>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <[email protected]<mailto:[email protected]>> Date: Thursday, April 24, 2014 at 11:58 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: [openstack-dev] [oslo] [messaging] Curious about retry/scheduled tasks Hello folks, I am curious if olso.messaging exposes a means to support retry and defer semantics for tasks. For example, it could be nice to retry processing a failed task under some circumstances, such as if a network service is temporarily unavailable. It might also be beneficial to be able to run a task at a time in the future, or on a recurring basis such as to drive an asynchronous polling process. These features can be handled in application code or orchestration services of course, but just curious if olso.messaging provides a lower-level mechanism for handling this. Thanks, John
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
