So taskflow has tasks, which seems comparable to actions? I guess I should get tired of asking but why recreate the same stuff ;)
The questions listed: - Does action need to have revert() method along with run() method? - How does action expose errors occurring during it's work? - In what form does action return a result? And more @ https://wiki.openstack.org/wiki/Mistral/Blueprints/ActionsDesign And quite a few others that haven't been mentioned (how does a action retry? How does a action report partial progress? What's the intertask/state persistence mechanism?) have been worked on by the taskflow team for a while now... https://github.com/openstack/taskflow/blob/master/taskflow/task.py#L31 (and others...) Anyways, I know mistral is still POC/pilot/prototype... but seems like more duplicate worked that could just be avoided ;) -Josh -----Original Message----- From: Renat Akhmerov <rakhme...@mirantis.com> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Date: Tuesday, March 11, 2014 at 11:32 PM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Subject: [openstack-dev] [Mistral] Actions design BP >Team, > >I started summarizing all the thoughts and ideas that we¹ve been >discussing for a while regarding actions. The main driver for this work >is that the system keeps evolving and we still don¹t have a comprehensive >understanding of that part. Additionally, we keep getting a lot of >requests and questions from our potential users which are related to >actions (Œwill they be extensible?¹, Œwill they have dry-run feature?¹, >Œwhat are the ways to configure and group them?¹ and so on and so forth). >So although we¹re still in a Pilot phase we need to start this work in >parallel. Even now lack of solid understanding of it creates a lot of >problems in pilot development. > >I created a BP at launchpad [0] which has a reference to detailed >specification [1]. It¹s still in progress but you could already leave >your early feedback so that I don¹t go in a wrong direction too far. > >The highest priority now is still finishing the pilot so we shouldn¹t >start implementing everything described in BP right now. However, some of >the things have to be adjusted asap (like Action interface and the main >implementation principles). > >[0]: >https://blueprints.launchpad.net/mistral/+spec/mistral-actions-design >[1]: https://wiki.openstack.org/wiki/Mistral/Blueprints/ActionsDesign > >Renat Akhmerov >@ Mirantis Inc. > > > > >_______________________________________________ >OpenStack-dev mailing list >OpenStack-dev@lists.openstack.org >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev