10:00:14 #startmeeting requirements 10:00:15 Meeting started Wed Jan 18 10:00:14 2017 UTC and is due to finish in 60 minutes. The chair is prometheanfire. Information about MeetBot at http://wiki.debian.org/MeetBot. 10:00:16 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 10:00:19 The meeting name has been set to 'requirements' 10:00:24 #topic rollcall 10:01:52 o/ 10:02:28 dirk: might just be us 10:02:42 probably, toabctl is still off 10:03:02 we need more regular contributors :) 10:03:10 indeed 10:03:31 #topic agenda 10:03:43 #topic Any controversies in the Queue? 10:03:58 #link https://review.openstack.org/420579 10:04:04 that's the only one I have 10:04:12 it's beind discussed on the lists already 10:05:01 dirk: you have anything? 10:05:50 other than monasca / kafka 10:05:56 it would be good to take a look at the pending issues 10:06:07 we have psutils, eventlet, and webob as major things to do right now 10:07:45 ya, I'd like to see what happens if we update the UC on psutils 10:08:07 the question is whether we try that soonish 10:08:10 don't think we can get the other two before freeze. 10:08:10 I would vote for that 10:08:11 ya 10:08:21 but we have oslo.reports and one other component blocking this 10:08:28 ? 10:08:39 oslo.reports has a requirements cap 10:08:46 so we need a newer release that includes the uncapping 10:08:55 and there was one tripleo component that had the same issue 10:09:09 are they not consuming gr? 10:09:23 I thought all of oslo would be at least 10:09:31 they are, but they need to merge the openstack bot proposal update and then do a release, and we need to update to the new release 10:09:44 ugh 10:09:51 and the tripleo-component is on follows-release, so the next release would be after the freeze 10:09:52 ya 10:10:43 well, we have to just poke them I guess 10:10:53 they probably want to do a release this week anyway 10:11:01 just make sure our stuff gets in 10:11:14 I'll try to find someone for that 10:11:39 any other ideas on that front? 10:14:03 ok, moving on 10:14:35 the last topic is kombu 4 10:14:45 there is some movement to release a kombu 4 compatible messaging 10:14:47 thanks, because the wiki is outdated 10:14:51 https://wiki.openstack.org/wiki/Meetings/Requirements 10:15:37 ok, so same problem there 10:15:39 I'm in favor of doing that, but we seem to have questions on ordering 10:16:37 sure 10:16:41 https://review.openstack.org/#/c/410176/ 10:16:45 is the discussion of that 10:18:06 well, in the past it was top down 10:18:14 ? 10:18:20 'upstream' breaks, then downstreams fix 10:18:23 we are upstream 10:18:34 so we bump, they break, then fix 10:18:56 the best way is if there's some crossover 10:20:23 it seems like they don't want to do that work though 10:21:24 it doesn't seem like there patch is too complex, (to make work with both), but I don't know kombu or oslo.messaging 10:22:30 so, not sure that'll get in either 10:22:44 kinda seeming like ocata is newton.1 10:23:59 dirk: that seem right? 10:24:47 prometheanfire: I'm fine with that approach of breaking when we have the core teams from oslo.messaging and the release prepared 10:25:03 might be easy enough if we get all the attention needed on this this week 10:25:21 ok, just be sure to note in reviews and ping people then 10:27:37 moving on 10:27:39 I have nothing 10:27:53 open discussion? 10:29:57 #topi open discussion 10:30:01 #topic open discussion 10:32:11 #endmeeting