14:00:26 <rosmaita> #startmeeting cinder
14:00:26 <opendevmeet> Meeting started Wed Dec  8 14:00:26 2021 UTC and is due to finish in 60 minutes.  The chair is rosmaita. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:26 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:26 <opendevmeet> The meeting name has been set to 'cinder'
14:00:28 <e0ne> hi
14:00:35 <rosmaita> #topic roll call
14:00:39 <simondodsley> o/
14:00:52 <jungleboyj> o/
14:00:55 <jungleboyj> kind of.
14:01:01 <enriquetaso_> hi
14:01:03 <rosmaita> probably a light turnout today
14:01:13 <rosmaita> it is a holiday in a surprising number of countries
14:01:22 <rosmaita> well, surprising if you are an ugly american like me
14:01:22 <simondodsley> slackers...
14:01:51 <rosmaita> enriquetaso_: i thought today is a holiday in Argentina?
14:02:05 <TusharTgite> hi all
14:02:08 <eharney> hi
14:02:16 <enriquetaso_> it is
14:02:19 <enriquetaso_> :P
14:02:25 <rosmaita> enriquetaso_: bonus points for you!
14:02:38 <simondodsley> https://www.holidayscalendar.com/
14:03:03 <rosmaita> ok, i think we can get started
14:03:16 <enriquetaso_> argentina it's not in the list simondodsley :P
14:03:22 <enriquetaso_> not sure why
14:03:23 <rosmaita> kind of a light agenda, mostly announcements, but that will leave plenty of time for open discussion
14:03:32 <rosmaita> #topic announcements
14:03:50 <rosmaita> first, you probably noticed that we are not holding this meeting in video right now
14:04:04 <rosmaita> we'll have the followup session for the midcycle tomorrow
14:04:14 <rosmaita> details here:
14:04:17 <rosmaita> #link http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026196.html
14:04:29 <rosmaita> and, there is the etherpad also
14:04:39 <rosmaita> #link https://etherpad.opendev.org/p/cinder-yoga-midcycles
14:04:51 <rosmaita> time will be 1400-1430 UTC
14:05:21 <rosmaita> topic is the new quotas work, and if there's time, also the community goal ("secure and consistent RBAC")
14:05:29 <rosmaita> it will be recorded if you can't make it
14:05:53 <rosmaita> next, early Yoga releases have happened
14:06:02 <rosmaita> os-brick: 5.1.0
14:06:08 <rosmaita> python-cinderclient: 8.2.0
14:06:30 <rosmaita> i think neither really needed a release, but the release team likes early releases in the cycle to shake out problems
14:06:52 <rosmaita> next, our cycle-trailing deliverable must be released next week
14:06:55 <rosmaita> that's cinderlib
14:07:13 <rosmaita> there is one patch that has to merge immediately, so cores, please look it over:
14:07:22 <rosmaita> #link https://review.opendev.org/c/openstack/cinderlib/+/820391
14:07:28 <rosmaita> it's a simple patch
14:08:00 <rosmaita> just noticed that i didn't put a link in the commit message to the docs explaining why we have to do this
14:08:10 <rosmaita> so i will put it here (soon as i find it)
14:08:35 <rosmaita> #link https://docs.openstack.org/cinderlib/latest/contributor/contributing.html#cinderlib-releases
14:09:03 <rosmaita> looking at the open patches, i don't see anything else that needs to get in to the xena release
14:09:16 <rosmaita> #link https://review.opendev.org/q/project:openstack/cinderlib+branch:master+status:open
14:09:59 <rosmaita> so https://review.opendev.org/c/openstack/cinderlib/+/820391 doesn't get forgotten, can I have 2 cores commit to looking at it today?
14:10:49 <enriquetaso_> 820391 has +2 already?
14:11:13 <rosmaita> ok, that was fast
14:11:18 <rosmaita> thanks e0ne and eharney
14:11:29 <e0ne> rosmaita: np
14:11:38 <enriquetaso_> just needs the workflow vote
14:11:42 <rosmaita> i think there was a race condition there
14:12:01 <rosmaita> thanks!
14:12:20 <rosmaita> the release team already has a patch up for cinderlib release, so we're all set there
14:12:42 <rosmaita> next reminder:
14:12:48 <rosmaita> spec freeze is next week
14:12:57 <rosmaita> #link https://releases.openstack.org/yoga/schedule.html#y-cinder-spec-freeze
14:13:29 <rosmaita> i tried to get comments on all the proposed specs, but there are a few i still have drafts on
14:13:32 <rosmaita> #link https://review.opendev.org/q/project:openstack/cinderlib+branch:master+status:open
14:13:46 <rosmaita> i'll get those done today, and then start re-reviewing
14:14:19 <rosmaita> also next week is the monthly Festival of XS Reviews
14:14:29 <rosmaita> 1400-1600 UTC on Friday
14:14:47 <rosmaita> next week is a pretty busy week!
14:14:57 <rosmaita> something a bit further out is the new driver merge deadline
14:15:02 <rosmaita> which is 21 January
14:15:09 <rosmaita> #link https://releases.openstack.org/yoga/schedule.html#cinder-new-driver-merge-deadline
14:15:28 <rosmaita> i know people are itching for reviews on their new driver patches
14:15:45 <rosmaita> but specs reviews are the priority over the next week
14:15:48 <rosmaita> in the meantime
14:16:01 <rosmaita> you can look through our handy new driver reviewer checklist
14:16:11 <rosmaita> and make sure you have all those things addressed
14:16:21 <rosmaita> #link https://docs.openstack.org/cinder/latest/contributor/new_driver_checklist.html
14:16:45 <rosmaita> and, of course, make sure your third party CI is working
14:16:56 <rosmaita> and displaying results in an easily consumable format
14:17:23 <rosmaita> that is, do not require people to download and decompress an archive file in order to see the logs etc
14:17:39 <rosmaita> ok, that's all for announcements
14:17:55 <rosmaita> #topic TC collection of service pain points
14:18:33 <rosmaita> the TC has been collecting operator feedback with the idea that there could be a service-specific community goal to fix a pain point
14:18:48 <rosmaita> the info has been collected here:
14:18:57 <rosmaita> #link https://etherpad.opendev.org/p/pain-point-elimination
14:19:14 <rosmaita> there is a video meeting to discuss this today, right after our meeting
14:19:23 <rosmaita> #link http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026207.html
14:19:40 <rosmaita> i will attend, though i'm not exactly sure what it's about
14:19:50 <rosmaita> anyway, there are 2 items currently listed for cinder
14:20:01 <rosmaita> 1. volume backup rotation
14:20:12 <rosmaita> 2. cinder backup fails due to user token expiration with swift backend
14:20:39 <jungleboyj> rosmaita: What it is about will hopefully be clearer after the discussion.
14:20:51 <rosmaita> jungleboyj: hope so!
14:21:20 <jungleboyj> Goal was to look at some of the higher level problems that our users have and if something can be done community wide to help address those items.
14:21:44 <rosmaita> ok, that's good from a cinder point of view then, because these are both minor issues
14:21:56 <jungleboyj> ++
14:23:48 <rosmaita> the first one looks like a minor enhancement, unless the idea is that cinder should store the number of backups, then it would require some thought about whether it's per-volume or per-project or what
14:24:28 <rosmaita> the second one has an alternative fix (if it is in fact a problem)
14:25:14 <rosmaita> short story is, the status of keystone "trusts" is kind of suspect, and the advice i got from the keystone team is don't use them in new code
14:26:09 <rosmaita> #topic openstackclient feature parity
14:26:17 <rosmaita> this one is a surprise
14:26:29 <rosmaita> #link http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026192.html
14:26:49 <rosmaita> the claim is made there that openstack SDK fully supports cinder
14:27:00 <jungleboyj> Whaaaaat!?!
14:27:03 <rosmaita> yeah
14:27:14 <rosmaita> i haven't had time to look closely at that
14:27:22 <jungleboyj> Well, ship it.
14:27:26 <jungleboyj> ;-)
14:27:57 <eharney> hmm
14:28:47 <rosmaita> the idea is that if SDK fully supports Block Storage API v3, then since the osc uses SDK, it's just a small matter of time before the osc will fully support it too
14:29:11 <jungleboyj> Well, that would be awesome if true.
14:30:15 <rosmaita> #link https://opendev.org/openstack/openstacksdk/src/branch/master/openstack/block_storage
14:30:39 <e0ne> jungleboyj: +1
14:31:22 <rosmaita> looking at the history makes me kind of skeptical
14:31:44 <rosmaita> #link https://opendev.org/openstack/openstacksdk/commits/branch/master/openstack/block_storage
14:33:00 <rosmaita> if you look at the email i linked above, this came up because a pain point is "why can't i use the openstackclient for everything?"
14:34:40 <rosmaita> ok, that's it from me ... let's have open discussion
14:34:46 <rosmaita> #topic open discussion
14:36:20 <rosmaita> ... or not
14:38:10 <rosmaita> enriquetaso_: thank you for your weekly bug report:
14:38:13 <rosmaita> #link http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026225.html
14:38:14 <eharney> i put up a couple of patches a bit ago that just remove dead code, maybe not a tough review if anyone wants to take a look: https://review.opendev.org/c/openstack/cinder/+/800703
14:38:47 <enriquetaso_> I have only one question regarding the bug report
14:38:59 <rosmaita> sure
14:39:03 <enriquetaso_> maybe i can do it in the open discussion and skip the bug meeting
14:39:10 <rosmaita> sounds good to me!
14:39:24 <enriquetaso_> bug_1  cinder schedules backups on disabled backup services
14:39:24 <enriquetaso_> #link https://bugs.launchpad.net/cinder/+bug/1952804
14:39:35 <enriquetaso_> Summary: Set up multiple cinder-backup nodes then mark one of them as disabled via 'openstack volume service set --disable'. Create some backups and those backups get sent to the disabled node. The reporter points out that the real issue here is the lack of any kind of feedback during the backup; ideally there would be some way to detect stuck jobs and retry them.
14:39:44 <enriquetaso_> Maybe this is too obvious but I'm not sure what to reply to the reporter here.
14:39:45 <enriquetaso_> The creation of the backup depends on the backend you're using, if it takes too long to create the backup there's not much we can do excerpts for a retry.  However, cinder shouldn't use the disable nodes for backups.
14:45:38 <enriquetaso_> ..guess I'll just mark the bug as medium importance and we can fix it :P
14:46:38 <eharney> it will take some investigating to figure out what to do with this, there may be some room to improve usability w/ async error messages
14:47:47 <rosmaita> yeah, i think a related issue is 'disabled' temporarily (fine for jobs to get picked up on restart) vs 'disabled permanently', i.e., the node is never coming back
14:50:20 <enriquetaso_> sure
14:50:35 <enriquetaso_> OK, that's all I have
14:50:45 <enriquetaso_> 14 bugs reported in two weeks!!
14:50:45 <enriquetaso_> The good side it's that most of them have fixes proposed on master but please take a look at the full list.
14:51:07 <rosmaita> thanks enriquetaso_ !
14:51:38 <rosmaita> anyone else have anything to discuss?
14:52:15 <rosmaita> ok, as a reminder, all cinder-cores need to be looking at specs over the next week
14:52:46 <rosmaita> i guess that's all for today
14:52:53 <rosmaita> thanks everyone, and have a good rest of the week
14:53:04 <rosmaita> don't forget the midcycle followup session tomorrow at 1400 UTC
14:54:52 <rosmaita> all right, we can close the meeting
14:54:54 <rosmaita> #endmeeting