Hi Oleg, I looked at the blueprint. Looks good to me, I understand the motivation behind. The fact that we use created_at and updated_at now to see the duration of the task is often confusing, I agree. So this would be a good addition and it is backward compatible. The only subtle thing is that when you make changes in CloudFlow we’ll have to make a note that since version X of CloudFlow (that will be using new fields to calculate durations) it will require Mistral Stein. Or, another option is to make it flexible: if those fields are present in the HTTP response, we can use them for calculation and if not, use the old way.
Thanks Renat Akhmerov @Nokia On 26 Sep 2018, 18:02 +0700, Олег Овчарук <vgvo...@gmail.com>, wrote: > Hi everyone! Please take a look to the blueprint that i've just created > https://blueprints.launchpad.net/mistral/+spec/mistral-add-started-finished-at > I'd like to implement this feature, also I want to update CloudFlow when this > will be done. Please let me know in the blueprint if I can start implementing. > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
