Friday, 2017-10-27

*** AlexeyAbashkin has joined #openstack-mistral00:10
*** AlexeyAbashkin has quit IRC00:14
*** bobh has joined #openstack-mistral00:22
*** gkadam has joined #openstack-mistral00:23
*** gkadam_ has quit IRC00:25
*** AlexeyAbashkin has joined #openstack-mistral00:46
*** AlexeyAbashkin has quit IRC00:51
*** gkadam has quit IRC01:07
*** Kevin_Zheng has joined #openstack-mistral01:21
*** bobh has quit IRC02:11
*** AlexeyAbashkin has joined #openstack-mistral02:47
*** AlexeyAbashkin has quit IRC02:52
*** AlexeyAbashkin has joined #openstack-mistral03:08
*** AlexeyAbashkin has quit IRC03:12
*** yangyape_ has joined #openstack-mistral04:09
*** yangyapeng has quit IRC04:11
*** gkadam has joined #openstack-mistral04:19
*** jaosorior has joined #openstack-mistral05:05
*** mcdoker181818 has joined #openstack-mistral05:10
*** mcdoker181818 has quit IRC07:17
rakhmerovd0ugal: can you please review https://review.openstack.org/#/c/512520/ again?07:27
d0ugalrakhmerov: sure07:28
d0ugalrakhmerov: I have a bunch of reviews open if you get time :)07:28
rakhmerovyes, ok07:29
rakhmerov:)07:29
rakhmerovtrying to survive here but I'll find time :)07:29
d0ugalhaha, they can wait until next week07:29
d0ugalrakhmerov: maybe just this one so I can start the release process. https://review.openstack.org/#/c/514675/07:29
rakhmerovyep07:30
rakhmerovno problem07:30
rakhmerovd0ugal: seems like 'task_execution_id' from the __init__ parameters is not used anywhere07:32
d0ugalrakhmerov: whoops, line 87 is wrong. One moment07:35
d0ugal82 I mean07:36
rakhmerovyes, right07:36
openstackgerritDougal Matthews proposed openstack/mistral-lib master: Rename task_id to task_execution_id  https://review.openstack.org/51467507:37
d0ugalrakhmerov: ^07:37
rakhmerovyep07:37
*** oidgar has joined #openstack-mistral07:38
rakhmerovok, looks good now07:39
d0ugalThanks07:39
rakhmerovso task_id now has higher priority07:39
d0ugalYeah07:39
d0ugalwell, sort-of07:40
d0ugalbut if you pass both that is weird :)07:40
rakhmerovyep07:40
rakhmerovthat's ok07:40
d0ugalI don't mind changing the order07:40
apetrichd0ugal, it might be me as a non native speaker but I had to reread "It will be removed in the future" twice. I'd rather read "Task_id will be removed in the future"07:42
apetrichd0ugal, but that is a very minor nit. LGTM07:42
* d0ugal re-reads07:43
d0ugalI think that is okay, but happy to take suggestions.07:43
apetrichd0ugal, it might just be morning. I can read it normaly now07:43
d0ugallol07:43
d0ugalapetrich: It is difficult to think with that bright thing outside07:44
*** AlexeyAbashkin has joined #openstack-mistral07:56
*** oidgar has quit IRC08:08
*** mcdoker181818 has joined #openstack-mistral08:16
mcdoker181818rakhmerov: What do you think about pluginaze a TaskPolicy through the stevedore? It would allow users to develop own a task policy.09:03
mcdoker181818Good morning all :)09:03
rakhmerovhi09:03
rakhmerovmcdoker181818: the idea sounds good but the implementation of policies is pretty hairy09:04
rakhmerovand involves a lot of interactions with internal engine mechanisms09:04
rakhmerovI thought about this idea initially when I was developing some of the policies09:05
rakhmerovbut we first need to understand how to make the engine more flexible etc.09:05
rakhmerovso believe me, it's really not easy09:05
mcdoker181818than what do you think about 'fail-on' policy that would allow to fail a task based on true\false expression after execution?09:14
mcdoker181818after task execution09:14
openstackgerritMerged openstack/mistral master: Add a config option to disable cron triggers  https://review.openstack.org/51252009:51
*** daidv has quit IRC10:12
*** gkadam has quit IRC10:34
rakhmerovmcdoker181818: task or action?10:40
d0ugalit should fail the task IMO10:43
mcdoker181818task10:46
*** gkadam has joined #openstack-mistral10:47
d0ugalmcdoker181818: Can you write up an example of what fail-on would look like?10:52
d0ugala full task or workflow10:52
d0ugalI don't think I really understand what you could do with fail-on that you couldn't do with the fail engine command.10:52
d0ugalmcdoker181818: maybe what you really want is a new engine command to fail the task but not the workflow?10:56
d0ugalbut I still don't know why you would want that :)10:56
d0ugalwhy is it so important that the task fails?10:56
rakhmerovyeah, I'm trying to see where it would be useful11:01
rakhmerovand we also need to keep in mind that "on-error" and "on-success" refer to action error or success11:02
rakhmerovtask is just an action call essentially11:02
d0ugalgood point11:06
openstackgerritDougal Matthews proposed openstack/mistral master: Pass the new ActionContext to mistral-lib  https://review.openstack.org/50618511:07
openstackgerritDougal Matthews proposed openstack/mistral master: Use the new action context in MistralHTTPAction  https://review.openstack.org/50550811:07
openstackgerritDougal Matthews proposed openstack/mistral master: Remove the __init__ method from the test action  https://review.openstack.org/51306111:07
openstackgerritDougal Matthews proposed openstack/mistral master: Rename task_id to task_execution_id  https://review.openstack.org/51468811:07
mcdoker181818For example, std.http returns some json. I check value. If value equals 'RUNNING' I retried task (retry -> on-continue). But if json equals 'ERROR'. I want that task has ERROR state. And for example, tasks will be triggered in 'on-error'.11:09
d0ugalmcdoker181818: why not just do it in an on-complete/on-success?11:09
rakhmerovdo what?11:10
d0ugalon-complete: - error_task: <% task().result = "ERROR" %>11:10
rakhmerovyep11:10
d0ugalI understand a it, you want the task to be an error because that is conceptually how you see it11:11
d0ugalbut really the action didn't fail11:11
rakhmerovprobably my main concern here is: what will having the task in ERROR state give us?11:11
* d0ugal will bbiab11:12
rakhmerovin order to handle the task's ERROR state we'll need something else11:12
rakhmerovbecause, like I said, on-complete/on-error/on-success is all about actions11:12
rakhmerovwhat to do if the action(s) failed, succeeded or just finished (no matter what the result is)11:13
rakhmerovnow task may get to ERROR state if its action(s) succeeded only if some post action run things failed11:14
rakhmerovlike "publish", "on-xxx" clause etc.11:14
rakhmerove.g. an error during YAQL/Jinja expression evaluation11:14
mcdoker181818The administrator see tasks but not actions. Now this task will has SUCCESS state. Administrutor must retried this task. But he cann't, right?11:23
mcdoker181818I will do example of implementation with examples to Monday :)11:37
d0ugalThe administrator should also pay attention to failing workflows, so you can show it that way11:43
d0ugalthe workflow itself should do the retrying if that is needed anyway tho'11:44
mcdoker181818All tasks has success state, how do i show users the root cause?11:52
mcdoker181818rakhmerov: > only if some post action run things failed12:02
mcdoker181818Not. For example is timeout policy. My action has success state, but task is failed12:02
*** dprince has joined #openstack-mistral12:05
*** gkadam has quit IRC12:37
*** toure_biab is now known as toure12:38
d0ugalmcdoker181818: I would improve the workflow output if the cause isn't clear.12:55
mcdoker181818Maybe the task output too. But users oriented by color (SUCCESS-green, ERROR-red) :D13:05
mcdoker181818I tried to show you examples on Monday. Maybe then you'll change your mind.13:05
d0ugalSounds good :)13:06
d0ugalI'm not totally against it, we just need to be careful what we add.13:06
*** shardy has quit IRC13:07
mcdoker181818I agree with you.13:07
rakhmerovmcdoker181818: language is always a very sensitive part and changes may have serious long-term impact on end users13:17
rakhmerovthat's why we discuss them during long time and with lots of people13:18
mcdoker181818Yep, I understand. This is why I offer opportunity to pluginaze policy too :)13:21
mcdoker181818I have dev build with policy with steveodore, I show on Monday too13:22
mcdoker181818rakmerov: While you're here can it will be merged? https://review.openstack.org/#/c/510384/13:24
mcdoker181818rakhmerov:13:25
rakhmerovmcdoker181818: I'll review, yes13:28
openstackgerritRenat Akhmerov proposed openstack/mistral master: 'all' parameter breaks task context  https://review.openstack.org/51038413:32
mcdoker181818Thank you13:36
openstackgerritMerged openstack/mistral master: Fix launcher tests  https://review.openstack.org/51257413:46
*** Dinesh_Bhor has quit IRC14:04
*** d0ugal_ has joined #openstack-mistral14:04
*** d0ugal has quit IRC14:05
*** bobh has joined #openstack-mistral14:55
*** toure is now known as toure_biab14:57
*** bobh has quit IRC14:58
*** toure_biab is now known as toure15:00
*** thrash is now known as thrash|biab15:06
*** AlexeyAbashkin has quit IRC15:13
openstackgerritDougal Matthews proposed openstack/mistral-lib master: Rename task_id to task_execution_id  https://review.openstack.org/51467515:43
openstackgerritDougal Matthews proposed openstack/mistral-lib master: Add deprecated context parameters to the new security context  https://review.openstack.org/51574915:43
*** thrash|biab is now known as thrash15:44
*** jaosorior has quit IRC15:48
*** AlexeyAbashkin has joined #openstack-mistral16:53
*** AlexeyAbashkin has quit IRC16:57
*** thrash is now known as thrash|bbl17:21
*** mcdoker181818 has quit IRC17:48
*** harlowja has quit IRC18:05
*** harlowja has joined #openstack-mistral18:05
*** dprince has quit IRC18:48
*** dprince has joined #openstack-mistral19:13
*** bobh has joined #openstack-mistral20:02
*** bobh has quit IRC20:04
*** bobh has joined #openstack-mistral20:05
*** bobh has quit IRC20:09
*** dprince has quit IRC20:27
*** jtomasek has quit IRC22:14

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!