16:01:54 #startmeeting Mistral 16:01:56 Meeting started Mon May 23 16:01:54 2016 UTC and is due to finish in 60 minutes. The chair is rakhmerov. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:57 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:02:00 The meeting name has been set to 'mistral' 16:02:12 hi 16:02:20 hey! 16:02:30 rbrady: how are you? 16:03:08 o/ 16:03:23 Hi 16:03:42 rakhmerov: doing well 16:04:45 ddeja: hi 16:04:48 mgershen: hi ) 16:04:53 hi' 16:05:02 hi hi ) 16:05:08 #topic Review Action items 16:05:15 o/ 16:05:56 1. rakhmerov: check if PyPi allows to rename releases 16:06:17 yes, it does but I still didn't do it 16:06:29 was doing something else 16:06:55 #topic Current status (progress, issues, roadblocks, further plans) 16:07:04 let's quickly tell our updates, if any 16:08:01 my status: doing a huge refactoring in Mistral engine, it's challenging but 100% required, https://review.openstack.org/#/c/317879/ 16:08:13 most of the tests already started passing 16:08:13 working on mistral-fail-transition-message. 16:08:25 I still didn't get the chance to complete the test for validate action cli call 16:08:47 My status: Not many work unfortunately, I still didn't recover fully and I didn't come back to office. But I have take a look into old patches implementing own RPC layer. I'm starting to working on rebasing them from Wednesday 16:08:54 mgershen: I suggest you add a test in a separate patch, IMO it's ok in case of functional tests 16:09:23 ddeja: ok, sure. Take care of yourself and get better 16:09:44 OK, I'll push later today or tomorrow. 16:09:56 ddeja: once you're back, find me in IRC and we'll discuss your next steps 16:10:02 I worked on the bug 1581649 for a while. I eventually reverted TripleO to use eventlet again for now and will come back to this bug once the other integration tasks are done 16:10:04 bug 1581649 in Mistral "Action Execution Response Timeout" [High,New] https://launchpad.net/bugs/1581649 - Assigned to Ryan Brady (rbrady) 16:10:06 rakhmerov: Thanks, I'm ok now and starting regular work from Wednesday, so I hope to push this case much faster :) 16:10:18 rakhmerov: Is there a description of the refactoring goals/plans? 16:10:55 d0ugal: there's a bunch of blueprints that together explain what needs to be fixed 16:11:20 rakhmerov: k, I'll take a look. It would be good to reference them in the commit message 16:11:35 ddeja: feel better 16:11:56 d0ugal: yes, sure. It's just not complete yet, but you're right. I'll insert all needed info 16:12:03 for example, https://blueprints.launchpad.net/mistral/+spec/mistral-engine-error-handling 16:12:10 rakhmerov: thanks :) 16:12:22 once I started it I realized that a lot of things need to be improved 16:13:08 #action rakhmerov: add all necessary info (links to BPs and bugs) to engine refactoring patch 16:14:15 one more thing, kong also sent a patch to enforce upper constraints, now we're trying to backport it into stable/mitaka 16:14:38 because now this branch is stuck due to new version of oslo.messaging 16:15:02 #topic Discuss what should be finalized in Newton-1 16:16:00 here's what's assigned to Newton-1: https://launchpad.net/mistral/+milestone/newton-1 16:16:23 https://blueprints.launchpad.net/mistral/+spec/mistral-alternative-rpc 16:16:40 ddeja: I'll move it to Newton-2 for now 16:16:52 and reassign it to you 16:16:53 ok? 16:17:02 rakhmerov: OK 16:17:46 honestly, I'm not even sure if we'll get it done in Newton-2 but if we do it would be awesome 16:18:00 https://blueprints.launchpad.net/mistral/+spec/mistral-custom-actions-api 16:18:17 rakhmerov: I hope it can be done in Newton-2, a lot of work is already done 16:18:25 same here, just one week left in N-1 so need to move it to N-2 too 16:18:31 yes 16:18:36 hope so 16:19:21 rbrady: with Actions API, technically we can start working on it 16:19:42 at least writing some minimal spec with goals, approaches etc. 16:20:27 like we discussed, I can propose an initial spec before the end of N-2 and then we'll complete it and decide who's going to contribute and how 16:21:19 obviously we'll not finish it during a week but I think N-2 looks feasible 16:21:44 we discussed this BP internally and decided that it's a high priority thing for us too 16:21:48 I mean Nokia 16:22:45 #action rakhmerov: propose an initial spec for Custom Actions API 16:23:31 https://blueprints.launchpad.net/mistral/+spec/mistral-fail-transition-message 16:23:41 hparekh_: I think this one will be done 16:23:56 tell me if I'm wrong 16:23:58 rakhmerov: yrah it will be done in N-1 16:24:05 ok, great 16:24:10 I just updated its status 16:24:47 https://blueprints.launchpad.net/mistral/+spec/mistral-priority-task-scheduler 16:25:18 this one is on Winson (StackStorm) but he's now working on a different task so this one will be moved to a later milestone 16:25:29 I even think it should be N-3 for now 16:25:59 https://blueprints.launchpad.net/mistral/+spec/validate-ad-hoc-action-api 16:26:17 I expect that this one will be done in N-1 16:26:30 mgershen: seems like there's not too much left on it 16:26:38 right? 16:26:52 fix a client a little bit and functional tests 16:27:02 I think I can move this to done now 16:27:19 The client is a different project 16:27:33 formally yes 16:28:06 What do you think? Should I? The code is In for the API 16:28:09 for now, I'd keep it "IN PROGRESS" because we don't pay too much attention to a client project at LP 16:28:46 if you move it to done then please make sure there's a BP at a client LP project 16:29:00 so that we know how to track it 16:29:01 Ok 16:29:20 as far as other BPs, I'm confident that they will be done 16:29:42 If It doesn't have to wait for the test, there is no problem 16:29:42 except UI BPs that I first need to discuss with a UI developer (he's not here) 16:30:23 as far as bugs 16:31:03 it'd be good to fix https://bugs.launchpad.net/mistral/+bug/1581649 and https://bugs.launchpad.net/mistral/+bug/1584731 in N-1 16:31:06 Launchpad bug 1581649 in Mistral "Action Execution Response Timeout" [High,New] - Assigned to Ryan Brady (rbrady) 16:31:08 Launchpad bug 1584731 in Mistral "Intermitent ActionExecution not found" [Critical,New] 16:31:35 we've already done some investigation with rbrady on the first one and know approximately where the problem is 16:32:10 seems like it's an issue with eventlet under Apache 16:32:28 as far as the second one, any volunteers? 16:32:29 :) 16:32:49 I think it's something relatively simple 16:33:23 hparekh: do you think you'll have capacity this week to look at it? 16:33:28 or early next week 16:34:26 yeah sure I will finish my bp then i can look into it sure 16:34:29 rakhmerov: I plan on taking another go at it towards the end of this week, but I'm definitely open to help or collaborating 16:34:38 hparekh: ok, assigned to you 16:35:07 rakhmerov ok 16:35:24 rbrady: yes, thanks. I actually didn't understand something 16:35:31 you said that you switched back to Apache 16:35:43 but it does not work with Apache 16:35:58 I may have misunderstood you 16:36:10 rakhmerov: https://review.openstack.org/#/c/319262/ 16:36:36 ooh, I see 16:36:42 thanks 16:37:20 anyway, I'd like to solve this since a lot of people will be stumbling on it 16:37:24 rakhmerov: this should keep tripleo undercloud working for now, but the idea is apache would be a better place to serve it like nova and keystone 16:37:35 yes 16:38:22 mgershen: Michal, please also look at https://bugs.launchpad.net/mistral/+bug/1581514 once you have 30 mins 16:38:23 Launchpad bug 1581514 in Mistral "Misinterpretation of action execution state by ActionExecutionsController" [High,Confirmed] - Assigned to Michal Gershenzon (michal-gershenzon) 16:38:39 it's pretty simple and we can fix it sooner than later 16:39:42 as far as other bugs, I'll move 2-3 to N-2 as they won't be finished this week 16:39:47 rakhmerov: sure np 16:40:41 https://bugs.launchpad.net/mistral/+bug/1484521, https://bugs.launchpad.net/mistral/liberty/+bug/1424461 16:40:44 Launchpad bug 1484521 in Mistral "wait-before and retry policies directly call task_handler.run_existing_task() method via RPC" [High,Confirmed] - Assigned to Renat Akhmerov (rakhmerov) 16:40:45 Launchpad bug 1424461 in Mistral "Published vars lost for complex parallel join" [High,Confirmed] - Assigned to Renat Akhmerov (rakhmerov) 16:41:46 ok, let's move to the next topic 16:41:48 #topic Discuss Newton-2 scope 16:42:12 https://launchpad.net/mistral/+milestone/newton-2 16:42:38 there will be several additions as a legacy of N-1 16:43:20 for now, I'd like to discuss 4-5 major things probably that we need to tackle in N-2 16:44:04 I'll select BPs based on that and on the next meeting we need to discuss that again in details and assign tasks 16:44:41 so, the thing #1 - Custom Actions API 16:44:41 https://blueprints.launchpad.net/mistral/+spec/mistral-custom-actions-api 16:45:15 it causes a lot of pain already and it needs to be done sooner because it's a serious gap in API 16:45:34 no matter whether it's a Python API or not 16:46:06 I realized that probably we'll have to move that Python API (as well as probably some other stuff) into a separate subproject 16:46:13 like mistral-common 16:46:19 or something like this 16:46:26 but we'll discuss it in the spec 16:46:38 I would like to help with this if I can 16:47:15 d0ugal: sure, if you can please attend the next meeting 16:47:21 rakhmerov: do you want to start a spec patch or want one of use to do it? 16:47:29 rakhmerov: will do 16:47:30 s/use/us/ 16:47:49 rbrady: if you have time, please go ahead 16:47:58 it doesn't matter who starts it 16:47:59 rakhmerov: ack 16:48:15 kind of related to this: https://blueprints.launchpad.net/mistral/+spec/mistral-separate-openstack-actions 16:48:25 I think it's important too 16:48:36 * d0ugal reads 16:49:07 oh, I hadn't seen that one. Sounds like a great plan. 16:49:19 btw, this all comes from my head based on our summit discussions but if you disagree with something pls disagree out loud ) 16:49:56 d0ugal: yeah, there's many reasons why it should be done, better sooner 16:50:08 assigned it to N-2 16:50:57 ok, what else 16:51:37 I'd finally like to propose a spec for API v3: https://blueprints.launchpad.net/mistral/+spec/mistral-api-v3 16:52:13 it's been going on for a long time, I see that we need to start improving usability 16:52:27 speaking of API v3, I don't mean workflow language 16:52:55 language is ok, although we're planning a number of small additions to it (backwards compatible) 16:53:11 it would be great to expand that spec. it's not entirely clear from the lp description 16:53:18 #action rakhmerov: Propose a spec for API v3 in N-2 16:53:33 rbrady: yeah-yeah, true 16:53:56 I already started making some notes on what we need to fix in API v2 but I didn't sort them out yet 16:54:06 will try to share soon 16:54:09 ack 16:55:39 most likely, we'll also need https://blueprints.launchpad.net/mistral/+spec/mistral-multi-region-support 16:55:41 soon 16:55:48 will assign it to N-2 too 16:57:51 there's also one thing that I'd like to do: https://blueprints.launchpad.net/mistral/+spec/mistral-logo 16:57:51 :) 16:58:03 but we need a designer here I guess 16:58:14 anyway, share your ideas! 16:58:23 rakhmerov: I know who to ask :) 16:58:26 rakhmerov: I know a designer (the one who made the tripleo logo) 16:58:30 jrist: ^ 16:58:36 rbrady: ha, snap. 16:58:42 yes, jrist! 16:58:44 d0ugal: ooh, that would be awesome 16:58:45 haha 16:59:05 rakhmerov: how did Mistral get its name? 16:59:09 designer might be a stretch 16:59:21 I joked to jrist on Friday that he should make a Mistral logo, so I am glad one is wanted :) 16:59:22 ok, we're running out of time. I'll propose more BPs and bugs till the next meeting, let's discuss more next time 16:59:34 +1 16:59:41 rbrady: it was an idea of one of my managers at Mirantis :) 17:00:08 I don't know how it came up, I guess just because the word itself is pretty beautiful 17:00:27 Yeah, it's a cool name 17:00:27 d0ugal: haha, you really discussed that?? ) 17:00:40 rakhmerov: Yup, because he just done a logo for my python usergroup 17:00:44 anyway... time up :) 17:00:48 hahaha )) 17:00:50 awesome 17:00:59 yes, thanks for joining guys 17:01:01 bye 17:01:05 #endmeeting