16:01:06 #startmeeting oslo 16:01:07 Meeting started Mon Aug 8 16:01:06 2016 UTC and is due to finish in 60 minutes. The chair is harlowja_at_home. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:08 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:11 The meeting name has been set to 'oslo' 16:01:13 hello oslo! ;) 16:01:16 ihrachys, ;) 16:01:19 hi there: -P 16:01:22 :-P 16:01:29 courtesy ping for GheRivero, amotoki, amrith, bknudson, bnemec, dansmith, dhellmann, dims, dougwig, e0ne, flaper87, garyk, haypo, 16:01:29 courtesy ping for ihrachyshka, jd__, jecarey, johnsom, jungleboyj, kgiusti, kragniz, lifeless, lintan, ozamiatin, redrobot, rpodolyaka, spamaps 16:01:29 courtesy ping for sergmelikyan, sreshetnyak, sileht, sreshetnyak, stevemar, therve, thinrichs, toabctl, viktors, zhiyan, zzzeek, gcb, Nakato 16:01:36 o/ 16:01:38 o/ 16:01:38 o/ 16:01:40 oops, thats using the old ihrachys 16:01:52 yo yo 16:01:52 o/ What, I've been dropped from the list? 16:01:53 SHAME ON YOU 16:01:58 hi 16:01:59 hmmm 16:02:02 ./ 16:02:07 In another meeting so distracted. 16:02:07 o/ 16:02:10 \o/ 16:02:26 weird, i think i ran the wrong ping me script 16:02:27 ha 16:02:42 weirds 16:02:42 ha 16:02:54 it got me, must be the right one. who's this rbradfor person? 16:03:03 new guy? 16:03:07 ohhhh, i know 16:03:17 o/ 16:03:21 my other script also has a ping me header, i gotta remove that one 16:03:32 #topic Red flags for/from liaisons 16:03:40 Nothing to report here 16:03:55 amrith, your a funny guy? 16:04:01 no red flags from murano 16:04:07 Nothing for keystone that I know of. 16:04:08 no flags on neutron side, grafana clear 16:04:12 all quiet on the trove front. I have a quesiton that I'd like to raise to the team. (other than the "who's the rbradfor guy") 16:04:27 ihrachys, https://review.openstack.org/#/c/352370/ is needed right? 16:04:39 (not sure its red, but perhaps yellow flag?) 16:04:53 harlowja_at_home: ah right, shame on me. too many things to handle. :P 16:04:58 it's yellow-ish yet 16:05:02 my periodic job bot is dead (not sure why) but i'll check those when i get in to work 16:05:04 k 16:05:13 it's not as red as the fact that currently the whole neutron gate is busted, so I forgot about it 16:05:23 :) 16:05:56 harlowja: we'll aslo need to bump in gate: https://review.openstack.org/#/c/352374/ 16:06:12 kk 16:06:52 gcb, anything from the nova folks? 16:07:28 #topic Releases for newton 16:07:38 (will find gcb later to catch up/check up) 16:07:52 so besides the current oslo.db (for mitaka) 16:08:11 anyone else need a specific release of any library? (otherwise i'll just batch them all, assuming periodic jobs are ok) 16:08:24 mine periodic is good 16:09:19 cool 16:09:27 also everyone keep in mind 16:09:29 http://releases.openstack.org/newton/schedule.html 16:09:48 time slowly approaching 'Aug 22-26' 16:09:55 http://releases.openstack.org/newton/schedule.html#n-final-lib 16:10:21 o/ 16:10:33 \o 16:11:04 #topic What amrith wants to talk about 16:11:11 amrith whats up :-P 16:11:13 thx 16:11:21 I want to ask about oslo.log and log rotation 16:11:28 are there any best practices on it? 16:11:37 someone proposed a change in trove based on rotating file handlers. 16:11:56 I just wanted to make sure that we didn't go accept some seventh solution to a known problem ... 16:12:21 one of https://docs.python.org/2/library/logging.handlers.html#rotatingfilehandler ? 16:12:28 see: https://review.openstack.org/#/c/352257/ 16:12:50 yes 16:12:54 rotating file handler 16:13:04 logging.handlers.RotatingFileHandler 16:13:41 right, so i haven't heard of any best practices (specific to oslo.log) here 16:13:42 I'd love it if someone from the oslo team could provide some guidance on whether this is the recommended way in which we do this. 16:14:07 agreed, it'd be nice to have a best practices for this kind of rotation stuffs 16:14:24 because, knowing my luck, we'll say yes to the one solution that is incompatible with the next change coming down the road in oslo.log. 16:14:41 :-P 16:15:07 i think what's being done in that review is fine, but agreed, let me start a little 'usage best practices' for this kind of stuff 16:15:20 thanks harlowja_at_home 16:15:33 also, please confirm that there's one more version of oslo.context before newton :) 16:15:40 the last one was fun 16:15:49 but now we have the process in place 16:15:56 and I'd like to give it a quick 'test'. 16:16:01 i'm guessing there is one more :-P 16:16:03 * amrith ducks to avoid the flying tomatoes 16:16:15 oh, those were eggs. 16:16:27 there is 2.7 16:16:40 there hasn't been any merges recently, so may not be a release this week 16:16:51 but i'd be safe to say there would be one more 16:16:59 oh, we got 2.7.0, I was wondering if there was more :) 16:17:16 crap, ok. will put on my raincoat 16:17:40 it rains frog parts each time you guys do one of those things. 16:17:48 lol 16:17:58 we were talking about this around here recently. 16:17:59 tasty 16:18:13 it would be nice if we could send a signal to the service to cause the file handle to re-open 16:18:31 apache httpd supports this 16:18:37 for logging? 16:18:38 bknudson, I saw that; sighup to reopen config files. but not file handle for log files. 16:18:39 makes log rotation more efficient 16:19:08 The result of the internal discussion was to use RotatingFileHandler, I think. 16:19:24 would SIGHUP trigger https://docs.python.org/2/library/logging.handlers.html#logging.handlers.RotatingFileHandler.doRollover then? 16:19:51 SIGHUP would allow logrotate to work. 16:20:35 our service is a bit skittish. if you say SIGHUP, it'll drop everything and run away. 16:21:10 doesn't seem like it would be that hard to have a RotatingFileHandler that is connected into the SIGHUP stuffs 16:21:30 yes, some small changes and we should be able to get that rotating file handler stuff working. 16:21:42 ok, that was my only question. 16:22:29 cool 16:22:48 #topic Reviews needing review 16:23:18 any reviews people want to raise so that others can (hopefully) look at? 16:24:10 i think all of kens stuff @ https://review.openstack.org/#/q/status:merged+project:openstack/oslo.messaging+branch:feature/amqp-dispatch-router merged 16:24:22 this one, need more core-reviewers https://review.openstack.org/#/c/349887/ 16:24:31 soo i'm guessing i'll have to find him to do the merge of that feature branch back into main oslo.messaging 16:24:51 osh, ah yes, i'll look that over today 16:25:32 harlowja_at_home: thanks C: 16:25:39 np :) 16:26:11 #topic Open discussion 16:26:51 anything else people want to talk about? bring up? other? :-P 16:28:08 ok, guess we can call it then :) 16:28:23 thx for those who showed up!! :) 16:28:31 thanks harlowja_at_home 16:28:36 np :) 16:28:48 bye harlowja_at_home bknudson rbradfor 16:28:55 peace! 16:29:01 #endmeeting