Monday, 2018-02-19

*** bobh has joined #openstack-mistral01:07
*** itlinux has quit IRC02:02
*** kushalAgrawal has joined #openstack-mistral02:12
*** bobh has quit IRC02:29
*** yangyapeng has quit IRC02:30
*** bobh has joined #openstack-mistral02:33
*** yangyapeng has joined #openstack-mistral03:44
*** ykarel has joined #openstack-mistral04:14
*** bobh has quit IRC04:18
*** hardikjasani has joined #openstack-mistral04:51
*** kushalAgrawal has quit IRC05:52
*** kushalAgrawal has joined #openstack-mistral06:08
*** threestrands has quit IRC06:10
*** threestrands has joined #openstack-mistral06:23
*** threestrands has quit IRC07:00
apetrichrakhmerov, oh dear. looking into that07:49
rakhmerovapetrich: yeah )07:52
rakhmerovhi07:52
rakhmerovapetrich: it looks monstrous but mostly consists of the tests07:53
*** AlexeyAbashkin has joined #openstack-mistral07:56
rakhmerovd0ugal, apetrich: TripleO gate in https://review.openstack.org/#/c/544318/ is still failing. I looked at it but didn't understand why. Is it something known on the tripleO side or you think it's Mistral specific?07:58
apetrichrakhmerov, that's really messy and weird. It seems it failed on setting the repos on the undercloud. I will take a better look when I'm fully in08:00
rakhmerovthanks08:29
*** oidgar has joined #openstack-mistral08:35
d0ugalrakhmerov: sure, we can delete the milestone - but I guess there could still be an rc2?08:46
rakhmerovd0ugal: as far as I understand the deadline was last Fri08:46
d0ugalrakhmerov: no, finaly RCs can be released up until the 23rd08:47
rakhmerovbut for some reason I still don't see that 6.0.0 is released08:47
d0ugalthen the release is 26th - march 2nd08:47
d0ugalhttps://releases.openstack.org/queens/schedule.html08:47
rakhmerovhm...08:47
rakhmerovlooking..08:48
rakhmerovI was sure it was the last week08:48
d0ugalso there wont be 6.0 until at least the 26th :)08:48
rakhmerovhah, yes08:49
rakhmerovmy mistake08:49
rakhmerovthen yes, OK!08:49
rakhmerovbtw, there's at least one thing I'd like to backport when the patch is ready08:49
rakhmerovhttps://bugs.launchpad.net/mistral/+bug/171405408:49
openstackLaunchpad bug 1714054 in Mistral "tasks listed after pause do not run when workflow is resumed" [High,New] - Assigned to Renat Akhmerov (rakhmerov)08:49
rakhmerovI confirmed that it doesn't work and am fixing it now..08:49
d0ugalalso, re: https://review.openstack.org/#/c/467799/ - as I saidn, I'll try and review it this week.08:50
rakhmerovyep08:50
rakhmerovthanks08:50
rakhmerovbtw, please also look at https://review.openstack.org/#/c/545692/08:50
d0ugalThe lack of docs is a big issue tho IMO08:51
rakhmerovwould be nice to backport it as well08:51
rakhmerovthe lack of docs for what?08:51
d0ugalThe events patch08:51
rakhmerovaah, he'll have to write them08:51
rakhmerovand I think for the next cycle (R) we need to consider this functionality experimental08:52
d0ugalI feel like to review it I need to try it out, but that is going to take a long time with no docs.08:52
rakhmerovI'm still not sure about some design decisions we made08:52
rakhmerovyes, understandable08:52
d0ugalI don't agree with landing experimental code, so you just made me worried08:52
rakhmerovthat's why I'd rather let it merge and experiment with it throughout the cycle08:52
d0ugalDid you test it?08:52
rakhmerovno!08:53
d0ugal:/08:53
apetrichmassive patch is massive08:53
rakhmerovI will08:53
rakhmerovbut have no time now08:53
d0ugalIndeed08:53
d0ugalA common problem :)08:53
rakhmerovand I'd personally prefer docs in a separate patch08:54
rakhmerovanyway08:54
d0ugalThat is fine08:54
d0ugalbut when we talked about it before we said there should at least be a draft docs patch up08:54
rakhmerovhe's really mad that nobody wants to review the patch already )08:54
rakhmerovif we ask him to add the docs he'll never finish it )08:55
d0ugalwell, he is also inactive in the Mistral community - until he wants something merged.08:55
rakhmerovtrue08:55
d0ugalI'm concerned if we merge it he will never finish it either08:55
rakhmerovbut I don't know how to fix it08:55
rakhmerovI tried many times but failed08:55
rakhmerovd0ugal: in this case I'll take the responsibility for it08:56
d0ugalHe has expectations from us, we should be allowed expectations from him08:56
rakhmerovI wanted to make something similar for years anyway08:56
rakhmerovI know Dougal but it is what it is08:56
rakhmerovlet it be my responsibility08:56
rakhmerovhe is a good engineer indeed but he's busy with other things all the time08:57
d0ugalWe are all busy people :)08:57
rakhmerovso I am grateful with this anyway08:57
rakhmerovwell, yes, but he mostly work in a completely different community08:57
rakhmerovnot OpenStack08:57
rakhmerovwe're at least in OpenStack all the time08:58
rakhmerovso it's not easy for him08:58
rakhmerovwill be right back08:58
*** jtomasek has joined #openstack-mistral09:04
*** jpich has joined #openstack-mistral09:05
*** oidgar has quit IRC09:28
rakhmerovd0ugal: just one more thought on the Winson's patch. You now have the final word in such situations. I can express my opinion, of course, but you can block things if you believe they are not ready or not compliant with the OpenStack rules09:37
rakhmerovso, please don't think I'm rebelling or something ))09:38
d0ugalrakhmerov: sure, thanks09:39
d0ugalrakhmerov: I'll have some time to start looking at it this morning09:40
d0ugalI am mostly fine with it in theory.09:41
d0ugalbut I am not sure how we get a commitment of docs etc.09:41
d0ugalMaybe I can revert it if we don't get docs before the end of Rocky :P09:42
d0ugaland if you consider it experimental, I think it should be clearly marked as such09:42
*** oidgar has joined #openstack-mistral09:43
*** oidgar has quit IRC09:47
d0ugalrakhmerov, apetrich - I tried one more recheck on https://review.openstack.org/#/c/544318/. I was seeing a similar error in my dev env, but it is okay now. So I think there may have been a packaging issue that is now resolved.09:55
d0ugalIf it fails again I'll dig in further09:55
apetrichd0ugal, yeah it really smelled of infra issue09:56
*** shardy has joined #openstack-mistral10:15
*** gkadam has joined #openstack-mistral10:39
d0ugalrakhmerov: when would you use the remote notifier?10:53
*** AlexeyAbashkin has quit IRC11:07
*** AlexeyAbashkin has joined #openstack-mistral11:32
*** katkapilatova has joined #openstack-mistral11:50
*** dprince has joined #openstack-mistral12:57
*** kushalAgrawal has quit IRC13:02
apetrichwould the notifier thread increase load?13:05
*** thrash|g0ne is now known as thrash13:06
thrashfyi: this should pass now: https://review.openstack.org/#/c/53955313:06
apetrichthrash, https://media.giphy.com/media/MjwL3oUTVPIOs/giphy.gif13:19
thrashNONE SHALL PASS13:20
*** ykarel has quit IRC13:20
*** oidgar has joined #openstack-mistral13:28
*** gkadam has quit IRC13:31
*** hardikjasani has quit IRC13:35
*** bobh has joined #openstack-mistral13:36
rakhmerovd0ugal: regarding the failure, thanks, got it13:43
rakhmerovd0ugal: as far as remote notifier, it's basically the exact same architecture as with executo13:43
rakhmerovexecutor13:43
rakhmerova remote notifier could be used when we want a better scalability, for example13:43
rakhmerovand better decoupling of the components13:44
rakhmerovso that engine process doesn't do all notifications itself (with the corresponding load)13:44
rakhmerove.g. if it involves some heavy processing and/or uses some heavy transport13:45
rakhmerovso he was basically following the decisions we made in Denver and I guess it's captured in the spec13:46
rakhmerovas far as commitment to write the docs, I agree13:46
rakhmerovlike I said, I'm taking responsibility for it13:46
rakhmerovand yes, we can revert it if it's not done till the end of Rocky13:47
*** ykarel has joined #openstack-mistral13:51
*** toure|gone is now known as toure13:54
*** bobh has quit IRC13:54
d0ugalapetrich: the notifier has its own server afaict, so it shouldn't add load unless you run it.14:01
*** bobh has joined #openstack-mistral14:31
*** jistr is now known as jistr|mtg14:31
apetrichthrash, rbrady might not have enough internets today to do the scum14:32
thrashapetrich: ack14:32
apetrichtrying anyway14:32
*** kushalAgrawal has joined #openstack-mistral14:32
apetrichlol can't even send messages on chat14:36
*** apetrich has quit IRC14:42
*** apetrich has joined #openstack-mistral14:43
*** hjensas has quit IRC14:50
*** jistr|mtg is now known as jistr15:02
*** oidgar has quit IRC15:12
rakhmerovd0ugal: I added one more topic to the etherpad which we MUST solve in Rocky15:13
rakhmerovmoving away from "blocking" executor in oslo.messaging15:14
d0ugaloh yeah15:15
d0ugaldamn, I hate that issue :)15:15
rakhmerovd0ugal: oh yeeah15:16
rakhmerovabsolutely15:16
rakhmerovit's a pain in the b...t15:16
rakhmerovd0ugal: most likely I'll have to skip the planning today, or at least a significant part of it15:18
d0ugalrakhmerov: no worries15:18
rakhmerovI asked Andras to join so he might15:18
d0ugalrakhmerov: in a meeting now  btw15:18
d0ugalgreat15:18
rakhmerovok15:18
rakhmerovd0ugal: are you going to make the schedule today or we can give people a couple of days more to add their items?15:20
d0ugalrakhmerov: I might start today, but probably over tomorrow and wednesday15:21
d0ugalI can always adjust it if we get more ideas after15:21
rakhmerovok, thanks15:21
*** umbSublime has joined #openstack-mistral15:45
*** hjensas has joined #openstack-mistral15:55
openstackgerritRenat Akhmerov proposed openstack/mistral master: Explain better combinations of task names and engine commands in docs  https://review.openstack.org/54569216:03
umbSublimedoes mistral use taskflow behind the scene ?16:03
rakhmerovno16:03
rakhmerovumbSublime: we tried to long ago but found that the execution models were significantly different16:04
rakhmerovwe even had a whitepaper somewhere on that topic..16:04
umbSublimeI'm currently checking out both mistral and taskflow for creating workflows. I've currently got a POC working on taskflow, but I also want to create one with mistral to compare16:05
umbSublimejust learned about mistral today actually :p16:05
umbSublimeI'm watching your Sydney talk rakhmerov  :)16:05
rakhmerovcool16:06
umbSublimeaccording to the wiki mistral is still in POC (v0.1.1), but according to github you have 6.0.0 tag. Is it prod ready ?16:08
*** katkapilatova has quit IRC16:08
rakhmerovumbSublime: forget about wiki :)16:09
rakhmerovit's seriously out of date16:09
umbSublimehehe yah I figured :p16:09
rakhmerovwe'll fix it at some point..16:09
rakhmerovor remove completely16:09
umbSublimealso from what I understand aside from keystone, mistral can be used as a stand-alone thing ?16:11
umbSublimeaka I can also use it for things unrelated to OS16:11
umbSublimehehe intead of asking 1000 questions is there some up-to-date doc I should look at :p16:12
*** mcdoker181818 has joined #openstack-mistral16:20
*** ykarel is now known as ykarel|away16:29
*** hardikjasani has joined #openstack-mistral16:35
d0ugalumbSublime: you don't even need Keystone btw16:50
*** AlexeyAbashkin has quit IRC16:50
d0ugalumbSublime: https://docs.openstack.org/mistral/latest/16:51
d0ugalThat is the best documentation we have, but it isn't great.16:51
d0ugalrakhmerov: we should remove the wiki and direct people to the docs. I'll make a note to do that.16:51
*** hjensas has quit IRC16:59
umbSublimethx d0ugal I'll check this out in the next N days :)\16:59
d0ugalumbSublime: np, we can try and help in here.17:00
d0ugalumbSublime: Just so you know, the OpenStack PTG is on next week - so it will be quiet in here then.17:00
umbSublimehehe makes sense :)17:01
umbSublimeI've just talked to my boss, he wants me to make the taskflow POC more robust before investigating other solutions. But from my first impression mistral is the way to go17:01
*** itlinux has joined #openstack-mistral17:21
*** shardy has quit IRC17:41
*** jpich has quit IRC17:49
*** AlexeyAbashkin has joined #openstack-mistral18:15
*** openstackgerrit has quit IRC18:18
*** AlexeyAbashkin has quit IRC18:20
thrashd0ugal: https://review.openstack.org/#/c/539553/18:23
*** hjensas has joined #openstack-mistral18:23
*** hjensas has quit IRC18:23
*** hjensas has joined #openstack-mistral18:23
*** hjensas has quit IRC18:27
*** jrist is now known as jrist-afk18:28
*** jrist-afk is now known as jrist18:28
*** hardikjasani has quit IRC18:38
*** hjensas has joined #openstack-mistral18:44
*** hjensas has quit IRC18:44
*** hjensas has joined #openstack-mistral18:44
*** rbrady has quit IRC18:50
*** rbrady has joined #openstack-mistral19:02
*** rbrady has quit IRC19:02
*** rbrady has joined #openstack-mistral19:02
*** harlowja has joined #openstack-mistral19:03
*** ykarel|away has quit IRC19:13
*** toure is now known as toure|biab20:01
*** toure|biab is now known as toure20:33
*** itlinux has quit IRC20:36
d0ugalthrash: +W20:43
thrashd0ugal: awesome. Thanks!20:43
*** kushalAgrawal has quit IRC20:52
*** rbrady has quit IRC21:06
*** rbrady has joined #openstack-mistral21:19
*** AlexeyAbashkin has joined #openstack-mistral21:26
*** AlexeyAbashkin has quit IRC21:31
*** dprince has quit IRC21:33
*** threestrands has joined #openstack-mistral21:37
zigoLooks like mistral Queens rc1 really needs mistral-lib >= 0.4. I got failure when using 0.3 from requirements.22:21
zigoI'd suggest fix the global-reqs ...22:21
zigoFilling a bug just for that is probably too much ... :P22:26
*** bobh has quit IRC23:02
*** AlexeyAbashkin has joined #openstack-mistral23:06
*** AlexeyAbashkin has quit IRC23:10

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