| *** bobh has joined #openstack-mistral | 00:08 | |
| *** altlogbot_1 has quit IRC | 00:10 | |
| *** altlogbot_0 has joined #openstack-mistral | 00:12 | |
| *** bobh has quit IRC | 00:18 | |
| *** bobh has joined #openstack-mistral | 00:48 | |
| *** bobh has quit IRC | 01:08 | |
| *** bobh has joined #openstack-mistral | 01:30 | |
| *** bobh has quit IRC | 01:42 | |
| *** apetrich has quit IRC | 01:57 | |
| *** ykarel|away has joined #openstack-mistral | 02:24 | |
| openstackgerrit | pengyuesheng proposed openstack/mistral master: Blacklist python-cinderclient 4.0.0 https://review.opendev.org/660551 | 03:28 |
|---|---|---|
| openstackgerrit | Renat Akhmerov proposed openstack/mistral master: Constraint networkx to <2.3 for Python 2 https://review.opendev.org/660104 | 03:39 |
| *** ykarel|away is now known as ykarel | 03:58 | |
| *** ykarel has quit IRC | 04:53 | |
| *** ykarel has joined #openstack-mistral | 05:11 | |
| *** pgaxatte has joined #openstack-mistral | 06:27 | |
| openstackgerrit | pengyuesheng proposed openstack/python-mistralclient master: Update sphinx dependency https://review.opendev.org/660577 | 06:47 |
| openstackgerrit | Merged openstack/mistral master: Optimize searching of upstream task executions https://review.opendev.org/660158 | 07:08 |
| openstackgerrit | pengyuesheng proposed openstack/python-mistralclient master: Update sphinx dependency https://review.opendev.org/660577 | 07:11 |
| *** apetrich has joined #openstack-mistral | 07:39 | |
| openstackgerrit | Merged openstack/python-mistralclient master: Update sphinx dependency https://review.opendev.org/660577 | 07:40 |
| *** ykarel is now known as ykarel|lunch | 07:52 | |
| rakhmerov | hello All | 08:00 |
| rakhmerov | is there anybody here for the meeting? | 08:01 |
| rakhmerov | #startmeeting Mistral | 08:01 |
| openstack | Meeting started Wed May 22 08:01:57 2019 UTC and is due to finish in 60 minutes. The chair is rakhmerov. Information about MeetBot at http://wiki.debian.org/MeetBot. | 08:01 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 08:01 |
| *** openstack changes topic to " (Meeting topic: Mistral)" | 08:02 | |
| openstack | The meeting name has been set to 'mistral' | 08:02 |
| rakhmerov | d0ugal, vgvoleg, pgaxatte, apetrich: hi | 08:02 |
| d0ugal | Hey | 08:02 |
| rakhmerov | :) | 08:02 |
| vgvoleg | hello | 08:03 |
| rakhmerov | just want to check if we have at least a small crowd to chat about anything | 08:03 |
| rakhmerov | d0ugal: how's it going? | 08:03 |
| d0ugal | I'm good thanks :) Keeping busy with various things! | 08:03 |
| d0ugal | Unfortunately no Mistral news from me. | 08:03 |
| vgvoleg | #help | 08:04 |
| vgvoleg | how's it should work | 08:04 |
| rakhmerov | d0ugal: yep, ok ) | 08:04 |
| vgvoleg | ? | 08:04 |
| rakhmerov | vgvoleg: what do you mean? :) | 08:04 |
| vgvoleg | I've typed | 08:05 |
| rakhmerov | "#help"? | 08:05 |
| vgvoleg | "#help" | 08:05 |
| d0ugal | lol | 08:05 |
| vgvoleg | and nothing happended | 08:05 |
| rakhmerov | aah, I don't know honestly | 08:05 |
| d0ugal | Are you looking for meetingbot commands? | 08:05 |
| rakhmerov | #help | 08:05 |
| d0ugal | https://wiki.debian.org/MeetBot | 08:05 |
| d0ugal | "#help - Add a "Call for Help" to the minutes. Use this command when you need to recruit someone to do a task. (Counter-intuitively, this doesn't provide help on the bot) " | 08:05 |
| rakhmerov | yeah | 08:06 |
| rakhmerov | it's like "#action" that puts an special entry into the meeting log | 08:06 |
| pgaxatte | hello | 08:06 |
| rakhmerov | vgvoleg: so these are basically some commands to make the meeting log good looking and more structured | 08:07 |
| rakhmerov | pgaxatte: hey! How have you been? | 08:07 |
| pgaxatte | good thanks rakhmerov | 08:07 |
| rakhmerov | ok ) | 08:07 |
| pgaxatte | very busy on openstack-helm these days :D | 08:07 |
| rakhmerov | I see | 08:08 |
| rakhmerov | good | 08:08 |
| vgvoleg | #idea guys what do you think about 'fail-on' policy on task, which read boolean expression and force fail task if it is True? | 08:09 |
| rakhmerov | pgaxatte, vgvoleg, d0ugal: we used to have this kind of meetings on a regular basis but we've not had them I guess since Decemtber. So I'll try to renew this tradition so that we have some dedicated time to gather team members and chat | 08:09 |
| rakhmerov | pgaxatte: please spread out this info across your colleagues who have something to do with Mistral | 08:09 |
| pgaxatte | rakhmerov: i'm not actively working on mistral but i'll pass the word to the teams here so they can attend the meetings | 08:09 |
| rakhmerov | we can brainstorm on stuff, triage bugs etc. etc., revisit BPs | 08:10 |
| rakhmerov | pgaxatte: yes, please | 08:10 |
| rakhmerov | thanks | 08:10 |
| rakhmerov | vgvoleg: what's the use case for "fail-on"? | 08:10 |
| pgaxatte | and anyway I'll keep an ear out :) | 08:10 |
| rakhmerov | vgvoleg: can you describe? | 08:10 |
| rakhmerov | pgaxatte: appreciate | 08:10 |
| vgvoleg | We are actively use this policy in our Mistral fork, and I don't know if it is interesting for vanilla Mistral or not | 08:10 |
| rakhmerov | it may be, but we need to know more on what you mean by that | 08:11 |
| vgvoleg | For example, we use some action, that return any result. We can add e.g. 'fail-on: <% task().result <=4 %>' and fail a task if result is unsatisfactory | 08:12 |
| vgvoleg | so we don't hide this logic in action code and make flow more readable | 08:12 |
| rakhmerov | vgvoleg: Oleg, it seems like you can do it in a different way | 08:13 |
| rakhmerov | so | 08:13 |
| rakhmerov | 1) there's the notion of a error result for an action that can be actually used later in the workflow | 08:13 |
| rakhmerov | that is, if your action finished with an error but still generated a result that you can use | 08:14 |
| rakhmerov | and then you can do: | 08:14 |
| rakhmerov | on-error: | 08:14 |
| rakhmerov | - fail: <% task().result ... %> | 08:14 |
| rakhmerov | if you also need to fail the entire workflow | 08:14 |
| rakhmerov | maybe I don't fully understand your idea though | 08:15 |
| rakhmerov | an example: std.http action may return a error status code and it will be considered an error result | 08:15 |
| rakhmerov | in the workflow text you'll be able to use it in some conditions | 08:15 |
| rakhmerov | via task().result | 08:16 |
| rakhmerov | e.g. task().result.status_code | 08:16 |
| rakhmerov | vgvoleg: what do you think? | 08:17 |
| rakhmerov | I have to admit thought that it might not be well documented now ) | 08:17 |
| rakhmerov | as some other things | 08:17 |
| vgvoleg | You talk about tasks with ERROR status | 08:17 |
| rakhmerov | yes | 08:18 |
| vgvoleg | I say about setting ERROR status to the task that was SUCCESS, but for some way it's result is unsatisfactory | 08:18 |
| rakhmerov | do you necessarily need to fail the same task? | 08:19 |
| rakhmerov | the semantics here is the following: if the action is successful then the task will be successful too (unless there are errors in YAQL, for example) | 08:19 |
| rakhmerov | but we can always handle the action result via conditions in the on-success clause | 08:20 |
| rakhmerov | and, for example, fail the entire workflow or reroute to another task | 08:20 |
| rakhmerov | but you saying that we can extend this semantics and add one more thing to force fail the task... | 08:21 |
| rakhmerov | hm.. | 08:21 |
| rakhmerov | well, ok | 08:22 |
| vgvoleg | yes | 08:22 |
| rakhmerov | it may make sense | 08:22 |
| rakhmerov | vgvoleg: can you please file a blueprint for this? | 08:22 |
| vgvoleg | It is more readable | 08:22 |
| rakhmerov | with a detailed description | 08:22 |
| vgvoleg | yes, sure | 08:22 |
| rakhmerov | ok, thanks | 08:22 |
| vgvoleg | I just wanted to know you opinion :) | 08:22 |
| rakhmerov | also a note on the mailing list would be helpful | 08:23 |
| rakhmerov | vgvoleg: I need to think. Seems like it's not going to harm anything | 08:23 |
| rakhmerov | but let's try to think it over and look at it from different angles | 08:24 |
| rakhmerov | #action vgvoleg: file a blueprint about the new "fail-on" policy to fail a task even if its action finished successfully | 08:24 |
| rakhmerov | ok | 08:26 |
| rakhmerov | we've got the first action item! | 08:27 |
| rakhmerov | cool ) | 08:27 |
| rakhmerov | vgvoleg, d0ugal, pgaxatte: do you have anything else for now? | 08:27 |
| rakhmerov | ok, if not, I'll close the meeting but we'll still be online for a while | 08:30 |
| pgaxatte | rakhmerov: nope not for me. But as we discussed in Denver, we're trying to move our mistral deployments to K8s+Helm so when that is done I'll probably have some stuff to add in Mistral itself :D | 08:30 |
| rakhmerov | yes, I remember, thanks Pierre | 08:30 |
| rakhmerov | ok | 08:30 |
| rakhmerov | thanks for coming :) | 08:31 |
| rakhmerov | #endmeeting | 08:31 |
| *** openstack changes topic to "Mistral the Workflow Service for OpenStack. https://docs.openstack.org/mistral/latest/" | 08:31 | |
| openstack | Meeting ended Wed May 22 08:31:08 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 08:31 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/mistral/2019/mistral.2019-05-22-08.01.html | 08:31 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/mistral/2019/mistral.2019-05-22-08.01.txt | 08:31 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/mistral/2019/mistral.2019-05-22-08.01.log.html | 08:31 |
| *** ykarel|lunch is now known as ykarel | 08:38 | |
| *** pgaxatte has quit IRC | 09:42 | |
| *** ykarel is now known as ykarel|afk | 11:12 | |
| *** apetrich has quit IRC | 12:01 | |
| *** bobh has joined #openstack-mistral | 12:10 | |
| *** apetrich has joined #openstack-mistral | 12:14 | |
| *** ykarel|afk is now known as ykarel | 12:18 | |
| *** apetrich has quit IRC | 12:19 | |
| *** bobh has quit IRC | 12:19 | |
| *** apetrich has joined #openstack-mistral | 12:35 | |
| *** bobh has joined #openstack-mistral | 13:55 | |
| *** bobh has quit IRC | 14:30 | |
| *** ykarel is now known as ykarel|afk | 14:31 | |
| openstackgerrit | Mike Fedosin proposed openstack/mistral master: Get rid of lookup utils https://review.opendev.org/653710 | 14:50 |
| *** ykarel|afk is now known as ykarel | 15:06 | |
| *** jtomasek has joined #openstack-mistral | 15:11 | |
| openstackgerrit | Mike Fedosin proposed openstack/mistral master: Get rid of lookup utils https://review.opendev.org/653710 | 15:12 |
| *** ykarel is now known as ykarel|away | 16:01 | |
| *** jtomasek has quit IRC | 16:05 | |
| *** ykarel|away has quit IRC | 16:15 | |
| *** bobh has joined #openstack-mistral | 17:06 | |
| *** bobh has quit IRC | 17:20 | |
| *** jtomasek has joined #openstack-mistral | 17:26 | |
| *** bobh has joined #openstack-mistral | 17:57 | |
| *** jtomasek has quit IRC | 18:23 | |
| *** jtomasek_ has joined #openstack-mistral | 18:23 | |
| *** bobh has quit IRC | 18:28 | |
| *** bobh has joined #openstack-mistral | 19:16 | |
| *** jtomasek_ has quit IRC | 19:24 | |
| *** jtomasek has joined #openstack-mistral | 19:25 | |
| *** jtomasek has quit IRC | 19:42 | |
| *** jtomasek_ has joined #openstack-mistral | 19:43 | |
| *** mmethot_ has quit IRC | 19:44 | |
| *** mmethot has joined #openstack-mistral | 19:46 | |
| *** jtomasek_ has quit IRC | 20:02 | |
| *** jtomasek has joined #openstack-mistral | 20:03 | |
| *** bobh has quit IRC | 20:16 | |
| *** jtomasek has quit IRC | 21:47 | |
| *** mmethot has quit IRC | 22:51 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!