16:02:22 #startmeeting Mistral 16:02:23 Meeting started Mon Jan 23 16:02:22 2017 UTC and is due to finish in 60 minutes. The chair is rakhmerov. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:02:24 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:02:27 The meeting name has been set to 'mistral' 16:02:35 hi 16:02:39 hello 16:02:56 ddeja: everything's fine? 16:03:38 rakhmerov: yeah, sure. How about you 16:04:10 aah, more or less ok too 16:04:28 a lot of stuff going on 16:04:37 ok, is there anybody else here? 16:04:40 d0ugal: ^ 16:04:57 mgershen1: ^ 16:05:06 rbrady: ^ 16:05:19 hey 16:05:23 hi Ryan 16:05:36 I reviewed your WIP, let's discuss it in a few 16:05:40 ack 16:05:46 ok, let's start 16:06:26 #topic Review action items 16:06:31 1. review https://review.openstack.org/#/c/411412/ 16:06:40 done (will discuss it later) 16:06:46 Hey all 16:06:49 2. rakhmerov: find Hardik's proposal on testing OpenStack actions 16:06:49 Sorry I'm late. 16:06:50 done 16:06:53 d0ugal: np 16:06:58 thanks for joining 16:07:04 #topic Current status 16:07:41 my status: sent a few relatively simple patches including fixing a bug with task() function w/o a task name, made a bunch of reviews 16:08:08 keep investigating big input size issue reported by tuan__ and colleagues 16:08:35 Hi Renat 16:08:42 let;s talk about it tomorrow 16:08:47 my status: finished refactoring of getting the rpc-related flag and finishing the multi-rabbit support in kombu driver. I'm hoping to get it merged before the freeze 16:08:50 i will try to provide more information 16:09:33 tuan__: yes, ok. I don't have any new updates on it now, I should have more tomorrow 16:10:17 ddeja: can you explain a bit why multi-rabbit support is needed? 16:10:18 I fixed an issue with name validation and posted this patch: https://review.openstack.org/412433 16:10:26 what use case does it cover? 16:10:30 Looks like I have a CI issue to resolve, but that aims to improve action loading in Mistral. 16:10:45 d0ugal: ok, cool 16:11:01 ddeja: and how does it actually work? 16:11:11 rakhmerov: when you have more than one rabbit host 16:11:28 and want to automatically switch beetwen them when one of them dies 16:11:30 ooh, you mean for rabbit deployed in HA? 16:11:33 yes 16:11:37 I see 16:11:48 but it's still one Rabbit cluster? 16:11:51 right? 16:11:53 yes 16:11:57 ok, now clear 16:12:07 I thought it's for multiple clusters :) 16:12:18 no no, that would be magic ;) 16:12:22 I was wondering why we would ever need it.. 16:12:27 yes 16:12:46 #topic Ocata-3 state 16:13:00 small announcement 16:13:09 this week we're releasing O-3 16:13:30 this cycle was very short comparing to the previous ones 16:14:03 yeah, scary short :-D 16:14:20 so, before this Fri we need to merge all the new features that we want to have in Ocata 16:14:55 I don't think we have many of those but please check whether you need something urgently 16:15:24 so, starting this Friday no new features in Ocata 16:15:59 we can use FFE if we need to but only if we really need something very much 16:17:14 I would also ask you to check all of your patches for everything to see if what is still possible to merge before Fri 16:17:24 maybe some small improvements, bugs etc. 16:17:32 sure 16:17:52 I believe we have lots of relatively small things that have been waiting their turn for a while 16:18:16 and please also review stuff actively this week 16:18:39 in general, this Ocata cycle turned to be pretty messy 16:18:44 mostly my fault, of course 16:19:07 although we discussed a lot of stuff in Barcelona, not much of that was really done 16:19:12 for various reasons 16:19:21 like in other projects, I guess 16:19:33 including changing priorities during development (internal influence) 16:19:58 ddeja: yeah, but usually we did slightly better in this regard 16:20:08 anyway, I think that's generally ok 16:20:23 that fact that priorities are changing is good 16:20:40 people are using Mistral and coming with new urgent requests 16:20:44 I think everyone was shocked how fast the time went 16:20:51 d0ugal: yeah 16:21:00 typically we would have 1.5 months more 16:21:15 ok 16:21:24 that's all I wanted to say 16:21:26 on this 16:21:45 we still have about a month for bugfixing etc. 16:22:39 Sounds good, there are lots of bugs and documentation improvements we can make :) 16:23:02 true 16:23:11 on documentation, the light is green 16:23:23 we can be improving it all the way till the PTG 16:23:37 (and beyond!) 16:23:43 yes ) 16:23:56 +1 16:23:59 and btw, I think we made a really noticeable progress on docs 16:24:11 mgershen: ooh, I again didn't realize you were here :) 16:24:13 hi! 16:24:31 Hi! 16:24:41 mgershen: Michal, any updates from your side? 16:24:53 mgershen: thanks for reviewing patches actively! 16:25:08 you're making good progress 16:25:20 I should update the documentation with the new function I added a few weeks back. 16:25:41 rakhmerov: thanks :) 16:25:42 mgershen: ok, good 16:26:00 #topic Open discussion 16:26:20 ok, any topics you'd like to discuss? 16:26:30 we put even more topics for the PTG 16:26:45 I think we now have VERY MUCH to discuss there 16:27:00 I'll be working on filling them with more details 16:27:24 not too much time left till then 16:28:03 rbrady, d0ugal: I reviewed a WIP for keystone utils, exceptions etc. in mistral-lib 16:28:18 I left some comments, please take a look 16:28:23 rakhmerov: thanks. I've been reading 16:28:37 I'll take a look later. 16:28:59 my big concern with this whole thing is decomposition of source code into multiple modules 16:29:29 maybe it's not something that we can find a good vision for, but I'm just bringing it up so we're more prepared before the PTG 16:29:54 for example, do we need to move all of our exceptions from 'mistral' to 'mistral-lib'? 16:30:09 rakhmerov: I can explain a little bit that might set some context 16:30:10 same about context thing, keystone, utils etc. 16:30:15 yes 16:30:55 my fear is that it won't be convenient during server-side development because 'mistral' will have another dependency that should be changing all the time 16:31:06 rbrady: yes, go ahead 16:31:43 so, we need to reasonable about what we keep in 'mistral' and what we move into 'mistral-lib' 16:32:01 rakhmerov: when I started moving code into the mistral_lib repo, I was under the assumption that mistral would take a dependency on mistral_lib 16:32:14 right 16:32:18 mistral_lib would then contain the minimum code needed for the actions 16:32:34 yes 16:32:46 I knew from past experience the keystone_utils were important if you were doing anything with openstack lients 16:32:52 so I started there 16:33:08 to move over the keystone utils, I needed the context 16:33:11 and it sucked in the rest? 16:33:22 I couldn't make a circular dependency, so the context was ported 16:33:27 yes! 16:33:32 aah... 16:33:35 I see now 16:33:50 I didn't realize it when I was reviewing the patch actually 16:34:26 hah.. 16:34:59 so somehow we should keep it small 16:35:19 so the conventions issue - I assumed the non-public classes and methods that would be subject to change would follow the underscore naming convention 16:35:21 maybe not all of the keystone stuff is needed that we have on the server-side? 16:35:57 that's a question I can look into, but I don't have an answer to that yet 16:35:58 rbrady: you mean even classes should contain _ if they are private to the project? 16:36:49 how typical is it for python? If it is pretty typical then it's probably OK 16:37:04 rakhmerov: https://www.python.org/dev/peps/pep-0008/ 16:37:12 I'm not insisting really, I just want to make it clear somehow for users of these public clases 16:37:48 rakhmerov: if you look at the oslo projects, they use underscores to mark private files, variables etc. 16:38:02 I've been thinking that most of the other information intended to be passed from server-side to a custom action - it would be appended to the context object 16:38:32 rbrady: yeah, but what I remembered is that this doesn't tell anything about module and class names 16:38:55 d0ugal: ok, no problem 16:39:10 d0ugal: yeah, I saw some 16:39:44 d0ugal, rbrady: ok, let's proceed with underscores, no objections 16:39:54 rakhmerov: it should be like this in python 16:39:56 rakhmerov: there are some naming guidelines for classes 16:40:24 honestly, I probably just don't like this underscore thing.. :) 16:40:34 but that's my personal issue though 16:40:38 nevermind 16:40:49 rahkmerov: lol 16:40:54 :) 16:41:07 yeah, I'm still kind of alien in Python 16:41:17 lol 16:41:20 although I've been using it for 4 years 16:41:26 ok 16:41:37 :) 16:41:37 * rbrady tries to find alien python shirt for rahkmerov 16:41:44 yeah :))) 16:42:06 that would be a really cool idea for a t-shirt design :) 16:42:49 since we are bringing funny stuff 16:42:53 http://dom.trojmiasto.pl/Mistral-i249.html 16:43:02 rahkmerov: I appreciate the review and will respond to the patch comments to keep the conversation going 16:43:11 "Still feel an alien in the Python world? You're not alone!" 16:43:13 just found out that there is a buliding developer in my city that is called mistral 16:43:22 nice 16:43:38 rbrady: ok, np 16:43:52 let's just try to prepare for the PTG as much as possible 16:43:58 rahkmerov: ack 16:44:09 including getting familiar with SS actions design 16:44:29 ddeja: haha, cool :) 16:44:44 sorry, I need to leave. I have some chores to do 16:44:53 that's better link :D http://www.mistral.ekolan.pl/ 16:44:57 * d0ugal waves 16:45:03 :D 16:45:06 bye d0ugal 16:45:06 d0ugal: ok, see you online tomorrow 16:45:12 well, for the underscore stuff 16:45:17 https://shahriar.svbtle.com/underscores-in-python 16:45:27 you guys can take a look to this one 16:45:32 but it is necessary 16:45:35 ok, rbrady: I don't see a simple solution for that dependency problems 16:45:42 we need to brainstorm it somehow 16:45:57 I'd like that ddeja to be also involved into this 16:46:06 rahkmerov: I will attempt to write up some thoughts to present it better to the group at PTG 16:46:10 he usually comes with good ideas 16:46:19 yes, please 16:46:45 rahkmerov: I think I might be able to explain it better in person. maybe. 16:46:48 I really want to knock it down in Pike 16:47:01 but for that we need to solve all the fundamental problems 16:47:08 yep 16:47:47 ok, if there's nothing else you'd like to discuss now we can close the meeting 16:47:56 12 mins left 16:47:59 rakhmerov: I'm done 16:48:04 ok 16:48:11 I'm good 16:48:22 ddeja: btw, do you have a context of this Actions API thing? 16:48:32 rakhmerov: a little bit 16:48:41 it'd be cool if you could participate too 16:48:50 at least in thinking and discussions 16:48:55 I can try ;) 16:49:10 it's not as simple as we thought it would be so we probably need more brains 16:49:29 ok 16:49:36 rahkmerov: my intent is to try to make it as simple as possible. I promise. :) 16:49:49 ddeja: we can discuss more it in our channel 16:49:59 rbrady: hope so! 16:50:04 ok, bye everyone 16:50:08 bye 16:50:12 thanks guys and have a good wekk 16:50:14 week 16:50:22 #endmeeting