16:00:54 #startmeeting Mistral 16:00:55 Meeting started Mon Sep 7 16:00:54 2015 UTC and is due to finish in 60 minutes. The chair is NikolayM. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:56 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:58 The meeting name has been set to 'mistral' 16:01:03 hi everyone! 16:01:07 Hello 16:01:16 hi, gpaz 16:01:18 <^Gal^> hellllo 16:01:21 hi all 16:01:26 hi there !) 16:02:35 the meeting seems to be a bit shorter, we have no action items 16:03:01 hi, all 16:03:02 let's start 16:03:17 #topic Review Action items 16:03:23 no action items 16:03:28 <^Gal^> :D 16:03:33 hehe 16:03:33 #topic Current status 16:03:36 Nice :-) 16:03:38 yes :) 16:04:10 guys, let's tell our status for last week 16:04:24 <^Gal^> I'm on execution update, haven't got much time to work on that last week 16:04:40 <^Gal^> no technocal barriers though 16:04:45 <^Gal^> technical* 16:05:26 my status: complete action-execution-deletion blueprint before l-3, have a 3-days holiday, :-) 16:05:35 my status: still working on the docs, already done with terminology, quickstart, architecture and CLI, next - 'how to write workflow' 16:05:47 Fix for expiration policy was merged. I wanted to work on the Docs for that but unfortantly I was busy with internal stuff here 16:06:21 working on internal stuff 16:06:27 my status: fix devstack gates twice :) made commit to openstack-infra to add gate that will build our docs 16:06:34 NikolayM: how about the progress of doc work? 16:06:44 akuznetsova: thanks very much for your work! 16:07:00 <^Gal^> NikolayM: I want to write further documentation on how to to debug mistral-dashboard, just appeared to me that I missed some keynotes 16:07:04 xylan_kong, you are welcome) 16:07:24 xylan_kong: It is almost completed, only a few articles remain 16:07:38 NikolayM: greate 16:08:08 ^Gal^, sure, you are free to write it 16:08:23 <^Gal^> :P 16:08:44 one thing: please, write it to main mistral repo, in doc/source 16:09:09 there is existent docs on dashboard, could you edit it? 16:09:19 <^Gal^> NikolayM: ok, sure. what about mistral dashboard github readme? 16:09:35 <^Gal^> NikolayM: sure 16:09:45 hi guys 16:09:51 it is partly moved to that article 16:09:55 hi rakhmerov 16:09:59 NikolayM, ^Gal^ I think that you are working on different 'parts' of docs, so your commit should not conflict 16:10:15 akuznetsova, yep 16:10:16 my status: I was working on the patch: https://review.openstack.org/220439 16:10:26 <^Gal^> Ok, so should I update both repos? 16:10:34 it's about fixing a bug with cyclic workflows and refactoring specifications 16:10:37 <^Gal^> both mistral and mistral dashboard readme? 16:10:55 ^Gal^, there is another article (currently is not started yet) - troubleshooting 16:11:11 ^Gal^, NikolayM also I think that it will be cool to add user guide with screenshots ) 16:11:21 <^Gal^> akuznetsova: +1 16:11:37 +2 :) 16:11:43 (as a core :))) ) 16:11:47 <^Gal^> lol 16:11:49 <^Gal^> :P 16:11:52 ^Gal^, I think no, it is enough to have docs at the main doc source (docs.openstack.org) 16:11:55 haha :) 16:12:17 <^Gal^> NikolayM: ok :) 16:12:21 I agree with NikolayM 16:12:37 <^Gal^> LimorStotland: ok, thanks! 16:12:40 and the rest :-) 16:12:55 <^Gal^> I agree with Limor 16:12:59 <^Gal^> :P 16:13:08 akuznetsova has submitted the patch to the infra recently and docs soon starts to build on docs.openstack.org 16:13:21 yep 16:13:33 good job 16:13:33 for every merged patch in mistral 16:13:39 hope so) 16:13:39 here it is: https://review.openstack.org/220226 16:13:45 thanks, akuznetsova! 16:13:54 :) 16:15:02 so folks, I'll be annoying again and talking about L-3 16:15:19 #topic Wrapping up L-3 16:15:37 as you know, we're a couple of days behind with L-3 release 16:15:49 technically, it's a couple of hours to make a release 16:15:50 but.. 16:15:58 #topic Wrapping up L-3 16:16:16 ooh, thanks! I forgot you're a host 16:16:17 :) 16:16:29 do you want some patches to get merged? 16:16:32 I just want that we have a chance to finish planned BPs 16:16:40 yes 16:17:04 do we still have open bp (not in the ui)? 16:17:13 ^Gal^: I know you're busy with internal stuff but I have to ask you about https://blueprints.launchpad.net/mistral/+spec/mistral-dashboard-executions-screen 16:17:23 is there a chance you'll finish it tomorrow? 16:17:29 <^Gal^> nope 16:17:36 <^Gal^> :( 16:17:41 ok, honest answer ) 16:17:45 <^Gal^> lol 16:17:46 let's move it to RC-1 16:18:14 <^Gal^> rakhmerov: thanks! and sorry 16:18:48 that's ok 16:18:55 another one is https://blueprints.launchpad.net/mistral/+spec/mistral-action-execution-deletion 16:19:04 rakhmerov, NikolayM: https://review.openstack.org/#/c/216509/ need +1 for workflow, but i found there is devstack failure which has nothing to do with my patch 16:19:17 xylan_kong: yes, I just wanted to say this 16:19:35 yes, something with changing execution states 16:19:36 are you sure it has nothing to do with it? 16:19:44 give me a sec 16:20:03 NikolayM: you met with this failure? 16:20:42 yeah, it's NegativeCLITests.test_ex_invalid_status_changing 16:20:47 hm.. weird 16:20:56 ooo 16:21:13 akuznetsova: do you know what's going on? 16:21:13 xylan_kong, I just see an error in gate 16:21:35 I have a theory 16:21:35 seems like the calling goes well, no exception is raised 16:22:06 seems like it can be related to https://review.openstack.org/#/c/219870/2 16:22:47 if it's not so urgent issue, i can figure it out tomorrow 16:22:57 there wasn't such problem in previously merged patch, but here this test failed 16:23:04 yes, I think akuznetsova is right 16:23:13 I think I even know what the problem is 16:23:29 xylan_kong: yes, please look at it tomorrow 16:23:34 rakhmerov: ok 16:23:40 rakhmerov: i'll cover it 16:24:04 #action xylan_kong: look at the failing test NegativeCLITests.test_ex_invalid_status_changing, it may be related with https://review.openstack.org/#/c/219870/2 16:24:13 xylan_kong: thnx, appreciate 16:24:17 yes, thanks 16:24:24 then let's merge Lingxian's patch now 16:24:24 np 16:24:50 rakhmerov: and this one, https://blueprints.launchpad.net/mistral/+spec/mistral-pagination-support, needs your approval and consider it as completed 16:25:02 for now 16:25:20 already done 16:25:25 I did it today 16:25:49 rakhmerov: really? I see no aprover 16:26:05 I usually mark BPs as "Beta available" before it's released 16:26:12 there is an approver ) 16:26:25 so it's been taken care of 16:26:46 ok 16:26:55 let's see what else we have.. 16:27:47 xylan_kong: I also wanted to find out the status of https://review.openstack.org/216729 16:27:53 but zhenguo is not here 16:28:00 do you happen to know his plans on it? 16:28:29 rakhmerov: yeah, i believe he want it to be merged in l-3 16:28:46 right, but now jenkins votes -1 16:28:55 I guess it needs to be rebased or something.. 16:29:04 ok, we need to ask him tomorrow 16:29:19 rakhmerov: I'll contact him tomorrow 16:29:24 #action rakhmerov, xylan_kong: remind zhenguo about https://review.openstack.org/216729 16:29:26 yes 16:29:34 so, just to let you know 16:29:34 let him finish it ASAP 16:29:44 yes 16:29:50 if there is not tech debate on that 16:29:57 I'm going to make a release tomorrow evening anyway 16:30:15 if something is not in then we'll have to move it to RC1 16:30:34 ok, good, do what you think is right :-) 16:30:50 akuznetsova: I know you had comments on this patch so please try to participate tomorrow 16:31:43 akuznetsova: yeah, need your insight and expertise 16:31:57 rakhmerov, xylan_kong ok 16:32:29 xylan_kong: and I need your review on https://review.openstack.org/220439 :)) 16:32:38 you should like this patch ) 16:32:59 np, leave another action item for me 16:33:01 :-) 16:33:11 if zhenguo won't be available, I can rebase/send new patch set for this patch 16:33:27 i'll do them all tomorrow 16:33:29 #action xylan_kong: review https://review.openstack.org/220439 and Nikolay's documentation patches 16:33:49 akuznetsova: yes, we can do it 16:33:57 ok 16:34:21 NikolayM: I guess we can move https://blueprints.launchpad.net/mistral/+spec/mistral-documentation to RC1? 16:34:26 this is a grouping BP 16:34:39 yep, I also think so 16:34:46 not all docs will be ready by the EOD tomorro, right? 16:34:48 ok 16:34:50 some of bps are not completed 16:35:32 i can't wait to see our doc listed on website :-) 16:35:37 yep 16:35:40 me too ) 16:35:46 it's really useful for new comers 16:36:02 guys, we need to make our docs shine during Sept 16:36:06 yes 16:36:20 we've been hearing much complaints about our docs 16:36:35 now it's high time we made them good and useful 16:36:36 <^Gal^> mistral dashboard tasks screen bp - assigend to Liat, not finished either 16:36:44 rakhmerov: yes, i did this when i came to mistral the first day 16:37:09 <^Gal^> same for cron trigger on mistral-dashboard 16:37:18 ^Gal^: I know, I promised to help her with it but didn't find time today. Will do tomorrow, either me or zhenguo 16:37:38 <^Gal^> rakhmerov: oh ok, didn't know she contacted you 16:37:40 #action rakhmerov, zhenguo: help Liat with her patch on tasks screen 16:37:59 ^Gal^: cron trigger screen has been moved to RC1 16:38:08 which is ok 16:38:32 like I said there's no time tension on UI work, we have more flexibility on it 16:38:48 but I just want to have some discipline anyway 16:39:02 <^Gal^> aggree 16:40:00 guys, one more thing I'd love to be able to push into L-3 is a new YAQL function for extracting task result 16:40:20 [openstack-dev] [mistral][yaql] Addressing task result using YAQL function 16:40:40 you can look at this thread and express your opinion 16:40:43 yes, i saw the email, didn't have time to reply. i like the idea 16:40:57 task(name) 16:40:59 nobody is against it so far 16:41:00 yes 16:41:12 and there's a strong technical reason to do so 16:41:20 you can read my explanations if you want 16:41:52 so, me or Nikolay will try to get it knocked down tomorro 16:41:59 xylan_kong: please be ready to review 16:42:08 rakhmerov: np 16:42:19 always in the position for help 16:42:31 #action rakhmerov or NikolayM: implement task() yaql function 16:42:35 ok 16:43:06 so this is all I wanted to discuss on L-3 16:43:14 do you have anything else? 16:43:49 rakhmerov: don't forget the client release 16:43:57 yes 16:44:08 ooh, btw, is gpaz here? 16:44:24 yes 16:44:46 can you please carefully look at the patch https://review.openstack.org/#/c/218544/ ? 16:44:50 hi, I saw your changes for the test 16:45:02 it's already merged and it actually looks slightly weird 16:45:14 it's because looks like expiration policy doesn't run as expected 16:45:17 for some reason 16:45:36 I was a critical issue in some production that still a lot of my time this week :( 16:45:49 so Winson says it may not run every minute as configured for some reason 16:45:50 I m not sure I understand why it is failing 16:45:59 yes 16:46:17 no urgency but pls try to investigate once you have time 16:46:30 I hope tommorow I ll have time 16:46:45 #action gpaz: try to investigate what may be wrong with expiration policy (look at https://review.openstack.org/#/c/218544/) 16:46:49 last days were realy busy here for me with customers 16:46:51 ok 16:47:07 it's understandable, no need to explain 16:47:08 thanks 16:47:30 where you saw it is failing by the way ? 16:47:47 it even happens on my local dev machine 16:47:53 once in a while 16:48:03 Ok 16:48:09 I will take alook 16:48:10 <^Gal^> #action ^Gal^: make mistral-dashboard debug shine 16:48:11 approximately every third or forth time 16:48:21 :) 16:48:25 haha )) 16:48:27 weired, never failed for me .. 16:48:48 Ok, taking that 16:49:02 yeah, it looks like a concurrency problem 16:49:19 it behaves differently on different machines 16:49:33 so now I really don't have anything else to discuss 16:49:46 let's go to open discussion 16:49:52 or end the meeting 16:49:56 rakhmerov: do you already have a plan for Tokyo Summit? I'm very interested in it 16:50:19 xylan_kong: no detailed plan 16:50:44 of course, I know major topics that we need to discuss 16:51:04 rakhmerov: all right, so we can discuss face to face if there's a chance 16:51:17 btw, please share your suggestion for the fishbowl session (with larger audience and projector) 16:51:23 xylan_kong: yes 16:51:52 at fishbowl session, for example, you could tell about your experience using Mistral or something like that 16:52:05 rakhmerov: no problem 16:52:18 sort of a promo actually 16:52:23 ok 16:52:39 rakhmerov: i can share story with HWS using workfow (but it's not mistral) 16:53:09 ok, let's talk about it in a few days 16:53:15 sure 16:53:48 so, nothing need to discuss for me 16:54:12 ok 16:54:23 NikolayM: let's end the meeting? 16:54:34 you are in charge today ) 16:55:00 sure 16:55:06 #endmeeting