16:03:47 #startmeeting Mistral 16:03:48 Meeting started Mon Jan 30 16:03:47 2017 UTC and is due to finish in 60 minutes. The chair is rakhmerov. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:03:49 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:03:52 The meeting name has been set to 'mistral' 16:03:54 hi 16:03:58 Hey! 16:04:21 Hi 16:04:47 o/ 16:05:06 ok, hi everyone 16:05:38 1 min 16:05:58 #topic Review Action Items 16:06:02 no action items 16:06:11 #topic Current Status 16:07:03 my status: sorting out blueprints and bugs at Launchpad after ocata 3 release, profiling Mistral in order to optimize it in case of big data stored in workflow context 16:07:24 sent one relatively simple patch 16:07:52 which is https://review.openstack.org/#/c/426704/ 16:08:05 if you have updates please go ahead 16:08:27 My status: finished working on kombu driver multi thread and mulit rabbit support 16:08:35 I'm also planning PTG and summit activities 16:08:47 ddeja: is everything merged? 16:08:52 and thanks to Renat and Dougal it was merged before the O-3 freeze :) 16:08:53 I don't really have anything to share this week :) 16:08:53 that you wanted 16:08:57 yup ;) 16:08:59 ok 16:09:01 \o/ 16:09:01 I have almost no status. Was on vacation last week. 16:09:14 d0ugal, sharatss: ok 16:09:27 sharatss: oh, good reminder - I will be on vacation next week. So don't look for me :) 16:09:27 Had to test congress actions, couldn't :( 16:09:30 d0ugal: can I announce your new role on the project? :) 16:09:35 rakhmerov: ha, sure 16:09:36 this week I'd like to double check if it works as expected and fix any bugs I will found in it 16:09:53 ddeja: yes, please 16:09:54 rakhmerov: but that did make it sound more exciting than it is :) 16:10:22 so, d0ugal will be the liaison for Mistral documentation in Pike 16:10:23 d0ugal: i will miss you :)) 16:10:53 congrats d0ugal :) 16:11:00 Thanks :) 16:11:19 there's a plan in the community to start more active communication with the projects in order to improve docs in OpenStack 16:11:19 Hopefully I can do the role justice ;) 16:11:34 so far I've been formally a liaison but I was a bad one 16:11:39 :) 16:11:57 yes, so we'll be counting on you :) 16:12:02 ok 16:12:22 d0ugal: congrats :) 16:12:37 I didn't have any special topics this week since I jumped into technical stuff and want to focus on it for now 16:13:13 my main goal though before the PTG is to prepare a good plan to discuss our topics we collected in the etherpad 16:13:37 I have one small topic: failing mysql/postgres gates 16:14:00 by a good plan I mean a more detailed list of topic and approximate time that we need to discuss it and when it's going to be 16:14:11 ddeja: yes, I was going to ask you about it actually 16:14:13 go ahead 16:14:19 share what you know 16:14:22 so, I spend some time looking on it 16:14:30 yep 16:14:34 i can reporduce it lokally using tox -e unit-mysql 16:14:45 ok 16:14:57 and I have a patch that fix it in a dummy way 16:15:23 ok, 1) what's the issue? 2) what's your fix that you call dummy? 16:15:47 https://review.openstack.org/#/c/426184/ 16:15:52 so that's the patch 16:16:11 and it deletes the importing of muranoclient 16:16:18 that's why it is dummy 16:16:27 so muranoclient is causing an issue? 16:16:31 but the gates are still failing on it 16:16:52 yes, since one or two tests requires the muronaclient 16:16:59 but most of the tests passes 16:17:09 on another patches, almost all tests not pass 16:17:32 so, the problem is with muronoclient, but I have no idea what the problem may be 16:17:53 If i use the python from .tox/unit-mysql/bin/python 16:18:07 hm... 16:18:13 and do importutils.load('python-muronoclient') 16:18:15 it just works 16:18:55 ddeja: murano :) 16:19:06 tuan__: yes 16:19:12 missclick ;) 16:19:18 but, what I can do for now 16:19:18 :D 16:19:35 is to put PBR inside the tests and see what the heck is happening when we use tox 16:19:42 I can try tommorow 16:20:01 yes, ok 16:20:05 interesting 16:20:07 that's all on this topic 16:20:17 the most interesting is what kong found 16:20:33 that it started to fail after we change the version of.... novaclient 16:21:14 after discussing ddeja problem 16:21:21 i have another one 16:21:22 ddeja: I'd suggest we write to openstack-dev 16:21:35 i think it should be discussed 16:21:47 rakhmerov: OK, I can send an email 16:21:50 seems like it makes sense to ask Murano team, they may know about it and be able to help 16:21:57 sure 16:22:07 +1 16:22:14 #action ddeja: send an email to openstack-dev about the issue with the murano client 16:22:46 Over time, I think it would be great if we could somehow isolate actions. 16:22:46 tuan__: what's your topic? 16:23:01 d0ugal: StackStorm did this 16:23:03 yeap, it is the topic of cacert 16:23:12 with using separate virtual envs 16:23:34 which also allows to use different dependencies 16:23:40 rakhmerov: ah, interesting. I was wondering how well that would work. containers would be another interesting approach :) 16:23:43 can i explain my topic 16:23:48 tuan__: please do 16:23:56 d0ugal: interetsing with docker 16:23:57 :D 16:24:00 ok 16:24:07 so, the problem like this 16:24:21 tuan__: sure, please do, it's just our regular way of having these meetings: we just keep telling our stuff no matter what others are doing :) 16:24:31 when we create pythonclient of other projects 16:24:48 in mistral i do not see the cacert that should be fetched 16:24:53 for instance 16:25:21 if inside workflow, i would like my novaclient talk to nova server by using cacert 16:25:38 and i do not see the cacert is fetched into novaclient in mistral 16:26:14 inside mistral/actions/openstack/actions.py 16:27:30 tuan__: ok, so the issue is that even though we can pass cacert from the client as --os-cacert parameter it doesn't get passed through to other OpenStack clients? 16:27:36 does that sound accurate? 16:28:45 because when I'm looking at the client code I see that we can pass it 16:28:56 we just pass it to mistralclient 16:29:07 how does mistralclient passes it to novaclient 16:29:18 no, I don't know yet 16:29:27 I'm just trying to clarify my understanding 16:29:28 of course we ccan do that by passing context of mistralclient 16:29:36 but i do not see it in the code 16:29:39 no, this is a bad way 16:29:45 ok, I understand 16:30:17 tuan__: please file a bug (look for an existing one) and change its priority to High 16:30:33 ok 16:30:50 we will talk to our team and file a bug ASAP 16:31:03 actually we did an implementation for this fix 16:31:04 :D 16:31:12 awesome 16:31:17 and now fixing unittest and testing it 16:31:19 is it already on review? 16:31:24 not yet 16:31:30 ok, cool 16:31:33 we are fixging unittest 16:31:39 but please have a bug report anyway 16:31:44 for sure 16:31:50 thanks 16:31:57 anything else folks? 16:32:13 I'm done 16:32:16 if no I'd like to keep this meeting short 16:32:22 ddeja: what about the kombu 16:32:23 ? 16:32:24 d0ugal? 16:32:48 tuan__: It's not that easy 16:33:00 I have one question, but it can wait until tomorrow :) so nothing from me. 16:33:12 but I'll file an patch as soon as I get it done 16:33:19 tuan__, ddeja: what are you discussing about kombu? 16:33:35 we can re-use failover mechanisms from kombu library 16:33:50 instead of what I did - writing our own ;) 16:34:00 so I need to do a little refactor 16:34:05 so we can use those 16:34:13 hm.. not sure I'm following you 16:34:34 can you briefly tell what exactly you're going to refactor/replace? 16:34:35 yeap, but i think you can take a look to the oslo messaging that for you i think it is an easy stuff 16:34:41 right now in kombu driver you can pass a number of rabbitMQ servers 16:34:42 as you did before 16:34:52 ddeja: ack 16:35:03 and connect to one of them, in case of failure, connect to another etc. 16:35:09 yes 16:35:17 the patch we recently merged 16:35:17 and I've implemented the logic of catching the exception and reconnecting 16:35:23 with "HA" it its title 16:35:29 yes 16:35:37 but, such mechanism is implemented in kombu library 16:35:43 I see 16:35:55 yeah, it's good if you can reuse it 16:35:58 so with a little refactor, we can delete some code from mistral and rely on kombu 16:36:06 yep, good 16:36:12 ddeja: btw, your patch is still good 16:36:13 :D 16:36:16 tuan__: that is why I'm saing it's not easy, I need to refactor the kombu_server 16:36:30 for kombu client it's a one-line change 16:36:33 okay, i understand 16:36:53 tuan__: are you using Kombu based RPC in CBAM? 16:37:06 or oslo.messaging based? Default one 16:37:14 rakhmerov: oh, and tuan__ is a person who pointed me that there is a failover mechanism in kombu ;) 16:37:18 I'm just not aware 16:37:34 I see, thanks tuan__ :) 16:38:26 ok, ending the meeting? 16:38:29 rakhmerov: we use rabbitmq 16:38:30 :D 16:38:49 tuan__: ok, I asked a little different thing, let's talk tomorrow 16:38:57 yeap 16:39:03 Istvan can probably help us answer this 16:39:16 ok, thanks everyone for joining 16:39:22 have a good week 16:39:31 #endmeeting