15:03:47 #startmeeting oslo 15:03:47 Courtesy ping for bnemec, jungleboyj, moguimar, hberaud, stephenfin, kgiusti, johnsom, e0ne, redrobot, bcafarel 15:03:47 #link https://wiki.openstack.org/wiki/Meetings/Oslo#Agenda_for_Next_Meeting 15:03:48 Meeting started Mon Nov 11 15:03:47 2019 UTC and is due to finish in 60 minutes. The chair is bnemec. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:03:49 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:03:52 The meeting name has been set to 'oslo' 15:05:43 o/ 15:06:56 This might be a quick meeting with only two of us. :-) 15:08:33 #topic Red flags for/from liaisons 15:09:13 Nothing much that I know of on the Oslo side. The main thing is probably that I'm planning to start doing the regular weekly releases again this week. 15:09:59 cool 15:10:39 my team moved a meeting for this same slot, so I'll be multitasking a bit from now on 15:10:49 to* 15:11:18 Bleh. That's annoying. 15:11:22 yeah 15:11:25 no news from Barbican 15:11:45 but I minght touch some oslo.cache bits in the near future 15:11:51 After the time change here this is now scheduled for immediately after my team standup, but at least it doesn't straight up conflict. 15:12:34 Cool. 15:12:55 we are evaluating enabling TLS in memcached 15:13:36 probably for keystone IRC 15:14:05 I don't know if this will be helpful, but kmalloc was pushing for a change in memcached library there: https://review.opendev.org/#/c/634457/ 15:14:42 pymemcached is supposed to be a better library in general so it might support TLS better. Or it might not. :-) 15:15:07 cool 15:15:28 I was reading about python-memcached and found out about pymemcached 15:16:19 That work has kind of stalled, so it might be good to sync up with hberaud about it. kmalloc is out on paternity leave right now. 15:16:24 Octavia is mostly looking for the networkx patch to merge 15:16:30 at least based on the number of contributors/commits/forks it feels like pymemcached is indeed more mature 15:16:57 ok bnemec, noted 15:17:02 Yeah, and python-memcached has some janky design we've had to work around. 15:17:18 johnsom: Okay, I think I +2'd that already? Can you drop a link here? 15:18:18 #link https://review.opendev.org/689611 15:18:38 You did. I'm just not sure who else will review... Sigh 15:19:49 johnsom: I'll ping hberaud next time I see him online. There isn't a networkx expert who's going to look at this so he may as well go ahead and +2 it. :-) 15:20:07 Ok 15:20:32 In fact, I'll go ahead and action him on this in case he reads the meeting notes. 15:20:44 #action hberaud to approve https://review.opendev.org/689611 15:21:22 johnsom: Thanks again for doing that. 15:23:11 #topic Releases 15:23:29 As I mentioned earlier, I'm planning to start the weekly release cycle this week. 15:24:06 Up until the week before the summit there weren't any deliverables for ussuri yet and I didn't want to do the first releases right before summit. 15:24:19 Otherwise not much to report here since I haven't been doing them. :-) 15:24:27 #topic Action items from last meeting 15:24:50 "kgiusti to followup with Akira7216 about NATS driver for oslo.messaging" 15:25:14 I believe I saw a spec posted for this. 15:25:36 Alternate drivers for oslo.messaging were kind of a popular summit topic. 15:26:18 Not sure how likely it is that we'll be able to merge them, but we'll see. Might also be a good way to attract some new oslo.messaging contributors. 15:26:32 "Oslo cores to NOT merge py27 removal patches yet" 15:26:55 AFAIK none of them have merged, so \o/ 15:27:05 "bnemec send email to list about py27 plan for Oslo" 15:27:07 Done 15:27:23 That was it for action items. 15:27:31 #topic Virtual PTG 15:28:08 So we had a PTG table in Shanghai, but a number of the topics proposed in the etherpad required more of the team to be present for the discussion. 15:28:44 Keystone is in a similar situation with a lof of their contributors not being present at the in-person PTG, so they've been doing virtual PTG video calls. 15:28:57 I'd like to propose that we try doing the same. 15:29:59 Keystone seems to have had the best scheduling luck by doing theirs around their regular meeting time, so I'm thinking we should try to do the same. 15:31:08 I'd like to do maybe 2 hours. Hopefully we can get through the remaining topics in that amount of time. 15:31:30 Ideally for me it would be this hour + the next one, but I know that might be getting late for folks in Europe. 15:32:23 Since we don't have most of the team here today I guess we'll need to do the planning on the list, so I'll send an email about it. 15:32:31 #action bnemec to send email about virtual PTG 15:36:28 #topic Weekly Wayward Review 15:36:39 #link https://review.opendev.org/678771 15:37:13 This one is pretty simple. moguimar, can you give it a second +2 when you're done with your other meeting? 15:37:27 bnemec: sure 15:37:40 moguimar: Thanks! 15:37:47 #topic Open discussion 15:37:59 That's it for the regular agenda. 15:38:06 this and the next hour is fine for me 15:38:12 for the virtual PTG 15:38:45 Cool. Hopefully it will work for everyone else too. 15:39:09 Otherwise I'll have to do one of those massive doodle polls and I'm not super excited about that. :-) 15:41:30 Okay, that should do it for this week. 15:41:39 Thanks for joining moguimar and johnsom! 15:41:42 #endmeeting