15:00:26 #startmeeting oslo 15:00:26 Courtesy ping for bnemec, jungleboyj, moguimar, hberaud, kgiusti, redrobot, stephenfin, johnsom 15:00:26 #link https://wiki.openstack.org/wiki/Meetings/Oslo#Agenda_for_Next_Meeting 15:00:26 Meeting started Mon Sep 9 15:00:26 2019 UTC and is due to finish in 60 minutes. The chair is bnemec. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:28 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:31 The meeting name has been set to 'oslo' 15:00:32 o/ 15:00:35 o/ 15:00:39 o/ 15:00:40 o/ 15:01:36 o/ 15:02:36 #topic Red flags for/from liaisons 15:02:38 o/ 15:02:50 Nothing to raise from Octavia team 15:03:24 Nothing from Oslo 15:03:27 oops 15:03:29 barbican 15:03:36 moguimar: :-) 15:03:38 :facepalm: 15:04:02 The one major thing to note from the Oslo side is that we have merged the sighup fix so that services won't be completely restarted when using mutable config. 15:04:14 If you see any weird behavior as a result please let us know ASAP. 15:04:32 nothing from Cinder 15:05:43 Okay, sounds like we're good. 15:05:44 #topic Releases 15:06:10 \o/ 15:06:28 We're in feature freeze, so releases from here on out should be bugfix only, unless an FFE is granted. 15:07:34 Also note that I released all the things last week. We need to do that so when branches are cut they include all of the doc and test changes we normally don't release. 15:08:27 Otherwise I would expect release activity to slow down a bit here as we come to the end of the cycle. 15:09:03 I think that's all I've got. 15:09:09 #topic Action items from last meeting 15:09:17 "bnemec add gsantomaggio to oslo.messaging core list" 15:09:20 Done. \o/ 15:09:43 @bnemec thank you 15:10:08 My pleasure. :-) 15:10:18 "bnemec to ask keystone team about https://review.opendev.org/#/c/662830" 15:10:50 Pretty sure I did that, but still haven't heard anything back. 15:11:20 At this point I'm inclined to just go ahead and merge it. 15:11:33 lbragstad: ^ 15:11:36 Since it's a bug fix we could do that now. I'm not sure how high priority this is though. 15:12:06 bnemec: lbragstad and I are working in the same DFG now 15:12:32 Handy. :-) 15:12:37 yep 15:13:15 i can take a look at that today if needed 15:13:26 The other thing is that since this is a bugfix we could wait until next cycle and backport it. 15:14:27 lbragstad: I'm mostly just looking for a sanity check that this isn't horribly violating any keystone expectations of how tokens get used. 15:15:06 bnemec cool - that sounds good 15:16:09 Okay, we'll wait for lbragstad's input on that one then. 15:16:37 #topic Feature freeze 15:17:00 I mentioned it earlier, but we're in feature freeze now, both for Oslo and non-client libs. 15:17:32 That means nobody should merge any patches that would require a feature release from now until we branch stable/train. 15:18:13 Unless an FFE has been granted, and at this point I think we'd need approval from both me and the release team since we're out of the Oslo-specific freeze period. 15:18:46 On a related note... 15:18:49 #topic Deprecation of oslo.i18n Message.translate function 15:19:17 A bug was pointed out on the mailing list a couple of weeks ago that there was an issue with the Message.translate function. 15:19:33 It turns out we shadowed a unicode built-in function in our Message subclass. 15:20:13 That causes problems when we pass a Message object as a unicode to external libraries that try to use it as a non-i18n call. 15:20:45 I have a two-part fix up for this, starting at https://review.opendev.org/#/c/679092/ 15:21:04 The first one we can merge because it's exclusively a bug fix. 15:21:25 The followup is more of a question because it deprecates the existing function. 15:21:27 #link https://review.opendev.org/#/c/679321/1 15:21:47 However, I would like to ask for an FFE to get that in this cycle so we can do the removal ASAP. 15:22:04 If we wait til next cycle we'll have to wait an extra cycle before removing it, per our deprecation policy. 15:22:38 It's a pretty low risk thing since we don't document calling that function directly. Translation is supposed to happen via the i18n.translate module-level function. 15:23:19 I don't see any deprecation warnings logged in the tempest jobs on the patch, so I don't think any of the projects we're testing with call it directly. 15:24:48 So I wanted to bring this up for two reasons: 1) To get another core to look at that so we can have it ready to merge if we get an FFE 15:24:48 2) To see if anyone has any objections to me asking for an FFE on it 15:26:11 If I hear no objections during the meeting I'll probably go ahead and take it to the list. 15:27:13 Okay, moving on then. 15:27:18 #topic PTG/Forum 15:27:26 #link https://etherpad.openstack.org/p/oslo-shanghai-topics 15:27:45 Forum session proposals are now open. 15:28:15 can't go :( 15:28:22 I don't have any topics planned, but if anyone has anything that they think would benefit from a broad discussion at the Forum please feel free to submit and add to the etherpad. 15:28:28 bnemec: feel free to ping me for the castellan demo 15:28:34 There's a lot of that going around. :-/ 15:28:52 moguimar: Cool, I was planning on that. :-) 15:30:24 I don't have a lot else to say on that, other than to always keep in mind that if you run across anything you think would benefit from discussion at the PTG, please add it to the etherpad too. 15:30:39 #topic Cycle highlights 15:30:54 Now that we're coming to the end of the cycle, it's time for cycle highlights. 15:31:13 I believe there was an email to the ML about this, but basically it's some marketing bullet points for each project. 15:31:47 We don't always have them for Oslo because a lot of our work is not user-facing, so it's not terribly marketable. 15:32:18 However, if you worked on anything this cycle that you think should show up in the OpenStack marketing materials please let me know ASAP. 15:32:26 Oslo-related of course. ;-) 15:33:20 was castellan driver this or last cycle? 15:34:59 Last cycle, I believe. 15:35:10 I'm pretty sure I included it in the cycle highlights last time. 15:36:08 For reference, here's the cycle highlights from last time: 15:36:10 #link https://review.opendev.org/#/c/645019 15:36:24 Basically all config-related. 15:38:49 #topic Weekly Wayward Review 15:39:35 This one catches my eye: 15:39:36 #link https://review.opendev.org/#/c/672781/ 15:40:14 It's a kind of important fix since it results in broken rules in the generated policy. 15:40:54 lbragstad: I'm thinking I might go ahead and +2 since we've both reviewed each other's changes, and I only touched the tests. 15:41:41 And maybe that will get cmurphy's attention. I hesitate to ping her since I don't know if she's caught up from PTO yet. 15:42:09 bnemec: I can review it tomorrow morning 15:42:21 moguimar: Sounds good, thanks. 15:42:50 #action moguimar to review https://review.opendev.org/#/c/672781/ 15:43:39 Alright, we'll call that good. At some point here I'll probably stop doing the wayward review section until ussuri opens up since we don't want to be forcing patches in late in the cycle. 15:43:43 #topic Open discussion 15:43:48 Anything else this week? 15:44:33 not on my end 15:44:48 thanks moguimar 15:47:13 Okay, let's give everyone 13 minutes back. Thanks for joining! 15:47:16 #endmeeting