14:00:03 <gcb> #startmeeting  oslo
14:00:04 <openstack> Meeting started Mon Jul 31 14:00:03 2017 UTC and is due to finish in 60 minutes.  The chair is gcb. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:05 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:07 <openstack> The meeting name has been set to 'oslo'
14:00:11 <gcb> courtesy ping for amotoki, amrith, bknudson, bnemec, crushil, dansmith, dhellmann
14:00:11 <gcb> courtesy ping for dims, dougwig, e0ne, electrocucaracha, flaper87, garyk, gcb
14:00:11 <gcb> courtesy ping for GheRivero, haypo, jd__, jecarey, johnsom, jungleboyj, kgiusti
14:00:11 <gcb> courtesy ping for kragniz, lhx_, lifeless, lxsli, Nakato, ozamiatin, rbradfor
14:00:11 <gcb> courtesy ping for redrobot, rpodolyaka, sergmelikyan, sileht, spamaps, sreshetnyak, sreshetnyak
14:00:13 <gcb> courtesy ping for stevemar, therve, thinrichs, toabctl, viktors, zhiyan, zzzeek
14:00:17 <crushil> \o
14:00:19 <kgiusti> o/
14:00:32 <jungleboyj> @!
14:00:32 <_pewp_> jungleboyj (◍˃̶ᗜ˂̶◍)ノ”
14:00:47 <dhellmann> o/
14:00:58 <gcb> \o/ welcome everyone
14:01:12 <gcb> #topic Red flags for/from liaisons
14:01:37 <jungleboyj> Nothing to report from Cinder.  :-)
14:01:59 <gcb> jungleboyj, thanks
14:02:20 <amotoki> hi, not a red flag but i have one bug which affects many projects in doc-mirgation
14:02:22 <amotoki> https://bugs.launchpad.net/oslo.config/+bug/1705245
14:02:22 <openstack> Launchpad bug 1705245 in oslo.config "sphinxext: duplicated group names in the rendered text" [Undecided,New]
14:02:59 <jungleboyj> amotoki:  I have been seeing that one too.
14:03:13 <jungleboyj> I think I figured out part of the problem.
14:04:06 <amotoki> do you see several causes?
14:05:41 <jungleboyj> Well, the one I did see was because it looks like it is rendering the tables and then when it tries to include them into the doc it shows up as a duplicate.
14:06:23 <jungleboyj> You can either changes the included files to use the .inc file extension or you can exclude the paths with those files in the setup for sphinx.
14:06:51 <jungleboyj> I haven't tried either yet as I just found the possible problem yesterday.
14:07:34 <jungleboyj> I can put what I found into the bug.
14:08:06 <gcb> amotoki: I don't have idea about this bug, will dig into tomorrow if others have no time to dig :-)
14:08:18 <gcb> jungleboyj: please add what you found
14:08:28 <amotoki> thanks. I also try to dig into the detail.
14:08:40 <jungleboyj> gcb:  Will do.  :-)
14:08:54 <jungleboyj> Dealing with several doc build issues.
14:09:15 <gcb> other red flags ?
14:09:35 <gcb> #topic Releases
14:10:02 <gcb> we just cut off branch stable/pike for each oslo library last week
14:10:53 <gcb> will hold on master release until cycle Queens is open, and will release stable/pike if we fix critical bugs
14:11:59 <gcb> please ping me if you think we need a new release for stable/pike
14:12:13 <gcb> #topic Denver PTG
14:13:33 <gcb> The next PTG is closing, please add item in https://etherpad.openstack.org/p/oslo-ptg-queens
14:14:05 <gcb> If you didn't get budget from your manager, please try to apply the travel support program and let me know:
14:14:05 <gcb> The second round of travel support is still taking applications until August 6t
14:14:28 <gcb> s/6t/6th
14:14:35 <gcb> https://openstackfoundation.formstack.com/forms/travelsupportptg_denver
14:14:47 <gcb> above is the link for travel support
14:16:24 <gcb> #topic PTL for Queens
14:17:37 <gcb> according to https://releases.openstack.org/pike/schedule.html,  Jul 31 - Aug 04  is week for Queens PTLs self-nomination
14:18:10 <gcb> As you know, I don't intend to run for run Oslo PTL for Queens  and post the email in http://lists.openstack.org/pipermail/openstack-dev/2017-July/119780.html
14:18:29 <gcb> Feel free to ping me if you want to run for Oslo PTL. I would be glad to help
14:19:18 <dhellmann> I would also be happy to act as a mentor if we have a new ptl candidate
14:20:04 <gcb> dhellmann: thanks , if no one else is in a position at the moment where they can do this then I'm up for another round
14:20:33 <gcb> I hope we can find a new ptl candidate :-)
14:21:38 <dhellmann> ++
14:23:23 <gcb> so please submit  ptl nomination candidacy before the deadline if any oslo core reviewers want to run for PTL
14:23:40 <gcb> #topic Open discussion
14:24:30 <kgiusti> hey - we've got some problems is messaging land...
14:24:58 <kgiusti> first the easy one: kombu 4.10 was released and breaks an assumption in one of the rabbit unit tests
14:25:30 <kgiusti> I have a fix - I think it's ok to remove that assumption
14:26:05 <kgiusti> But... there's a bigger problem looming:  it seems that nova is relying on vhost support from messaging.
14:26:36 <kgiusti> that's a problem because the notion of "apache httpd vhost" is not common for all messaging systems.
14:27:07 <kgiusti> for example qpidd, activemq - no notion of vhost
14:27:34 <gcb> kgiusti: ack , the first issue http://logs.openstack.org/71/489171/1/check/gate-oslo.messaging-python27-ubuntu-xenial/51ce7ca/testr_results.html.gz can be fixed easily
14:27:56 <kgiusti> I think I have a way to mimic that feature in amqp1, but as far as zeromq, kafka are concerned I don't have an answer yet.
14:28:19 <kgiusti> gcb: for that I have https://review.openstack.org/#/c/488563/1
14:28:39 <gcb> kgiusti, you mean nova are using vhost now ?
14:29:01 <kgiusti> It appears so - see devstack: http://git.openstack.org/cgit/openstack-dev/devstack/tree/lib/rpc_backend#n112
14:30:06 <kgiusti> I'm working on a couple of patches that can fix this for amqp1 (I think): https://review.openstack.org/#/c/488610/ and https://review.openstack.org/#/c/478537/
14:30:35 <kgiusti> and the qpid dispatch router is working on multi-tenant support, which should fix this but is not available as of today.
14:31:25 <kgiusti> that's all I have for now.
14:31:28 <gcb> kgiusti,  I guess vhost  should  be a option ,right ?
14:31:49 <kgiusti> it's actually part of the transport url definition
14:32:06 <kgiusti> so it's already part of the api
14:32:23 <kgiusti> we've (oslo) never actually tested it it appears
14:33:45 <kgiusti> whoever turned this on for devstack apparently decided to only support rabbitmq
14:34:04 <kgiusti> which is the prevailing viewpoint IMHO
14:34:26 <kgiusti> we really need nova et al to add non-rabbit tests to their CI process.
14:34:54 <kgiusti> or we'll always be hitting these issues ;(
14:38:39 <gcb> kgiusti,  so devstack works well for all drivers of oslo.messaging now,  you point out only rabbit uses this option
14:39:14 <kgiusti> gcb only rabbit supports that option, and now nova is apparently using it.
14:39:21 <gcb> kgiusti, we'd better add something to note only rabbit support vhost
14:40:15 <kgiusti> gcb: we're effectively removing support for all non-rabbit backends in that case - if that means nova can only work with rabbit
14:40:56 <kgiusti> I think the genie is out of the bottle - we need to get the other drivers to support vhost somehow.
14:41:27 <kgiusti> I think I can get amqp1 to work, but I can't imagine how a point-2-point system like zeromq will go about this.
14:41:33 <gcb> kgiusti, I saw your point, we should test other drivers not only for rabbit
14:42:05 <kgiusti> On our side I'll add a vhost-based functional test.
14:42:24 <kgiusti> I would've been nice to know this was coming at least.
14:42:56 <gcb> add two jobs?  one with vhost support , the other is not ?
14:43:30 <kgiusti> gcb:  not just add a test to the existing functional tests
14:43:50 <kgiusti> gcb: I'll post a patch at some point.
14:45:22 <gcb> kgiusti, ack.  I'm not sure Nova guys know the discussion,  did you post a email before ?  I didn't check the dev ML recently
14:46:00 <kgiusti> not yet - wanted to see if anyone else in the group had a better idea(s)
14:46:09 <kgiusti> but I'll do that today.
14:46:30 <gcb> kgiusti: thanks
14:46:51 <gcb> please add me as reviewer if you have any patch ready to review
14:47:13 <kgiusti> +1
14:48:01 <gcb> dhellmann,  I should hold off on landing the constraint URL changes for stable/pike,  I just read the email :(
14:49:03 <dhellmann> gcb : it's not a big deal. if they landed and cause a problem, we can revert
14:49:09 <dhellmann> the requirements repo should be branching soon anyway
14:49:36 <gcb> dhellmann, okay
14:50:20 <gcb> dhellmann,  do you think it is necessary to apply tc:approved tag for oslo libraries ?
14:51:26 <gcb> s/tc:approved/ tc:approved-released
14:56:08 <gcb> Our time is running out, maybe we can discuss the topic later in #openstack-oslo
14:56:18 <gcb> any other topic ?
14:57:57 <gcb> thanks everyone
14:58:11 <crushil> thanks
14:58:30 <gcb> #endmeeting