16:00:13 <dims_> #startmeeting oslo
16:00:13 <dims_> courtesy ping for GheRivero, amotoki, amrith, bknudson, bnemec, dansmith, dhellmann, dougwig, e0ne, flaper87, garyk, harlowja, haypo,
16:00:13 <dims_> courtesy ping for ihrachyshka, jd__, jecarey, johnsom, jungleboyj, kgiusti, kragniz, lifeless, lintan, ozamiatin, redrobot, rpodolyaka, spamaps
16:00:13 <openstack> Meeting started Mon Dec 21 16:00:13 2015 UTC and is due to finish in 60 minutes.  The chair is dims_. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:14 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:15 <dims_> courtesy ping for sergmelikyan, sreshetnyak, sileht, sreshetnyak, stevemar, therve, thinrichs, toabctl, viktors, zhiyan, zzzeek, gcb
16:00:17 <openstack> The meeting name has been set to 'oslo'
16:00:18 <dims_> Anyone here today?
16:00:20 <dims_> :)
16:00:25 <rpodolyaka> o/
16:00:25 <gcb> hi
16:00:36 <SpamapS> Oddly enough I'm kind of here... since there's no open schools for me to be taking kids to ;)
16:00:44 <harlowja_at_home> yoooo
16:00:48 <bknudson_> hi
16:00:52 <jecarey> o/
16:00:53 <dims_> haha SpamapS
16:01:03 <dims_> hi bknudson_ jecarey rpodolyaka gcb
16:01:16 <bogdando> o/
16:01:22 <dims_> hi bogdando
16:01:35 <dims_> hopefully a quick one today
16:01:37 <dims_> #topic Red flags for/from liaisons
16:01:47 <bknudson_> nothing for keystone
16:02:28 <dims_> thanks bknudson_
16:02:31 <dims_> #topic Releases for Mitaka
16:02:31 <dims_> #link https://review.openstack.org/#/c/259707/
16:03:16 <harlowja_at_home> ^ looks ok to me
16:03:28 <dims_> rpodolyaka : can you please eye ball the oslo.db changes? see the list-changes job output
16:03:29 <bknudson_> nothing will break this week!
16:03:38 <rpodolyaka> dims: looking
16:03:53 <dims_> bknudson_ :)
16:03:59 <harlowja_at_home> bknudson_, nothing ever breaks, obviously :)
16:04:23 <dims_> harlowja_at_home : i deliberatly held back the oslo.utils review for the timeutils stuff
16:04:28 <harlowja_at_home> kk
16:04:33 <harlowja_at_home> good idear
16:04:36 <rpodolyaka> dims_: oslo.db changes look good to me
16:05:00 <rbradfor> dims_, sorry for the newbie question, what is list-changes job output?
16:05:11 <dims_> harlowja_at_home : bknudson_ : https://travis-ci.org/dims/ looks green except for a nova py34 break that happens only in travis (need to dig into it)
16:05:16 <harlowja_at_home> dims_,  do u know if there is any ongoing infra change or something to start to highlight depreciation warnings in some manner?
16:05:29 <harlowja_at_home> did that whole conversation as what to do about depreciation warnings go anywhere?
16:05:39 <dims_> rbradfor : look in the review link above look for "gate-releases-tox-list-changes" job
16:05:48 <dims_> https://review.openstack.org/#/c/259707/
16:05:50 <gcb> rbradfor, http://logs.openstack.org/07/259707/3/check/gate-releases-tox-list-changes/f7993cc/console.html
16:06:01 <rbradfor> dims_, gcb, got it, thanks.
16:06:20 <dims_> harlowja_at_home : not that i heard about. we'll have to kick start something, probably based on the keystone mode
16:06:22 <dims_> model
16:06:27 <harlowja_at_home> right
16:06:42 <harlowja_at_home> i'd even be happy with like a alternate log file that depreciation warnings go to
16:06:52 <harlowja_at_home> that shows up in CI, and people can go look at...
16:07:11 <harlowja_at_home> *similar to all the other log files produced from CI runs
16:07:11 <dims_> harlowja_at_home : that may be an easy thing to pull off
16:07:26 <harlowja_at_home> ya, might not be so hard
16:07:41 <dims_> let's find a pattern we can follow
16:07:51 <harlowja_at_home> def
16:07:52 <dims_> #topic Open discussion
16:07:52 <dims_> Any other stuck reviews?
16:08:33 <dims_> rbradfor : if you see the travis link, that shows us running a bunch of py27,py34 tests by inserting oslo.* from master
16:08:35 <bogdando> the work queue spec?
16:08:41 <ozamiatin_> dims_: hi, when we can add mutlinode grenade gate for zmq?
16:08:54 <ozamiatin_> dims_: how can I help with that?
16:09:16 <dims_> ozamiatin_ : whenever you are ready, need to figure out how to do that :)
16:09:46 <rbradfor> dims_, thanks, looking at the output. helps me understand the weekly release process.
16:10:03 <dims_> bogdando : so are you happy with what you have there in the spec?
16:10:07 <ozamiatin_> dims_: ok, I'll look into it :)
16:10:09 <bogdando> yes
16:10:19 <bogdando> dims_, added example flow for a call
16:10:21 <dims_> bogdando : do we need to outline the API in the spec or we can do that later?
16:10:23 <bogdando> addressed comments
16:10:39 <bogdando> That depends on how deep we go in specs
16:11:14 <bogdando> IMO, all API details should be outside
16:11:36 <bogdando> as you suggested for example https://etherpad.openstack.org/p/oslo-messaging-work-queue-api
16:11:36 <dims_> bogdando : looks like some traffic in etherpad
16:11:38 <dims_> https://etherpad.openstack.org/p/oslo-messaging-work-queue-api
16:11:46 <dims_> so i'll cast my +2 on the spec
16:11:50 <bogdando> thank you
16:12:03 <gcb> dims, harlowja_at_home> what's the right process if our new version of oslo lib breaks other projects  ?    just block the version in g-r  ?
16:12:29 <dims_> gcb : we block in g-r, cut a new release with a fix
16:12:50 <dims_> sometimes we cut a new release first since g-r takes a while
16:13:29 <dims_> harlowja_at_home : gcb : ozamiatin_ : please cast your vote on the work queue spec too
16:13:35 <gcb> you mean , fix  and  submit a commit in openstack/release firstly ?
16:13:37 <dims_> anyone else who is interested as well
16:14:11 <dims_> gcb : yes, fix in say oslo.messaging, submit a commit in releases/ repo and then submit a commit in requirements/ repo
16:14:11 <gcb> will look at the spec :-)
16:14:26 <dims_> thanks gcb : it has a long history
16:14:50 <gcb> dims_ , got it ,thanks
16:14:57 <harlowja_at_home> dims_ bogdando  ya, hmmm that one :-P i'm somewhat biased to say just move the taskflow jobboard concept to tooz and then poof, this whole spec sorta isn't needed (afaik)
16:15:09 <harlowja_at_home> so i'm refraining from my biased vote :-P
16:16:00 <dims_> harlowja_at_home : let's see how it shakes out...right now i am saying "yes, we want/need it" :)
16:16:17 <harlowja_at_home> ya, fair enough, idk how it will all shake out yet either
16:16:48 <dims_> gcb : do you want to take that timeutils up with the nova folks?
16:17:50 <gcb> yes, so I need talk with nova guys in IRC and submit new commit , right ?
16:18:01 <bogdando> harlowja, at least the failure modes and contracts might come in handy
16:18:16 <dims_> gcb : yes please, i'd say just submit a new commit first and then talk to them
16:18:16 <bogdando> harlowja, that is how things should have been designed for RPC
16:18:21 <harlowja_at_home> bogdando, agreed
16:18:41 <gcb> dims_ , ok, will do that
16:18:52 <dims_> so can we skip next week's meeting?
16:19:14 <dims_> meet next on Jan 4th?
16:19:22 <gcb> I think most of you are in holiday :-)
16:19:44 <rpodolyaka> that's the best time to work :P
16:19:50 <bknudson_> I'm ok with skipping next meeting
16:19:51 <dims_> haha
16:19:55 <ozamiatin_> dims_: ok to skip
16:20:27 <harlowja_at_home> sureee
16:20:34 <dims_> rpodolyaka : gcb : +1 and the CI would be all ours too
16:20:48 <rpodolyaka> :)
16:21:01 <dims_> cool.
16:21:11 <dims_> any other things we need to talk about?
16:21:41 <dims_> harlowja_at_home : you and me can poke on the deprecation stuff on infra
16:21:50 <harlowja_at_home> dims_, def
16:22:01 <rbradfor> dims_, I have a few log/config/service specific questions. I'll bring up in oslo channel.
16:22:07 <dims_> rbradfor : ack
16:23:00 <dims_> so Wish everyone happy holidays and a very happy new year as well. (Russia/Ukraine - we'll wish you again next month :)
16:23:13 <harlowja_at_home> :)
16:23:31 <gcb> :)
16:23:34 <dims_> thanks everyone
16:23:39 <harlowja_at_home> np!
16:23:48 <dims_> #endmeeting