16:01:24 #startmeeting Mistral 16:01:25 Meeting started Mon Jul 27 16:01:24 2015 UTC and is due to finish in 60 minutes. The chair is NikolayM. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:26 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:28 The meeting name has been set to 'mistral' 16:01:46 hi everyone! 16:02:24 hi there 16:02:36 Hi 16:03:07 let's wait a few minutes for others 16:04:05 Hi everyone 16:04:21 <^Gal^> hi 16:04:45 so, let's start 16:04:55 first topic is review action items 16:04:58 #topic Review action items 16:05:18 1. NikolayM: review and discuss Lingxian's proposal about removing wf_trace module 16:05:36 particially done 16:05:46 reviewed but not discussed yet 16:06:06 so, I absolutely support this idea 16:06:31 xylan_kong is not with us today 16:06:58 next item 16:07:00 NikolayM: I am not familiar enough with this to have an opinion 16:07:04 OK 16:07:29 melisha, I can send a link on the document to you 16:07:40 2. NikolayM: map what we have and what we don't have in our docs and next week at the meeting discuss plan for it 16:08:01 I've worked on it ) 16:08:10 we have an etherpad with docs plan at https://etherpad.openstack.org/p/mistral-docs-plan 16:08:16 thanks to akuznetsova 16:08:21 and prepared etherpad ^ 16:08:29 well done :) 16:09:45 guys, you are welcome to look at it and write comments 16:09:55 akuznetsova: Very good starting point. Thanks! 16:10:04 next topic is current status 16:10:06 #topic Current status 16:10:09 as far as we agreed this scheme we can start moving articles to our official site with docs 16:10:23 <^Gal^> I'm on the execution list table, started working on the action buttons, update, and shorten the output sectioמ 16:10:27 <^Gal^> section* 16:10:30 let's tell our status 16:11:09 I am just about to finish BP: Support large datasets for execution objects - https://review.openstack.org/#/c/205190/ 16:11:14 expiration-policies-for-executions, I m ready for the first push ... 16:11:15 my status: worked on with-items-concurrency blueprint, it is fully implemented now and is no review now 16:11:37 I've prepared etherpad with scheme for our future docs and also I've started work on new gates (run unit tests against postgresql) 16:11:38 on review* 16:12:02 Updating for LimorS - She is at the process of contributing the Mistral Puppet Module and she started working on qpid support 16:12:31 yes, I've seen that patch to puppet-mistral 16:12:38 Updating for LiatFried - She will start working on the tasks screen soon 16:13:43 So, we haven't any more specific topic for this meeting 16:13:49 #topic Open discussion 16:14:14 <^Gal^> I would love you guys taking a look at the 2 blueprints we suggested, need to get them reviewd 16:14:14 <^Gal^> https://blueprints.launchpad.net/mistral/+spec/tasks-screen-improvments 16:14:15 <^Gal^> https://blueprints.launchpad.net/mistral/+spec/mistral-dashboard-cron-trigger-screen 16:14:31 ok, good 16:14:41 NikolayM, as far as I know L2 is coming, will we release Mistral on this week ? 16:14:56 #action NikolayM, all: look and review https://blueprints.launchpad.net/mistral/+spec/tasks-screen-improvments 16:14:59 ^Gal^: I reviewed them and it looks good to me 16:15:06 #action NikolayM, all: look and review https://blueprints.launchpad.net/mistral/+spec/mistral-dashboard-cron-trigger-screen 16:15:17 melisha, that's fine 16:15:27 ^Gal^, UI improvements, super! 16:15:30 thanks, melisha 16:15:34 yes 16:15:36 <^Gal^> thanks :) 16:16:17 ^Gal^, appreciate your contribution :) 16:16:28 Winson, are you here? 16:16:45 <^Gal^> sure, np. the whole team helps :) 16:17:16 all: I know we have a workflow builder coming up. Are there plans for Workflow execution graph (that shows the definition / runtime status)? 16:17:32 seems like he it not here, that's pity, cause I have a question for him 16:17:45 hmm, it seems Winson is not with us, I have a question to him... 16:17:45 melisha, yes 16:18:20 melisha, yes, we have this plans 16:18:41 akuznetsova, NikolayM: Is there a BP? Did someone started it yet? 16:18:44 What's up 16:18:46 but I'm sure we don't finish this work even in next cycle 16:18:57 ooh, hi, m4dcoder! 16:19:06 hey! 16:19:14 melisha, nobody has started it 16:19:19 m4dcoder, hi 16:19:31 akuznetsova: OK. Thanks. 16:19:50 @NikolayM: you've a question for me? 16:20:00 m4dcoder, yes 16:20:18 m4dcoder, me too 16:20:22 I saw your patch for running tests on postgres again and have a question 16:20:57 do you plan to continue on it and add ability to run tests against mysql ? 16:21:03 m4dcoder, ^ 16:21:15 *to continue to work 16:21:25 aah, yes, that's the question 16:22:36 so, and why you refused of mysql there? I remebered it was there :) 16:22:43 for postgresql, it's done from a unit test standpoint. i was hoping you can add the devstack gate for it. 16:23:01 as for mysql, it's a lower priority for me. but i can continue to work on it. 16:23:21 melisha, ^Gal^ http://horizon-merlin.mirantis.com/horizon/auth/login/?next=/horizon/project/mistral/edit/ 16:23:34 here is what we have for the current moment 16:23:39 mysql requires some more work, especially around the timestamp fields. 16:23:44 creds: demo / demo 16:24:15 melisha, ^Gal^ I mean this is a prototype of Workbook Builder 16:24:21 <^Gal^> nice!!!! 16:24:26 <^Gal^> that's sweet!! 16:24:40 akuznetsova: Thanks! I saw it on the Vancuvouer Summit. It is very nice. 16:24:45 you guys want me to separate the mysql and postgresql changes. mysql just requires more work and it's a lower priority for me currently. 16:24:48 <^Gal^> "Here will be a fancy Graph View as soon as we implement it!" :D :D 16:25:06 m4dcoder, ok, got you 16:25:12 akuznetsova: I was asking more about an execution graph for viewwing and less about a builder 16:25:30 Can we continue work with it without editing datetime fields? 16:26:13 the unit tests will fail because lacking fractional seconds. 16:26:21 melisha, I know, I just wanted to show you where we are now, how we can build wb) 16:26:33 so either we hack the unit test or we add a utility to normalize the timestamp values 16:27:07 akuznetsova: OK. Thanks. It is very cool. 16:27:52 m4dcoder, ok, we can do it separately 16:27:59 +1 16:28:50 melisha, as far as I understand there are should be two graphs: one that shows wb structure and another is for wf execution process 16:29:17 akuznetsova, yes. Static picture and dynamic one 16:29:35 akuznetsova: I tend to agree. These two views are different. 16:29:38 NikolayM, ok, thanks 16:29:52 Maybe in the future - the static one will also be a visual builder 16:30:10 m4dcoder, one more question about run_tests 16:30:31 melisha, yes, we have the blueprint for that! 16:30:53 akuznetsova: ok, go ahead 16:31:11 m4dcoder, I tried to run it in devstack gate and got following error: sudo: unknown user: postgres sudo: unable to initialize policy plugin 16:31:32 NikolayM: Thanks. Can you please share the BP? 16:31:37 what distro is the test running on? 16:32:01 m4dcoder, am I right that there are should be 2 "postgres" user: system and db 16:32:12 just the system 16:32:20 the test creates a db user called mistral 16:32:28 m4dcoder, ubuntu 16:32:43 if on ubuntu, it's automatically setup for trust for postgres user 16:32:45 melisha, it seems that it was deleted by someone 16:32:56 it was on LP 16:33:05 but now I can't find it 16:33:24 NikolayM: OK. Thanks. 16:33:51 m4dcoder, hmm 16:33:57 akuznetsova: probably will need to troubleshoot 16:34:14 have you tried locally on your own system? 16:34:42 16:34:43 org.codehaus.jackson 16:34:43 jackson-jaxrs 16:34:43 1.9.0 16:34:43 16:34:52 Sorry :-) 16:35:13 I should not work while chatting :-) 16:36:05 all: I noticed that the workflow pagination BP was merged - that is great! Do you know if someone is already working on adding it to the executions API? 16:36:09 m4dcoder, not yet) cause I decided to make test commit and run this tests on our gate 16:36:49 melisha, I guess xylan_kong will work on this 16:37:06 now it can be implemented significantly faster 16:37:38 NikolayM: OK. Cool. Yes. I believe so to. 16:39:53 m4dcoder, I will continue to debug it, if I come to a standstill, I will write to you 16:40:58 akuznetsova: thanks. feel free to reach out. i'll also run the test on my system again today to make sure it's alright. 16:41:20 m4dcoder, btw how did you test this script ? devstack + postgresql installation or just vm with ubuntu + manual postgresql installation ? 16:41:33 ubuntu + manual postgresql 16:41:42 on a vm 16:43:19 m4dcoder, ok, thanks 16:43:53 np 16:43:55 guys, do you have any more questions? 16:44:02 any more topic to discuss? 16:44:17 <^Gal^> I would like to ask in behalf of us Alcatel-Lucent guys whether could we find an earlier time for the weekly? 16:44:17 <^Gal^> and is such thing good on everyone else's timezone? 16:44:17 <^Gal^> #openstack-meeting-3 seems quite vacant regularly 16:45:12 ^Gal^, ok, I discuss this with our PTL 16:45:29 <^Gal^> thanks, appreciate that :) 16:45:40 as far as I know, current time is not suitable for xylan_kong and rakhmerov too 16:45:48 <^Gal^> yeah and Niu 16:46:06 #action NikolayM: talk to rakhmerov about moving weekly meeting to earlier time 16:46:49 For us - earlier will be better as well. It is now 19:45 16:47:11 melisha, like in our timezone (me and NikolayM ) 16:47:25 then please don't do meet on a monday AM if earlier... it's brutal 16:47:57 m4dcoder, what's time is it in your location ? 16:48:27 it's 9:47 AM US pacific. please don't make it any earlier on a Monday AM. 16:49:07 <^Gal^> lol monday morning 16:49:13 <^Gal^> worst time ever :D 16:49:25 m4dcoder: If it will be ealier on a different day - is it OK? 16:49:44 m4dcoder, we'll take it into account :) 16:50:07 yep, different day ok. evening after 10 PM PST is also ok for me. 16:50:13 I suggest to create a doc on google or etherpad for this 16:50:39 Or a doodle - http://doodle.com/en_GB/ 16:50:49 NikolayM, firstly let's find free slots 16:52:35 ok, yes 16:52:48 so, let's end our meeting 16:52:58 <^Gal^> k bye all 16:53:04 bye-bye 16:53:06 thanks to all who come us today 16:53:08 Bye 16:53:09 bye! 16:53:09 alright. thx! 16:53:15 #endmeeting