Joshua, Thanks for your interest and feedback.
I believe you were able to deliver your message already, we definitely hear you. So no need to the same stuff again and again ;) As I promised before, we are now evaluating what’s been going on with TaskFlow for the last couple of months and preparing our questions/concerns/suggestions on using it within Mistral. But that’s not very easy and quick thing to do since there’s a bunch of details to take into account, especially given the fact that Mistral codebase has become much more solid and Mistral itself now has lots of requirements dictated by its use cases and roadmap vision. So patience would be really appreciated here. If you don’t mind I would prefer to discuss things like that in separate threads, not in threads devoted to daily project activities. So that we can split our conceptual discussions and current work that’s going on according to our plans. Otherwise we have a risk to make spaghetti out of our ML threads. Thanks Renat Akhmerov @ Mirantis Inc. On 13 Mar 2014, at 08:54, Joshua Harlow <[email protected]> wrote: > 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 <[email protected]> > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > <[email protected]> > Date: Tuesday, March 11, 2014 at 11:32 PM > To: "OpenStack Development Mailing List (not for usage questions)" > <[email protected]> > 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 >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
