15:01:28 #startmeeting Mistral 15:01:30 Meeting started Mon Apr 3 15:01:28 2017 UTC and is due to finish in 60 minutes. The chair is rakhmerov. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:31 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:34 The meeting name has been set to 'mistral' 15:01:37 Hey all! 15:01:39 o/ 15:01:42 hi 15:01:56 hi there 15:02:12 hi 15:02:16 o/ 15:02:53 hi all 15:02:54 1 sec 15:03:47 #topic Review Action items 15:03:50 1. d0ugal to check for doc liaison tasks 15:03:59 oops, I have not done this. 15:04:05 :) 15:04:09 #action d0ugal to check for doc liaison tasks 15:04:17 hello... 15:04:32 toure: hey 15:04:34 2. rakhmerov: ask Michal to review the spec about mistral-extra 15:04:35 done 15:04:50 3. mgershen/team to talk with Renat about bug https://bugs.launchpad.net/mistral/+bug/1672379 15:04:50 Launchpad bug 1672379 in Mistral "default task on error not running when task fail to evaluate input" [Undecided,Invalid] 15:05:03 rakhmerov: I think maybe that wasn't needed in the end 15:05:13 yes 15:05:28 we've kind of touched that, it's not an easy thing to solve now 15:05:48 4. rbrady start sensitive data spec 15:06:02 it was done 15:06:08 about 3, should I open a blueprint? 15:06:12 hey rakhmerov once I finish fighting with gerrit I have the client code ready for review 15:06:14 it even has one +2 15:06:15 :) 15:06:28 toure: for error analysis? 15:06:32 yup 15:06:36 awesome ) 15:06:41 merge conflicts 15:06:43 #link https://review.openstack.org/450853 15:06:43 :( 15:06:50 mgershen: yes, please 15:06:57 ^ that's the sensitive data spec 15:07:06 yes 15:07:30 ok 15:07:42 rakhmerov: do you want to add an action to make sure I won't forget? 15:08:16 #action mgershen: create a BP about "on-error" semantics 15:08:25 #topic Current status (quick info from team members) 15:09:43 my status: reviewing, working on advanced publishing (actually got stuck with lang changes unexpectedly, will probably have to do some serious refactoring first), investigating an issue introduced by new SQLAlchemy 15:09:53 the last one was finally fixed today 15:10:14 so please provide a short update if you have anything 15:10:39 I'm now working on mistral-extra, and starting the ground work for moving the OpenStack actions over. The spec merged today (thanks for reviews!) 15:10:54 I will have almost no time in the next few weeks to work on mistral, but if something needs reviewing try to ping me. 15:10:55 that is great 15:11:11 mgershen: sure, understandable 15:11:53 just FYI: akuznetsova is now helping us with some tasks again (which is awesome) 15:12:10 akuznetsova: could you please tell a little bit about your activities? 15:12:39 yes, for the old times' sake 15:12:43 :) 15:12:52 I've published fixes for two bugs 15:13:14 * d0ugal needs to catch up with reviews. 15:13:23 d0ugal: yes! :) 15:13:25 and looked through the list of bugs in mistralclient, there were a lot of old bugs which I closed 15:13:39 bug triage ++ 15:14:08 d0ugal: yeah, I was actually going to do that today at the meeting ) 15:14:29 but akuznetsova volunteered to do some pre-filtering 15:14:43 great 15:14:55 akuznetsova: thanks a lot! 15:14:56 thank you akuznetsova :) 15:15:11 I'm working on moving some imports from mistral to mistral-lib mostly in tripleo-common (sorry for for the tripleo centric status) 15:15:14 rakhmerov, mgershen you are welcome 15:15:57 apetrich: it is extremely valuable for Mistral to show this stuff working, it is all theoretical so far :) 15:16:05 mgershen, d0ugal: we got a bunch of patches passed through check queue today after we rebased them after merging an SQLA issue so please try to find some time to review them 15:16:34 sure 15:16:52 rakhmerov: do you have links? 15:17:04 d0ugal, apetrich: this is very very good, the only thing I'm worried about is that isn't it too early? :) 15:17:13 d0ugal, I can see that 15:17:22 mgershen: there's too many of them, just look at gerrit pls 15:17:40 rakhmerov: possibly - but we need to start some time and it'll help direct us what we need to do next. We wont land anything in tripleo yet. 15:17:41 rakhmerov, it is more of proof of concept and identify the early pitfalls 15:17:46 +1 15:17:47 ooh, ok 15:17:55 if so then it's fine 15:18:10 because otherwise the APIs may not be stable yet etc. 15:18:48 then this is good really 15:18:49 rakhmerov: ok, I will. 15:18:52 ok 15:19:35 mgershen: I just usually look at "Watched Changes" tab and see patches that recently changed on the top 15:21:13 ok, is there anything else on that? 15:21:24 rbrady: do you have any updates today? 15:22:07 rakhmerov: thrash took care of the spec, I've only done reviews since last week 15:22:26 ok, thanks 15:22:27 good 15:22:58 rbrady: as far as mistral-lib, are you planning to make more changes in the near future? 15:23:18 rbrady: what do you think is now left? 15:23:28 from what we planned 15:23:32 rahkmerov: I think the next steps are the keystone_utils and the openstack actions 15:23:39 We need Mistral to depend on msitral-lib and to pass the context 15:23:56 rbrady: ^ I think we need that first maybe, but it is easy to hack in for testing :) 15:23:58 ^^ and what d0ugal said :) 15:24:28 I have a patch locally that does it, I could put it up for review but we need mistral-lib in global-requirements first 15:24:43 I'll post it as a starting point at least. 15:24:56 yes 15:24:58 agree 15:25:27 d0ugal: having it in global-requirements should not be a huge problem, right? 15:25:38 afaik 15:25:44 rakhmerov: no, that should be easy 15:25:52 I just need to find the process and follow it 15:26:04 ok 15:26:32 and we need to figure out rpm packaging for the tripleo side - just adding the dep will break tripleos CI I think 15:26:44 but again, that should be quite easy. 15:27:00 yep 15:27:26 so, we can probably go to an open discussion 15:27:46 I don't have any special topics today 15:28:03 if you do please bring them up 15:28:12 #topic Open Discussion 15:29:04 one thing I'd like to share about what I'm doing is that I stumbled on making changes in workflow language in the last few days 15:29:22 I found that it became very hard to make such changes 15:29:51 What makes it so difficult? 15:29:52 this Spec class hierarchy became enormously complex 15:29:55 ah 15:30:12 The code in mistral.lang.*? 15:30:18 d0ugal: too many places to change in order to make even relatively small changes 15:30:21 yes 15:30:35 Interesting, I wonder how we can make it easier 15:30:39 and then if you look at how to alter tests it's not easier ) 15:30:53 d0ugal: yeah, that's what I'm thinking about now 15:31:04 I have some ideas, will try to implement them 15:31:31 one more thing related to that is we may want to have a new version of the language some time in the future 15:31:39 and I believe it may happen relatively soon 15:32:02 because we've been adding more and more feature into the language 15:32:36 they are all backwards compatible and hence we lose some opportunities to make the lang more concise and elegant 15:32:36 Migrating workflows doesn't sound like fun :) 15:32:46 no, wait :) 15:32:50 I didn't mean that ) 15:33:00 haha, I know 15:33:09 what I meant is that we'll have to support more than one language version 15:33:18 I know, sounds scary 15:33:28 yup, but even in that case we would want to upgrade older workflows over time. 15:33:37 and especially scary for me after I looked again at how it's now implemented :) 15:33:42 lol 15:34:15 d0ugal: yeah, true we'll probably need to provide some aid to upgrade to a newer version 15:34:54 anyway, this is something that I've discussed with a number of people already and seems like this idea of the new lang version may not be that theoretical 15:35:11 so, that's just one thing I'm involved in now 15:35:28 cool, it would be interesting to see those ideas. 15:35:31 ideally I'd like to improve it somehow 15:35:46 and btw, I found one thing that makes WF validation slower, I'll fix it soon 15:36:12 yeah, the mechanism is powerful but it became too heavy 15:36:49 that is all from my side 15:37:02 I don't really have anything to discuss this week. 15:37:14 guys, next time let's sync on Pike-1 tasks 15:37:35 sure 15:37:38 ack 15:37:49 please try to find time to check if you're going to meet the scope of Pike-1 15:38:39 another topic I'd like to bring up next week is something I discussed with my boss at Nokia recently 15:39:20 so essentially I set up 4 goals for 2017 regarding Mistral 15:39:30 mostly from our business perspective 15:39:58 but anyway, I think these goals reflect my vision of how Mistral should evolve in the next year 15:40:11 I'd be interested in discussing these goals with you 15:40:16 cool 15:40:18 sounds good 15:40:20 so that we all understand the direction 15:40:29 Sounds like it'll be a busy meeting :) 15:40:33 yes 15:41:13 my suggestion would be even to declare these goals (if we agree on them) somewhere, in the spec repo or a wiki (seriously outdated now btw) 15:41:26 a spec? 15:41:33 maybe a spec, yes 15:42:11 so, just to be even more clear: I believe these goals is the 3-4 main things that we should be focusing on in order to make the project more successful 15:42:22 and attract more people to it (both users and contributors) 15:42:42 ok, details next time ) 15:42:52 I am done for sure 15:42:55 * toure waits for details 15:42:55 now 15:42:56 :) 15:42:56 look forward to it :) 15:43:04 toure: haha, rakhmerov is teasing us! 15:43:11 :)) 15:43:11 indeed 15:43:14 hehe 15:43:24 yeah, may be a little :) 15:43:37 I've been teasing d0ugal for a looong time with a UI tool :) 15:43:51 that is something I'd really love to demonstrate some time soon 15:44:10 cool 15:44:16 can't wait to see it 15:44:32 +1 15:44:36 I'm going to bring that up soon with my management in order to find out when and how we're going to announce it 15:44:55 ok 15:45:04 anything else may be? 15:45:13 not from me 15:45:16 or we can finish for today 15:45:20 nothing for me 15:45:28 nothing for me 15:45:31 nothing from my side 15:46:37 ok 15:46:49 thank you all for coming and for the interesting discussion 15:46:54 see you next week 15:46:59 thanks all! 15:47:03 have a good one 15:47:05 have a wonderful week guys ) 15:47:06 thanks, bye 15:47:11 bye 15:47:12 ta 15:47:16 #endmeeting