16:00:17 #startmeeting oslo 16:00:17 Meeting started Mon Mar 28 16:00:17 2016 UTC and is due to finish in 60 minutes. The chair is dims. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:18 courtesy ping for GheRivero, amotoki, amrith, bknudson, bnemec, dansmith, dhellmann, dougwig, e0ne, flaper87, garyk, harlowja, haypo, 16:00:18 courtesy ping for ihrachyshka, jd__, jecarey, johnsom, jungleboyj, kgiusti, kragniz, lifeless, lintan, ozamiatin, redrobot, rpodolyaka, spamaps 16:00:18 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:19 courtesy ping for sergmelikyan, sreshetnyak, sileht, sreshetnyak, stevemar, therve, thinrichs, toabctl, viktors, zhiyan, zzzeek, gcb 16:00:20 courtesy ping for dukhlov, lxsli, rbradfor, mikal, nakato, tcammann1, browne, 16:00:21 The meeting name has been set to 'oslo' 16:00:22 o. 16:00:23 o/ 16:00:23 o/ 16:00:23 o/ 16:00:25 hi 16:00:25 hi 16:00:26 0/ 16:00:26 \o 16:00:28 ./ 16:00:29 o/ (partial attention) 16:00:30 o/ 16:00:47 miqui (new) 0/ 16:00:47 hi rbradfor johnsom rpodolyaka e0ne bknudson jecarey jroll amrith dhellmann kgiusti 16:00:52 hi miqui 16:00:55 hi dims 16:00:59 welcome miqui 16:01:00 hi dims.. 16:01:18 #topic Mitaka update 16:01:19 hi all... 16:01:25 o/ 16:01:34 we ended up doing one last batch from stable/mitaka branches last night 16:01:52 oslo.messaging 4.6.0 broke windows CI. Fix is in progress (https://review.openstack.org/#/c/298195/) 16:01:54 o/ 16:02:06 so we'll end up with a 4.6.1 for oslo.messaging 16:02:40 did anyone else see any CI failures? please holler immediately 16:02:55 windows CI? 16:03:00 bknudson : yep 16:03:20 bknudson claudiu pinged me early in the AM and we came up with that fix 16:03:39 #topic Red flags for/from liaisons 16:03:49 they don't report CI failures to gerrit they report to you? 16:03:52 dims: Nothing from Cinder. 16:03:52 none from trove at this time. 16:04:04 thanks jungleboyj amrith 16:04:12 no red flags from keystone that I know of 16:04:29 thanks bknudson 16:04:40 I found an issue where networkx changed it's module paths in 1.11, but that only impacted a documentation feature in TaskFlow. I put a quick patch up for that. Otherwise nothing from LBaaS 16:04:59 we'll need to make sure requirements branch of stable/mitaka has the right upper-constraints. already pinged mriedem about it 16:05:20 johnsom : ack thanks 16:06:19 k let's switch to open discussion as i don't have any other topics 16:06:21 #topic Open discussion 16:06:54 so, I've been working with harlowja on his advocacy work. 16:07:05 hi , am thinking into looking at oslo.logging first... 16:07:16 everyone, please look at the Design Summit schedule 16:07:18 #link http://markmail.org/message/yeg57r5yyddveoka 16:07:20 * amrith waits for a break in the traffic 16:07:32 rbradfor : got a etherpad? 16:07:47 miqui : sounds good 16:07:49 one part of advocacy is blogging, and one part of blogging is a planned approach. See https://etherpad.openstack.org/p/oslo_blog 16:08:09 any volunteers for blogging? ^^ 16:08:19 dims, happy to help with blogging 16:08:21 dims, we are seeking volunteers in Newton to put their name on a oslo project, and then a calendar week 16:08:40 rbradfor : looks promising 16:08:50 while we have a much bigger picture in advocacy, this is the background resource work. 16:09:00 rbradfor : somehow reuse the blogging material into documentation too? 16:09:01 maybe I could blog about the soon to be obsolete isotime() function :) 16:09:09 LOL +1 amrith 16:09:21 seriously, yes, we should amrith 16:09:23 I will be taking that conversation to the mailing list as discussed at last OSLO meeting. 16:09:31 we are also wanting the blogger to update developer docs with better examples, following the examples of oslo.log (which includes actual docs/source/examples/*.py, and that running codde is embedded into usage documentation 16:09:37 I have written up a lengthy description of the issues 16:09:45 and some possible solutions. 16:09:56 amrith, absolutely, we want exactly these types of issues also 16:10:27 * amrith makes a note to update Wikipedia entry for 'lightning rod' 16:10:59 amrith, speaking of wiki, what does OpenStack have about projects? 16:11:30 rbradford, say again plz 16:11:34 rbradfor : project vs tenant? 16:11:52 #link https://en.wikipedia.org/wiki/OpenStack 16:11:55 https://en.wikipedia.org/wiki/OpenStack 16:11:59 no mention of Olso, will have to change that. 16:12:16 dims, you talking about context? 16:12:17 ah ok 16:12:33 ah, good point 16:12:35 rbradfor : misunderstood "OpenStack have about projects" 16:12:40 I have a note to also add more details about Trove. 16:12:47 dims, ok. 16:13:58 #link https://etherpad.openstack.org/p/oslo_blog 16:14:03 oslo people might find this interesting -- proposed switching keystone to use oslo.db's opportunistic testing -- https://review.openstack.org/#/c/295837/ 16:14:42 it found a few issues with keystone's unit tests 16:15:02 bknudson : nice 16:15:36 nice! 16:15:38 reminds me, not sure if i posted this already - DSVM jobs now generate a deprecations.txt - http://logs.openstack.org/58/294758/18/check/gate-tempest-dsvm-full/713d8bb/logs/deprecations.txt.gz 16:16:06 dims: very good change! 16:16:07 thanks 16:16:10 dims, I'm not sure you have mentioned it before, but I've been looking at them, it's great. 16:16:33 dims, inspired one now merged patch 16:16:35 thanks. bknudson : glance seems to be generating deprecations from keystone a lot 16:17:10 rbradfor : cool 16:17:33 anyone get a change to see ozamiatin 's zmq status to ML? 16:17:58 #link http://markmail.org/message/owimiyhpe6aj4v3v 16:18:07 hopefully the deprecation messages are clear enough for the problems to be fixed. 16:18:11 dims, it also produced a great flameout also, seems keystone has it's own inconistencies in renamed options 16:18:54 bknudson : so the idea is to look at the count (first column) then go searching logs 16:19:01 rbradfor : ack 16:19:22 kgiusti : haven't asked you in a while here, all's well in qpid-proton-land? 16:19:46 dims: as well as ever :P 16:19:53 haha 16:19:54 I'm working on a summit preso 16:20:07 nice 16:20:09 explaining the work I'm doing with qpid-dispatch router 16:20:13 and oslo.messaging 16:20:23 bring rotten tomatoes 16:21:18 ozamiatin's status puts me to shame .... 16:21:50 :) 16:21:53 I'll get a formal status together for summit 16:22:05 kgiusti : ack thanks 16:22:17 anyone here not making it to the summit? 16:22:54 dims, I'll be attending 16:23:16 thanks rbradfor 16:23:17 shall we do a roll call? 16:23:24 I will be attending as well 16:23:59 me three 16:24:08 dims, when do you think we will have a schedule of Oslo design slots? 16:24:22 anyone who can't make it, please let harlowja and me know how to make sure you are involved we can do hangouts etc 16:25:18 rbradfor : the time slots are ready, the etherpad has ideas, so we should all try to figure out which goes where and combine talks if needed 16:25:33 rbradfor : harlowja is on point for that 16:25:38 dims, I'd not seen an anouncement of the timeslots. 16:25:39 am sure he can use help 16:25:49 dims, happy to help! 16:26:12 rbradfor : if you scroll back i posted link 16:26:17 rbradfor http://markmail.org/message/yeg57r5yyddveoka 16:26:35 dims, thanks, missed that. 16:27:37 one success...oslo.messaging now advertises python 3 support as we have a functional test that runs python3 + rabbit 16:28:21 anything else from anyone? 16:28:46 thanks everyone. talk to you all next week 16:28:53 #endmeeting