16:00:50 #startmeeting Mistral 16:00:50 Meeting started Mon Jan 19 16:00:50 2015 UTC and is due to finish in 60 minutes. The chair is rakhmerov. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:51 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:54 The meeting name has been set to 'mistral' 16:00:55 hi 16:01:22 hi 16:02:09 how's it going? 16:02:18 not good 16:02:34 hi ! 16:03:07 hi 16:03:15 akuznetsova, what happened? 16:03:18 anything serious? 16:03:37 rakhmerov, I stuck with my commit to Rally 16:03:42 akuznetsova, :( 16:03:49 ooh!! 16:04:29 that's ok, don't hurry with that 16:04:33 hi all 16:05:01 hi 16:05:04 let's start 16:05:12 rakhmerov, we discussed some ideas with Boris, today he founded another solution and I have to rewrite part of my code 16:05:27 ok, I see 16:05:52 let us know if you need help, don't struggle alone in the dark ) 16:06:11 #topic Current status (progress, issues, roadblocks, further plans) 16:06:25 let's quickly let each other know our statuses 16:07:14 I am working on my commit to Rally, fix Boris's comments 16:07:57 my status: Last week we had several meetings with Dmitri on a number of problems they faced with Mistral, I completed a part of "Secure Access" BP (patches on review), today I was also trying to fix problems occurring in environment tests (still in progress) 16:09:14 anybody here? :) 16:09:19 yes 16:09:20 yep 16:09:32 hi Bryan, nice to "see" you again here 16:09:34 OK, just a little quiet 16:09:38 Hi, yeah same 16:09:50 my status: last week I investigated ‘result->output->published data’ transformation and discovered some problems there, discussed with Renat; this week I target to begin fixing some of them. 16:10:01 everyone is still trying to wake up after New Year holidays :) 16:10:06 especially in Russia :) 16:10:33 status: worked on with-items, especially on concurrency policy and its implementation for with-items, already worked fine but I still have few issues 16:10:49 ok 16:10:55 So far have looked into webhooks and ceilometer triggering for heat a bit to see how they do it. Haven't started yet though. Will soon. 16:11:10 alright 16:11:20 Also, prototyped catching errors and reportign exceptions in engine (to solve the problem of tasks/workflows stuck in “RUNNING” state when some exceptios happen. Got stuck there because the desired behavior is not clear. 16:11:59 yeah, we probably need to talk about that separately 16:12:06 @m4dcoder: Winson are you here? 16:13:21 I know that Winson was building workflows and discoered / fixed bugs and problems there as he moved on. 16:13:41 ok 16:14:00 dzimine, do you know what his status is on environment BP? 16:14:05 he’ll be pushing his local fixes upstream hopefully this week - we didn’t have a chance to sync up 16:14:11 is there something left on that? 16:14:21 ok, I see 16:14:36 AFAIK environment BP first part is done, what’s left is ‘default variables’. 16:14:43 for tasks. 16:14:49 yes, ok 16:14:58 that was pretty much my understanding as well 16:15:15 guys, do you see any roadblocks in your work that you'd like to discuss right now? 16:16:16 #action dzimine, clarify Winson's status on "Environment" BP 16:16:55 ok, let's proceed 16:17:03 #topic "Kilo-2" scope and blueprints 16:17:25 I'd like to discuss Kilo-2 scope again a little bit 16:17:27 is nmakhotkin around? 16:17:31 yes 16:17:34 he's here 16:18:18 may be I missed nikolay’s status update? 16:18:31 he reported it 16:18:32 damn sorry here it is! 16:18:35 :) 16:18:38 :) np 16:19:02 yes :) 16:19:25 ok, so the reason I'd like to pay a little bit of our attention to Kilo-2 scope again is that I talked to Dmitri last week :) 16:20:13 and after those conversations I came to conclusion that we should probably move some of the BPs to the next milestone 16:20:27 just because we now see much more important things 16:20:47 blocking bugs, mainly. 16:20:53 yes 16:21:27 this is what we have so far: https://launchpad.net/mistral/+milestone/kilo-2 16:21:31 unfortunately, we still need to work through that and build the full list of urgent bugs 16:21:50 yes 16:22:09 what we could do now is to take a look at this page and suggest what we can get rid of (for now) 16:23:15 one thing that I'd like to say over and over again is: we should forget about "half-done" solutions, quality is our highest priority now 16:24:03 ok, let's vote 16:24:23 I think https://blueprints.launchpad.net/mistral/+spec/mistral-non-distributable-actions could be moved away 16:24:32 +1 on “no half-done”. It really blows once we real-use it 16:24:46 agree on non-distributable-action 16:24:51 maybe we can postpone bps connected with mistral-dashboard? 16:24:58 although I already started working on it I realized it's not so trivial task and I don't want to spend time on it now 16:25:29 akuznetsova, yes, I think the same 16:26:10 objections? 16:26:15 I would move manage-db out, too. 16:26:29 https://blueprints.launchpad.net/mistral/+spec/mistral-dashboard-crud-operations , https://blueprints.launchpad.net/mistral/+spec/mistral-dashboard-tests , https://blueprints.launchpad.net/mistral/+spec/mistral-execution-visualization 16:27:06 This is maintanance task, no tech risk, just ‘do it once the thing works’. 16:27:07 I actually really want to implement those UI BPs but it's not a good time now. We can commit to that work in the next milestone 16:27:42 +1 on akuznetsova’s proposal 16:27:49 dzimine, yes. I included it just because Fuel folks asked about it 16:27:56 +1 on it too 16:29:20 Nikolay, what do you say about "manage-db" ? 16:29:45 I remember Igor asked us to add it but am not sure exactly how important it is for him now 16:30:03 he had some problems with packaging because of it as far as I remember 16:30:15 I mean Igor Yozhikov 16:30:29 rakhmerov, did you create more bps based on your meeting with dzimine ? 16:30:59 akuznetsova, not yet, it's in progress, we will soon 16:31:12 no we did not but we probably should (bug at least) to see the scope visible. 16:31:24 we're just making various notes that we still need to think over 16:31:38 sure, we need to do it 16:31:45 ok. it means that list of bps for kilo-2 will be bigger 16:32:05 NikolayM, you here? 16:32:13 and it may help to add a dedicated “DB_model refactoring” blueprint as other tasks depend on it (at least 2). 16:32:15 yep 16:32:23 and/or bugs 16:33:20 #action rakhmerov, dzimine, create necessary BPs/bugs for the upcoming "cleaning up" work 16:33:26 action: dzimine - add blueprints/bugs and add critical of them to kilo-2 scope, rakhmerov will remove the ones he thinks wrong.. 16:33:27 haha 16:33:38 :))) 16:33:58 ok, moved away "manage-db" for now 16:34:14 we may ask folks from fuel to help with it 16:34:16 what about https://blueprints.launchpad.net/mistral/+spec/mistral-auth-middleware-option ? I guess it is quite 'big' feature, isn't it? 16:34:47 right, but it's now in low priority which means it's not 16:34:50 so it's ok 16:35:11 if it's not completed in 3 weeks we can easily move it 16:35:47 ok 16:36:13 dzimine, what do you think about "aciton providers"? 16:36:22 move out. 16:36:26 https://blueprints.launchpad.net/mistral/+spec/action-providers 16:36:48 I hoped to bring more developers to this but we lost some to sickness… 16:36:49 I know we still owe Winson a response to his letter but not sure how important it is for you 16:37:02 ooh, it's bad to hear 16:37:08 response is important - we want to be clear on design 16:37:16 tomorrow 16:37:26 but doing it - we won’t have time due to bugs / critical additions. 16:37:33 I'll do it tomorrow first thing 16:37:55 #action rakhmerov, NikolayM: reply to Winson on action providers design 16:38:03 ok, clear 16:38:43 done 16:38:47 anything else? 16:39:00 I'm personally still hoping to tackle Script Action 16:39:19 really would love to see that thing 16:39:40 so suggesting that we leave it 16:40:11 I think Nikolay is the best candidate to get it knocked out 16:41:10 dzimine, one more thing I'd like to ask you about is to clarify a BP definition with Winson: https://blueprints.launchpad.net/mistral/+spec/mistral-runtime-context 16:41:29 I asked him some questions about it via email but still didn't get a reply 16:42:14 ok. 16:42:16 the thing is that this BP doesn't make a lot of sense to me anymore 16:42:20 ok 16:42:33 #action dzimine, clarify https://blueprints.launchpad.net/mistral/+spec/mistral-runtime-context definition with Winson 16:43:26 ok, looks like we now have some room for new blueprints 16:43:56 anything else on that part? 16:44:08 some other thoughts? 16:44:56 #topic Open discussion 16:45:36 please go ahead if you have anything to discuss 16:45:55 ooh, btw 16:46:13 I already mentioned we now have some problems with environment tests 16:46:25 just for your information 16:46:50 they now basically are blocking the whole process of development 16:46:56 unit tests? 16:47:00 yes 16:47:14 we have about 5-6 patches that we can't merge in because these tests keep failing 16:47:28 even though non of these patches are related to environments 16:47:33 so 16:47:57 I think I'm close to fixing them and will try to do it asap, ideally tomorrow 16:48:02 just be aware of it 16:48:27 the bad news is that they seem to be not very easy to trace 16:48:40 because they occur not every time 16:48:56 talking about failing tests, rakhmerov what about update_action test in your commit ? 16:49:03 and actually never on my local machine ) 16:49:18 that one is still on you :) 16:49:26 I was hoping you would take a look at it 16:49:47 I did spend a few mins on it but was unable to see the problem 16:49:49 won't you add a couple of unit tests that check update too? 16:50:00 so maybe something is wrong with the test itself, dunno 16:50:08 ooh, sure 16:50:11 I'll do 16:50:38 maybe it is some issue on cli side? 16:50:39 #action rakhmerov, add a couple of unit tests checking "updated_at population 16:50:57 yes, that's what I honestly think it is 16:51:05 very likely 16:51:42 so I think that's it from my side 16:51:48 anything else folks? 16:52:37 nothing from my side 16:52:37 ok, let's wrap up for today 16:52:47 ok, thanks to everyone! 16:52:51 OK, thanks 16:52:56 have a good week ) 16:53:03 bye-bye 16:53:05 bye 16:53:11 #endmeeting