15:22:20 #startmeeting oslo 15:22:20 Courtesy ping for bnemec, jungleboyj, moguimar, hberaud, stephenfin, kgiusti, johnsom, e0ne, redrobot, bcafarel, smcginnis 15:22:20 #link https://wiki.openstack.org/wiki/Meetings/Oslo#Agenda_for_Next_Meeting 15:22:21 Meeting started Mon Mar 16 15:22:20 2020 UTC and is due to finish in 60 minutes. The chair is bnemec. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:22:22 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:22:24 The meeting name has been set to 'oslo' 15:22:29 o/ 15:22:30 o/ 15:22:39 o/ lol 15:22:43 o/ 15:22:53 I guess it's been a Monday for me too, I didn't notice 15:23:06 o/ 15:23:19 They keep adding more people to my Monday status meeting downstream, so it keeps taking longer and longer. :-/ 15:23:36 o/ 15:25:38 On the plus side, it will be better once Europe goes DST and we add an hour gap between these two meetings. 15:25:40 #topic Red flags for/from liaisons 15:26:38 Nothing from the Octavia team today 15:27:34 Nothing from Cinder. 15:27:47 I'm not coming up with anything objectionable that we did last week, but last week was also a bit drama-filled for me so I may be forgetting something. :-) 15:28:14 Drama filled? I think that describes life in general right now. 15:28:50 Yeah, this was piled on top of the "regular" drama that's going on. 15:29:13 I would really like life to be boring for a while. 15:29:30 Best of luck with that. 15:30:43 #topic Releases 15:31:07 Pretty sure I forgot to do these last week. Will try to rectify that this week. 15:31:20 So I guess not much to say on this topic. 15:31:28 #topic Action items from last meeting 15:31:43 "bnemec to follow up on https://review.opendev.org/#/c/689482/" 15:31:50 Let's see, did I actually do it this time? 15:32:02 Hey, I did! 15:32:23 That was the only action item last week, so hooray! 15:32:39 #topic Oslo core security team 15:32:43 lol 15:32:54 You may have seen my email about this last week. 15:33:38 There is an oslo-coresec group on Launchpad that is automatically notified of any security bugs in Oslo projects. 15:34:08 It was last updated ~6 years ago and I believe there are only two active contributors to Oslo left on it. 15:34:33 I've removed everyone else since we don't want to be notifying them of private security bugs if they don't need to know. 15:35:00 However, the main reason I wanted to bring it up in the meeting is I am looking for volunteers to be on the team. 15:35:18 There's not a whole lot to it. We don't get so many security bugs that it is a big time commitment. 15:35:45 bnemec: You can put me on the list. Not sure I will be able to do much with it, but willing to help out if something big comes up. 15:35:53 Fair warning, if I don't get volunteers I'll probably just start adding Oslo cores so we have _someone_ to look at things. ;-) 15:36:10 smcginnis: Great, thanks! 15:36:33 Mostly it's just so we have someone who can pre-review patches before they get proposed to public Gerrit. 15:36:35 lol, volun-told 15:36:57 Generally speaking, the coresec team isn't on the hook to fix every security bug that comes in. 15:37:26 Yeah, I can be on the list, again, I don't have a lot of spare cycles, but can try to help 15:38:03 VMT should do most of the paperwork right? (behind on that e-mail thread) 15:39:03 Yeah, in 6 years I've never had to fill out a CVE disclosure or anything. 15:39:15 And I was actually on two coresec teams for most of that time. 15:39:25 Nice 15:39:30 bnemec: Add me as well - I really need to work on my insecurities... 15:39:46 lol 15:40:29 Okay, that's a good start. I'll get y'all added shortly. 15:41:07 #action bnemec to add smcginnis, johnsom, and kgiusti to oslo-coresec 15:41:32 I'm open to adding more people so if anyone is interested after the meeting just let me know. 15:42:02 Alan Bishop proposed openstack/tooz master: Add TLS support in etcd3 and etcd3gw drivers https://review.opendev.org/710539 15:43:00 #topic Weekly Wayward Review 15:43:16 #link https://review.opendev.org/705064 15:43:24 This sounds promising, let's take a look... 15:44:20 Oh, that one's rather large. Might be a bit much to do during the meeting. 15:44:37 bnemec could be improved more but let's cut this into separate patches 15:45:08 hberaud: That would make it an easier review. 15:45:16 bnemec: I also introduced this one > https://github.com/4383/oslo.labs 15:45:31 bnemec: but still fresh paint on 15:46:00 bnemec: I don't know if this is something that we could host officially 15:46:18 and why not merge oslo.tools and oslo.labs 15:46:40 to centralize debug tools and personnal way to tests things on oslo 15:46:57 That's an interesting question. You could potentially go through the new library spec template and see if it helps clarify whether it's a good fit. 15:47:30 bnemec: I know that the major part of us have similar tools and scripts so centralize this could be effortless for all of us 15:47:43 bnemec: ack 15:48:48 Yeah, I don't have an immediate strong opinion one way or another. 15:48:54 bnemec: I want to avoid to reinvent the weel for each of us on our side 15:49:06 s/weel/wheel 15:49:24 We probably don't want to call it oslo.labs, as the oslo. libraries tend to be runtime dependencies for other services (oslo.tools being an exception to that). 15:49:42 bnemec: make sense 15:50:20 I also left some comments on https://review.opendev.org/#/c/707180 15:50:31 Needs a rebase and I'd like to see it added to the test script. 15:50:53 ack 15:51:20 hberaud: So you're going to spilt up https://review.opendev.org/705064, correct? 15:51:28 nope :) 15:52:08 I will continue to try to improve oslo.test but through new commits 15:52:16 follow-up patches 15:53:06 in other words I don't plan to split this one unless you really ask for 15:53:10 Okay, we'll just leave that one as to-review then. 15:53:20 I see smcginnis already did, so we're halfway there. :-) 15:53:29 :) 15:53:48 #topic Open discussion 15:54:01 That's all I had for the week. Anything else in the 7 minutes we have left? 15:54:10 I try to introduce functional tests on oslo.cache 15:54:12 If someone is an expert on oslo.middleware, could you take a look at: https://review.opendev.org/#/c/711127/ 15:54:53 I am helping implement the healthcheck code. I ran into some major confusion with how the oslo config is handled in the middleware library. 15:55:44 I have it working, but not sure I'm doing it the best way. There seems to be a chicken/egg with the configuration settings. 15:56:58 How so? 15:57:21 * bnemec is not an expert, but did look at the healthcheck code at one point in the semi-distant past 15:57:46 https://github.com/openstack/oslo.middleware/blob/master/oslo_middleware/healthcheck/__init__.py#L384 15:58:38 The config options don't materialize until the __init__, then it stevedore loads the backends based on that. So fixture override to test the backends is... interesting 15:58:53 https://github.com/openstack/oslo.middleware/blob/master/oslo_middleware/healthcheck/__init__.py#L388 15:59:25 The backend load is once and done, no mutate, so... The trick is setting the config settings, before they are needed, etc. 16:00:29 Ah. I don't even remember what backends this supports... 16:00:56 Well, there are two included, but we are adding one. It's really not much of a check without backends 16:01:25 Anyway, it is working, so this is a "if you have interest and time" 16:02:35 I ended up defining those opts twice, which seems to work ok. 16:03:45 Yeah, that might be a case where you just have to pre-register the opt in the test so you can set an override. 16:04:49 Which is not ideal because config opts are generally considered private to their defining project. :-/ 16:05:21 Right. 16:05:46 Okay, we're over time. If anyone comes up with a better solution to this let johnsom know. 16:05:59 hberaud: Didn't mean to ignore you. Do you need reviews or help? 16:06:10 Just to summarize the oslo.cache situation, the etcd3gw functional tests works well, but I currently facing some issues with the memcached functional tests who doesn't work (I need to deep dive), and in second time after these tests I reintroduced the dogpile backend based on pymemcache but without removing the python-memcached based backend, so we retrieve a functional oslo.cache, we surround the 16:06:12 situation to avoid similar situation, and we continue to modernize it (the both described parts are still WIP). 16:06:46 just to inform the oslo world of the advancement/situation 16:07:22 bnemec: help could be useful on the memcache functional tests 16:07:44 Okay, thanks for the update. 16:08:13 Sounds like adding tests for the various backends could probably be done separately once the functional testing framework is in place? 16:08:20 bnemec: I don't seen why it fail, so if someone have spare time... 16:08:56 bnemec: yes it could be done separately but we will only win 1 commit 16:09:18 bnemec: but why not :) 16:10:18 bnemec: this is the culprit => https://review.opendev.org/#/c/712479/ 16:10:18 Okay, going to make use of a meetbot command that I don't often use since we have a couple of followups. 16:10:18 #help johnsom looking for a better way to override oslo.middleware healthcheck backends opt 16:10:18 #help hberaud looking for assistance on memcache functional testing 16:10:31 #link https://review.opendev.org/#/c/712479/ 16:10:32 :) 16:10:59 that's all for me 16:11:06 Okay, sounds good. 16:11:57 We're well over time, so thanks for your patience everyone and catch you all next week. 16:12:07 If we don't all catch coronavirus in the meantime. ;-) 16:12:21 #endmeeting