15:01:20 #startmeeting oslo 15:01:22 Meeting started Mon Aug 27 15:01:20 2018 UTC and is due to finish in 60 minutes. The chair is bnemec. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:23 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:25 The meeting name has been set to 'oslo' 15:01:38 courtesy ping for amotoki, amrith, ansmith, bnemec, dansmith, dhellmann, dims 15:01:38 courtesy ping for dougwig, e0ne, electrocucaracha, flaper87, garyk, gcb, haypo 15:01:38 courtesy ping for jd__, johnsom, jungleboyj, kgiusti, kragniz, lhx_, njohnston 15:01:38 courtesy ping for raildo, redrobot, sileht, spamaps, sreshetnyak, stephenfin, stevemar 15:01:38 courtesy ping for therve, thinrichs, toabctl, zhiyan, zxy, zzzeek 15:01:50 o/ 15:01:52 Kind of here. 15:02:09 o/ 15:02:19 o/ 15:02:53 o/ 15:03:40 #link https://wiki.openstack.org/wiki/Meetings/Oslo#Agenda_for_Next_Meeting 15:03:50 o/ 15:04:21 #topic Red flags for/from liaisons 15:05:44 Nothing that I'm aware of from last week. 15:06:40 #topic Releases 15:06:55 We released castellan last week as an FFE. 15:07:07 Otherwise that was it. 15:07:40 I guess now that we're past the rc date we can start releasing stein? 15:08:24 bnemec: there are a few deprecations that are due to land 15:08:38 bnemec: they need to be done earlier rather than later 15:09:00 I'm assuming it's ok to start that process now on master, no? 15:09:07 kgiusti: deprecations or removals? 15:09:26 bnemec: gah - deprecated things that are due for removal, sorry 15:09:41 bnemec: remove them now? 15:10:08 Chuck Short proposed openstack/oslo.privsep master: Replace assertRaisesRegexp with assertRaisesRegex https://review.openstack.org/596793 15:10:40 kgiusti: Yeah, that's good to do early. 15:11:09 ok thanks 15:13:05 And I'll take a todo to figure out if we're good to start releasing stein versions of things. 15:13:28 #action bnemec check if we can release stein libraries 15:14:04 #topic Action items from last meeting 15:14:28 "Review patches listed in http://paste.openstack.org/show/727932/" 15:14:38 I believe we got through some of them, at least. 15:15:04 Have spent a lot of time chasing broken repos though. 15:15:17 We made progress on that too, fortunately. 15:15:29 here's a new list, it's much shorter: 15:15:30 #link http://paste.openstack.org/show/728832 15:15:50 looks like 23 left, if I'm doing math right 15:16:25 Okay, thanks. 15:16:32 #action review patches listed in http://paste.openstack.org/show/728832/ 15:17:51 "add moguimar to core ACL after review period ends" 15:17:54 Done 15:18:07 "review stestr migration backports" 15:18:20 I have one more that still needs to go in. 15:18:27 #link https://review.openstack.org/#/c/588060/ 15:19:35 Oh, there's also one for taskflow. 15:19:37 #link https://review.openstack.org/#/c/594439/ 15:20:43 So let's get those landed. 15:20:50 Otherwise that was it for action items. 15:21:29 #topic PTG planning etherpad 15:21:41 #link https://etherpad.openstack.org/p/oslo-stein-ptg-planning 15:21:46 bnemec : it looks like https://review.openstack.org/#/c/594439/2 depends on a patch I rolled into another one, so it might need a rebase 15:21:52 This is probably the final reminder of that. 15:22:40 dhellmann: Those two actually work as plain backports without combining anything. 15:23:06 looking at the "related changes" list, it appears to be stacked in a series? 15:23:13 (at least I think they were both passing) 15:23:18 sorry, I didn't notice there was a literal depends-on too 15:23:46 the depends-on links to a master patch 15:23:56 that has been merged 15:24:04 so I'm talking about https://review.openstack.org/#/c/591245/1 15:24:06 Oh, I should have removed that. 15:24:26 Although it should be a noop since it's stacked on the backport of the master patch. 15:24:50 so we want that one instead of my jumbo patch? 15:25:16 It feels a little cleaner if we don't have to squash patches. 15:25:17 I guess it does pass, so +2 15:25:28 agreed 15:25:48 Apparently the stestr migration isn't strictly necessary for this repo, but I think it's a good thing to do anyway. 15:26:35 Okay, I approved the pydot backport too so that should land now. 15:26:41 Thanks 15:27:52 I think that takes care of the broken repos topic too. 15:28:05 There may be others, but we'll fix them as we find them. 15:28:17 #topic PTG team photo 15:28:22 Specifically, does anyone want to do one? 15:28:47 I don't think we have in the past for this team, but I got the email about signing up last week. 15:29:12 I'll join in if we do one, but won't push folks to do it if there's not much interest 15:30:02 I'm not much of a picture person, so I probably won't sign us up unless someone specifically asks. :-) 15:30:06 Merged openstack/devstack-plugin-pika master: import zuul job settings from project-config https://review.openstack.org/588686 15:30:35 maybe we can get some body doubles to stand in for us 15:32:00 I like that plan. :-D 15:32:54 Anyway, contact me if you want a team picture from the PTG and I can ask about open time slots. 15:33:04 #topic VMT? 15:33:15 This came up last week. 15:33:35 Apparently the Oslo projects aren't vulnerability managed by the OpenStack VMT. 15:33:48 I can't remember if there was a reason for that or if it was just an oversight. 15:34:06 I imagine that initially they focused on the services 15:34:24 It _seems_ like we would want to be managed. 15:34:48 I agree, if they have the capacity to do it 15:35:00 The services are only as secure as the libraries they use. 15:35:29 Okay, I'll look into whether they would be willing to take us on. 15:35:33 yeah, we may just need to ask 15:35:53 #action bnemec to check with VMT about Oslo libraries 15:35:58 Merged openstack/devstack-plugin-zmq master: import zuul job settings from project-config https://review.openstack.org/595988 15:36:24 #topic uuidsentinel 15:37:09 This spawned quite the mailing list thread, so I thought I'd bring it up here in case we wanted to pull some more people into the meeting and have a more direct conversation. 15:37:48 sorry for throwing a wrench in that right before taking a day off 15:38:13 Merged openstack/devstack-plugin-pika master: import zuul job settings from project-config https://review.openstack.org/595987 15:38:19 it seems like the main feature of this thing is the simple API, so making a fixture would make it harder to use 15:38:47 so we have 2 ways to handle the global 15:39:25 1. we take the class, and nova keeps the global. The benefit there is adopting it in nova wouldn't require so many updates to imports. I'm not sure how much of a real benefit that is. 15:40:03 2. we take the class and add a global. That makes it easier to document how to use it and the adoption can just import the instance from oslo.utils 15:40:22 I'm not counting the idea of adding the global to sys.modules because I don't want us to do that. 15:40:49 I guess 1 would be like i18n, where the classes live in oslo but each project has an integration module. 15:40:55 yeah 15:41:00 that seems heavy for this case 15:41:08 there's no special configuration to do, like in i18n 15:41:14 Yeah 15:42:38 I guess I'm more comfortable with the global if it's in oslotest so it can't accidentally be abused in production code. 15:43:32 Mock has this pattern too, but AIUI mock is only used for testing. 15:43:43 (although I've been wrong about that kind of thing before) 15:44:51 ok, I guess I can go along with putting it in oslotest 15:46:08 I know Eric wanted it in utils because of uuidutils, but the fact that they share a name isn't a strong technical argument to me. 15:46:30 oslo.utils is a runtime library and this is a test module. 15:46:56 I don't think we want oslotest to depend on oslo.utils, so if we reimplement this to just call the uuid module directly that should be ok 15:47:07 There's precedent to have test fixtures in runtime libs, but if we're not going to do this as a fixture then I'm less comfortable with it. 15:47:14 yeah 15:47:22 Oh, that's right. There was the dependency thing too. 15:47:39 I guess we could also put it into oslo_utils.fixture 15:50:06 so either a new module in oslotest or oslo_utils.fixture works for me 15:50:17 I don't have a very strong opinion about either 15:50:27 I would probably lean slightly towards the latter 15:51:07 I suppose we could add it as a fixture but also provide the global for projects that are okay with that pattern? 15:51:32 oh, I meant just add the global in oslo_utils.fixture as a way to indicate that it's test code 15:52:09 so take all of efried's code and put it in that module and then nova's tests can import the instance of the global from there 15:52:09 Yeah, I'm just thinking that if we do both then we don't force that choice on anyone. 15:52:24 sure, though I can't imagine anyone using the more cumbersome API if they have the easy one 15:52:33 Clint 'SpamapS' Byrum proposed openstack/oslo.tools master: Remove spamaps from pings https://review.openstack.org/596828 15:52:45 Well, some people really dislike globals. :-) 15:52:59 sure 15:53:24 we could always add the fixture later if someone wants it 15:53:30 or now if you do :-) 15:53:42 Merged openstack/oslo.tools master: Remove spamaps from pings https://review.openstack.org/596828 15:53:58 No, I don't feel anywhere near that strongly about it. 15:54:07 I jumped in early with an opinion, but it's not very strongly held, so as long as folks are happy with the thing it's fine with me 15:54:17 This seems like a pretty harmless use of globals. 15:54:22 yeah 15:54:35 my anti-pattern detector has a hair trigger :-) 15:54:36 I've never really believed in absolute rules for programming. 15:54:52 It's a code smell for sure. 15:54:52 I have one absolute rule for programming. No rules. Ever. 15:55:29 :-) 15:55:48 :) 15:56:45 dhellmann: Do you want to propose that on the list then? 15:56:52 * bnemec can't remember exactly where that discussion ended up 15:57:17 Other than the proposal to resurrect incubator. ;-) 15:57:40 so I'll propose we add eric's code to oslo_utils.fixture? 15:57:47 Merged openstack/oslo.service master: Skips signal handling on Windows https://review.openstack.org/593897 15:57:54 Yeah 15:58:00 ok 15:59:24 #action dhellmann to respond to uuidsentinel thread 15:59:34 Okay, we're just about out of time 15:59:36 #topic Open discussion 15:59:50 #link http://lists.openstack.org/pipermail/openstack-dev/2018-August/133861.html 16:00:11 I guess the one thing would be that next Monday is a US holiday, so I won't be around to run the meeting. 16:00:27 I suspect a lot of our team won't be either. 16:00:48 I will be off 16:00:51 So I'm thinking we just cancel? 16:00:58 wfm 16:01:15 +1 16:01:22 The PTG is the next week so we'll just have to finish any last-minute scheduling asynchronously. 16:01:58 #action bnemec cancel oslo meeting for next week 16:02:37 Okay, we're over time. Thanks for joining everyone! 16:02:39 #endmeeting