14:00:19 #startmeeting cinder 14:00:19 Meeting started Wed Nov 17 14:00:19 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:19 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:19 The meeting name has been set to 'cinder' 14:00:33 #topic roll call 14:00:40 ahoy, mateys! 14:00:40 hi 14:00:43 hi 14:00:45 hi 14:01:05 o/ 14:01:10 o/ 14:01:41 hi! o/ 14:01:55 good turnout! 14:02:03 #link https://etherpad.opendev.org/p/cinder-yoga-meetings 14:02:08 #topic announcements 14:02:23 well, the cycle is moving right along ... this week is Milestone 1 for yoga 14:02:26 hi 14:02:33 hi 14:02:38 luckily, we aren't required to do an M-1 release any more 14:02:59 but, keep in mind that we are on third of the way through the development cycle 14:03:08 ok, some upcoming events 14:03:24 the OpenInfra Live: Keynotes are today and tomorrow, 1500-1700 UTC 14:03:37 if you're curious, the schedule is here: 14:03:45 #link https://openinfra.dev/live/keynotes?utm_id=Keynotes#schedule 14:03:47 starting right after this meeting concludes, in fact 14:03:52 exactly 14:04:07 you need to register to get a link to the video session, and it is free 14:04:12 Hi 14:04:15 #link https://openinfralivekeynotes.eventbrite.com/ 14:04:24 next item 14:04:33 our monthly Festival of XS Reviews happens on Friday this week (1400-1600 UTC) 14:04:45 full info here: http://eavesdrop.openstack.org/#Cinder_Festival_of_XS_Reviews 14:05:09 i will be on limited bandwidth and may not be in meetpad for that one, but i will be in irc and watching the etherpad 14:05:26 next 14:05:36 the stable/ussuri branch is now in Extended Maintenance mode 14:05:47 thanks to whoami-rajat for getting the final ussuri releases out the door in time 14:06:21 ++ 14:06:32 this means no more ussuri releases, though we may merge backports of bugfixes as a courtesy to people still using that branch 14:06:46 another announcement 14:07:04 the openstack-wide stable core team process has changed 14:07:07 details here: 14:07:16 #link http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025741.html 14:07:53 it doesn't really affect us, except in the sense that the openstack stable-core team can't -2 our releases if inappropriate stuff slips in 14:08:08 so we need to continue to exercise due diligence 14:08:26 ok, last announcement: 14:08:34 cinder yoga midcycle coming up in 2 weeks on Wednesday 1 December 2021 14:08:42 #link https://etherpad.opendev.org/p/cinder-yoga-midcycles 14:08:48 please add topics to ^^ 14:09:00 if you are working on a spec, it would be a good place to get some feedback 14:09:29 or if you have an idea for a feature, or a bugfix that requires a new config option or something, also a good place to get feedback 14:09:50 Are we thinking the usual time? 14:10:14 was just going to ask that ... actually, first, is that day good (or at least not awful) for everyone? 14:10:24 (somehow I seem to remember someone saying there might be a conflict) 14:11:07 The day should be fine for me. 14:11:29 ok, hearing no negative responses, we will stick with 1 december 14:11:37 OK, next question is the time 14:11:42 I'd like to do our usual thing where we use 1 hour from the weekly meeting time 14:11:49 (since everyone has that blocked off already) 14:11:55 ++ 14:11:56 and add an hour either before or after the meeting 14:12:04 let's try to pick a time right now 14:12:15 options are: 14:12:15 A 1300-1500 UTC 14:12:15 B 1400-1600 UTC 14:12:15 C either one of the above 14:12:15 D need more options 14:12:27 #startvote time for the R-17 (1 December) midcycle? A, B, C, D 14:12:27 Begin voting on: time for the R-17 (1 December) midcycle? Valid vote options are A, B, C, D. 14:12:28 Vote using '#vote OPTION'. Only your last vote counts. 14:12:43 (everybody clear about how this works?) 14:12:58 #vote B 14:13:02 #vote C 14:13:04 #vote B 14:13:07 #vote B 14:13:29 #vote C 14:13:38 #vote B 14:14:57 one more minute to vote! 14:15:01 #vote C 14:15:20 #vote C 14:16:09 ok, let's see what the results are 14:16:14 #endvote 14:16:14 Voted on "time for the R-17 (1 December) midcycle?" Results are 14:16:14 B (4): jungleboyj, walshh_, rosmaita, ssuerd 14:16:14 C (4): lucasmoliveira059, fabiooliveira, geguileo, eharney 14:16:33 OK, looks like 1400-1600 UTC it is 14:17:04 by the way, if you are constrained to 1400-1500, put a note on the midcycle etherpad when you add your topic 14:17:15 and we can make sure we discuss it during that time frame 14:17:29 ok, thanks everyone ... on with the meeting 14:17:43 #topic Ceph: add option to keep only last n snapshots per backup 14:17:52 #link https://review.opendev.org/c/openstack/cinder/+/810457 14:17:57 jhartkopf: that's you 14:18:32 yes 14:18:58 so basically we'd like be able to only keep a specific number of backup snapshots of a volume 14:19:25 for the RBD driver 14:19:47 well, ceph backup driver, i mean 14:19:53 so this patch adds a new config option to configure how many snapshots to keep 14:20:02 exactly, for the Ceph driver 14:20:49 seems like a good idea, but i asked jhartkopf to put it on the agenda because it requires a new configuration option 14:21:03 I disagree, I don't like this 14:21:21 please elaborate 14:21:24 that's my first impression, looking more on the patch 14:21:37 rosmaita: the reason for having backup snapshots is to be able to do incremental backups 14:22:06 if we remove the snapshot without removing the related backup then we can reach a point were we can't do an incremental backup and end up doing a full backup 14:23:01 that is a good point 14:23:23 literally what the referenced bug was fixing 14:23:27 https://bugs.launchpad.net/cinder/+bug/1703011 14:24:26 as far as I understand, we still can do incremental backups if both snapshots (the same ones) exist on both sides 14:25:10 but if you remove it due to the new config option then we can't 14:25:39 we have a 1-to-1 relationship between cinder backups and RBD snapshots 14:25:43 that's quite a commit message on https://review.openstack.org/486678 14:25:45 that's how we can do incremental 14:26:01 if we break that 1-to-1 relationship we break incremental backups in some cases 14:26:54 but if we only remove older snapshots, we keep the more recent ones which can then be used to do incremental backups 14:27:21 let me show you the issue with an exageration 14:27:27 set the new conf option to 2 14:27:32 do 4 incremental backups 14:27:41 the oldest 2 snapshots are removed 14:27:45 now you delete the last 2 backups 14:27:50 now you can't do incremental backups 14:28:06 because the new one will be a full backup 14:28:20 (the removal of the snapshots are done by the new feature) 14:30:15 so it looks like if the motivation for this is to save space on the backend, this approach is counterproductive 14:30:25 yes that seems like a situation to consider 14:30:39 and that was the situation that the related bug was fixing 14:31:07 jhartkopf: why don't you take some time to think about this, and we could discuss again at the midcycle if you have some new ideas 14:31:18 jhartkopf: what was the original reason for the feature? 14:31:28 performance? save space? 14:32:06 mainly to save disk space because keeping all snapshots can quickly take up much space 14:32:33 jhartkopf: I assume you don't want to delete the backups that match those snapshots 14:34:05 yes we'd like to keep the backups 14:35:24 I don't like the idea of removing the source snapshots... Though I understand your issue 14:36:24 ok, let's think about this some more and pick up the discussion, maybe at the midcycle, and work through the issues 14:36:34 thanks geguileo and jhartkopf 14:36:50 #topic Implications of new Glance spec-lite on Cinder image encryption spec rewrite 14:37:02 i'll make this quick, it's a national holiday for the secustack folks, but during the image encryption pop-up team meeting on monday, Luzi mentioned wanting to inquire in the cinder meeting whether anyone's had time to mull over the implications of the glance "spec-lite" on the former cinder spec, and whether a new spec would be required for the cinder side of things or if changes 14:37:02 fungi: you have the floor 14:37:04 might be needed to the old cinder spec for it 14:37:20 looks like jhartkopf had some feedback on the agenda etherpad already 14:37:36 actually, that was me 14:37:44 ahh, okay 14:37:56 so the change in Glance is to not wait for the Barbican Secret Consumers API to be implemented 14:38:03 right 14:38:04 but go ahead without it, and add it later 14:38:13 that's my understanding, yes 14:38:26 i believe that cinder wasn't in the workflow for using the Secret Consumers API 14:38:31 so that doesn't affect us 14:39:13 i think there may be some issues that are going to come up with how to handle the optimizations when glance is using the cinder glance_store 14:39:23 so the old cinder spec is still applicable, or are you saying there's no need to any work in cinder to support it? 14:39:24 and also the cinder image cache 14:39:47 er, no need to do any 14:40:16 i guess what i'm saying is that some stuff will have to be worked out during the implementation of the cinder side 14:40:35 but i don't think we need a new spec for that 14:40:51 so doesn't rise to the level of complexity to require a spec. got it 14:40:54 thanks! 14:41:14 yeah, i am in favor of the glance spec-lite because i think it will move the effort along 14:41:18 i mainly wanted to make sure the folks working on this weren't blocked for a week waiting for another cinder meeting 14:41:29 much appreciated 14:41:36 once there is end-to-end testing of the feature, i imagine a bunch of issues will areise 14:41:39 *arise 14:41:45 sure, as ever 14:41:52 "that's software" 14:41:57 yes, so on the cinder side, the first priority is to get the gpg stuff into os-brick 14:42:51 #link https://review.opendev.org/709432 14:43:35 yeah, looks like it needs rebasing at the very least 14:43:36 thanks fungi ... anyone else have comments or concerns about this? 14:44:28 okay, cool. that answers the questions i think. thanks again! 14:44:29 fungi: yes, if Luzi could get it out of merge conflict, that would be a good motivator for reviewers 14:44:44 agreed 14:45:28 ok, thanks ... let's move on 14:45:35 #topic mypy patch of the week 14:46:03 last week's patch was this one 14:46:12 #link https://review.opendev.org/c/openstack/cinder/+/733622 14:46:32 we're still working on it ... it's very close, i think 14:46:47 so that will remain the mypy patch of the week for this week 14:47:08 yep, i'll update that again shortly 14:47:16 and we can carry over the same reviewers 14:47:39 also, thanks to walshh_, who did a thorough review 14:48:06 you are welcome 14:49:07 #topic volume driver API function of the week 14:49:16 i think we are stalled on this one 14:49:37 still need a solidfire dev to leave an OK on https://review.opendev.org/c/openstack/cinder/+/814898 14:50:32 and that blocks the next patch, that needs a second +2 14:50:40 #link https://review.opendev.org/c/openstack/cinder/+/815659 14:51:47 i had a nit on the next patch, but iirc it's a sphinx formatting thing, not content 14:51:56 #link https://review.opendev.org/c/openstack/cinder/+/815660/3 14:52:06 so don't let that stop you from looking at it 14:52:47 so it looks like we remain the same for volume driver API function of the week 14:53:04 rosmaita: I'll update the patches and start working on a new patch 14:53:22 geguileo: thanks! 14:53:24 I've been busy on the new quota stuff, which has turned to be a bit more complex than I had anticipated 14:53:31 (but making progress) 14:53:44 that is understandable! 14:54:10 #topic open discussion 14:54:10 > still need a solidfire dev to leave an OK on https://review.opendev.org/c/openstack/cinder/+/814898 14:54:10 i'll take a look :D 14:54:11 I should have the spec and patches for the midcycle 14:54:17 fabiooliveira: thanks! 14:54:27 fabiooliveira: thank you 14:55:58 I just looked at the calendar, next week is the last meeting of the month, so will be held in video 14:56:16 but, thursday and friday next week are holidays in some parts of the world 14:56:40 just wondering if we will have a critical mass of attendance for wednesday's meeting? 14:57:30 anyone who will not be attending? 14:58:15 ok, sounds like everyone will be around ... great! 14:58:31 don't forget the Festival of XS Reviews on Friday this week 14:59:40 it has gotten awfully quiet in here ... thanks for attending, and have a good rest of the day 14:59:44 see you on friday! 14:59:59 #endmeeting