14:00:06 <whoami-rajat> #startmeeting cinder
14:00:06 <opendevmeet> Meeting started Wed Feb  8 14:00:06 2023 UTC and is due to finish in 60 minutes.  The chair is whoami-rajat. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:06 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:06 <opendevmeet> The meeting name has been set to 'cinder'
14:00:08 <whoami-rajat> #topic roll call
14:00:11 <felipe_rodrigues> o/
14:00:14 <Roamer`_> o/
14:00:16 <jungleboyj> o/
14:00:19 <enriquetaso> hi
14:00:19 <Tony_Saad> o/
14:00:23 <simondodsley> o/
14:01:05 <kgube> o/
14:01:49 <nahimsouza[m]> o/
14:03:20 <keerthivasansuresh> o/
14:04:24 <rosmaita> Rajat is disconnected from irc, will be a minute
14:05:28 <whoami-rajat__> sorry i got disconnected, my znc bouncer is having issues
14:05:48 <whoami-rajat__> #link https://etherpad.opendev.org/p/cinder-antelope-meetings
14:06:12 <rosmaita> whoami-rajat__: did you start the meeting?
14:06:24 <whoami-rajat__> assuming the roll call is done, let's start with announcements
14:06:34 <whoami-rajat__> rosmaita, yes, it disconnected after that
14:06:50 <whoami-rajat__> or at least what i think happened
14:06:59 <rosmaita> sorry, i'm still not used to the meeting bot not being able to update the channel topic
14:07:25 <Roamer`> FWIW, yeah, the opendevmeet bot did announce that the meeting started
14:07:58 <whoami-rajat__> logs show it started https://meetings.opendev.org/irclogs/%23openstack-meeting-alt/%23openstack-meeting-alt.2023-02-08.log.html
14:08:09 <whoami-rajat__> so on to announcements
14:08:15 <whoami-rajat__> but yeah thanks for reminding me to check
14:08:23 <whoami-rajat__> #topic announcements
14:08:36 <whoami-rajat__> first, os-brick release this week (10th Feb)
14:09:03 <whoami-rajat__> #link https://review.opendev.org/c/openstack/releases/+/872778
14:09:14 <whoami-rajat__> the release patch is up but I've put a -1 to discuss some patches
14:09:29 <whoami-rajat__> we've an etherpad to track the changes we need in the release
14:09:33 <whoami-rajat__> so far 2 have been added
14:09:34 <whoami-rajat__> #link https://etherpad.opendev.org/p/os-brick-antelope-patches
14:10:25 <whoami-rajat__> but i wanted to discuss about the changes done by stephen to move to privsep
14:10:27 <whoami-rajat__> #link https://review.opendev.org/q/topic:privsep+project:openstack/os-brick+status:open
14:11:13 <whoami-rajat__> they're pretty big changes so I'm not sure if we should target them, also not all the changes are updated and some are in merge conflict
14:11:30 <whoami-rajat__> but wanted to know what the team thinks
14:12:09 <rosmaita> well, we really need to get that done, though it sucks to merge a big possibly destabilizing change right before release
14:12:32 <whoami-rajat__> yeah that's what i was worried about
14:14:26 <whoami-rajat> ok I'm back
14:14:39 <rosmaita> i guess it doesn't make any sense to have part of os-brick de-privsep'd, but part not
14:15:19 <whoami-rajat> yeah true, doesn't help us achieve the final goal (for nova to drop the rootwrap dependency)
14:15:36 <whoami-rajat> and i think stephen is also not around if someone has concerns
14:15:37 <whoami-rajat> so let's postpone it to next release
14:15:51 <whoami-rajat> but do take a look at the other changes on the etherpad
14:15:55 <whoami-rajat> #link https://etherpad.opendev.org/p/os-brick-antelope-patches
14:16:00 <rosmaita> i think that makes sense ... and we can make it a priority to do that early in bobcat
14:16:16 <whoami-rajat> +1 sounds good
14:16:51 <whoami-rajat> ok moving on to next announcement
14:16:53 <whoami-rajat> Cinder Antelope Features (Deadline: 17th Feb)
14:16:56 <whoami-rajat> which is next week
14:17:09 <whoami-rajat> #link https://releases.openstack.org/antelope/schedule.html#a-ff
14:17:20 <whoami-rajat> I've created this etherpad to track all the features we have this cycle
14:17:22 <whoami-rajat> #link https://etherpad.opendev.org/p/cinder-antelope-features
14:17:31 <whoami-rajat> I've added all the features from the review request section
14:17:45 <whoami-rajat> also we got some merged early in the cycle so that's good
14:18:00 <whoami-rajat> but a lot of them remain
14:18:57 <whoami-rajat> so requesting everyone to take a look at them to avoid last minute issues
14:20:07 <whoami-rajat> next, Testing runtime for 2023.2 (Bobcat)
14:20:15 <whoami-rajat> #link https://review.opendev.org/c/openstack/governance/+/872232
14:20:30 <whoami-rajat> there is a proposal patch for next release testing runtimes
14:20:45 <whoami-rajat> which i assume are going to be the final ones as well
14:20:53 <whoami-rajat> Ubuntu 22.04
14:20:54 <whoami-rajat> Debian 11
14:20:54 <whoami-rajat> Python 3.9 (available as default in Debian 11)
14:20:54 <whoami-rajat> Python 3.10 (available as default in Ubuntu 22.04)
14:21:48 <whoami-rajat> so we need to get py310 running in all of our gates
14:21:56 <whoami-rajat> i know cinder is running it as voting but not sure about other projects
14:22:29 <whoami-rajat> or i think it's part of template now
14:22:38 <whoami-rajat> anyway i will check that
14:22:38 <rosmaita> it is, it's required for antelope
14:22:49 <rosmaita> https://governance.openstack.org/tc/reference/runtimes/2023.1.html
14:23:02 <whoami-rajat> oh ok, then we're good
14:23:03 <whoami-rajat> thanks
14:23:10 <simondodsley> so we should also ensure all 3rd party cis are running jammy as well
14:23:36 <whoami-rajat> yes, that should be the best thing to do
14:23:41 <rosmaita> simondodsley: good point, and at least py39
14:23:48 <whoami-rajat> so basically we're removing py38 support and minimum testing is with py39
14:23:53 <whoami-rajat> as rosmaita said
14:24:34 <whoami-rajat> we need to do a compliance check at some point
14:24:53 <whoami-rajat> but I will worry about it after the feature freeze
14:25:19 <whoami-rajat> ok, last announcement
14:25:22 <whoami-rajat> Cleanup of PyPI maintainer list for OpenStack Projects
14:25:43 <whoami-rajat> rosmaita, brought this topic up last week and we had some projects that had external maintainers apart from openstackci
14:25:54 <whoami-rajat> Sean, Gorka and Walt have transferred the ownership to openstackci
14:26:01 <whoami-rajat> thanks for the quick response
14:26:04 <rosmaita> \o/
14:26:16 <whoami-rajat> Mike Perez and Ivan haven't been around lately but we can assume they are OK to make the change
14:26:30 <whoami-rajat> I've updated the etherpad so we should be good there
14:26:33 <whoami-rajat> #link https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup#L36
14:27:21 <whoami-rajat> that's all i had for today, anyone got anything for announcements?
14:28:37 <whoami-rajat> guess not
14:28:41 <whoami-rajat> let's move to topics then
14:29:00 <whoami-rajat> #topic cinder A/A support. How to get checkmark here https://docs.openstack.org/cinder/zed/reference/support-matrix.html
14:29:21 <whoami-rajat> happystacker doesn't seem to be around
14:29:29 <whoami-rajat> but I've replied to his query on the etherpad
14:29:43 <Tony_Saad> im filling in for happystacker
14:29:43 <whoami-rajat> assuming that's what he was querying about
14:29:51 <whoami-rajat> oh ok
14:29:55 <whoami-rajat> sure Tony_Saad go ahead
14:29:57 <Tony_Saad> he cannot connect
14:31:40 <whoami-rajat> Tony_Saad, sure you can continue
14:32:12 <Tony_Saad> just looking for some information about about A/A support
14:32:42 <Tony_Saad> Guidance for installation and configuration of HA environment
14:33:49 <Tony_Saad> How to get checkmark here: https://docs.openstack.org/cinder/zed/reference/support-matrix.html ?
14:34:37 <whoami-rajat> Tony_Saad, I've added an answer to the etherpad, you can check if that's what you were looking for https://etherpad.opendev.org/p/cinder-antelope-meetings#L118
14:35:35 <simondodsley> Pure added this support some time ago - this is the patch we applied. Might help. https://review.opendev.org/c/openstack/cinder/+/779781
14:35:53 <Roamer`> mm, could it be that Tony_Saad is asking more like how to set up such an environment so that they can make sure their driver supports this?
14:36:27 <jbernard> Tony_Saad: our in-tree doc is here: https://opendev.org/openstack/cinder/src/branch/master/doc/source/contributor/high_availability.rst
14:37:19 <whoami-rajat> I couldn't find any document regarding A/A deployment but geguileo did most of the work so he might know better
14:37:53 <simondodsley> there isn
14:37:54 <geguileo> whoami-rajat: I don't think there's any A/A deployment configuration
14:37:57 <geguileo> docs
14:38:29 <simondodsley> there isn't any tempest test for this. We have to take it on your word that you tested your driver in an A/A configuration
14:38:33 <geguileo> it's to not configure host/backend_host, configure cluster, deploy a DLM and configure it in cinder.conf
14:38:37 <whoami-rajat> ok so I'm not that bad at google search
14:38:58 <Tony_Saad> happystacker question is how to get the checkmark?
14:39:19 <simondodsley> see the pure patch I just listed
14:39:28 <geguileo> Tony_Saad: We are going with an honor system
14:39:37 <geguileo> Vendor says it works, we believe them
14:39:56 <eharney> be aware that you have to also audit the design of your driver and know that it will work correctly in an A/A environment
14:40:56 <Tony_Saad> Thanks I will relay the information to happystacker
14:41:16 <geguileo> Tony_Saad: so basically submit patch to set the flag, and answer the questions from the reviewers
14:41:34 <geguileo> who will ask pertinent questions to confirm that things have been tested/audited
14:43:03 <Tony_Saad> Thank you!
14:43:29 <whoami-rajat> anything else on this topic Tony_Saad ?
14:44:55 <Tony_Saad> From me no. From Happystack maybe. but that will have to wait for next meeting
14:45:04 <Tony_Saad> Thanks!
14:45:17 <abdi> Whoami-rajat: Along the same lines.  From a process pov.  When are newly supported drivers added to the support matrix: https://docs.openstack.org/cinder/zed/reference/support-matrix.html
14:45:24 <whoami-rajat> great
14:45:48 <whoami-rajat> abdi, they are added with the driver patch
14:46:31 <abdi> Thank you.  So no action on my end?
14:47:08 <simondodsley> your patch will need to update the matrix
14:47:13 <Roamer`> abdi, if you are the one submitting the patch that adds the new driver, you should make sure that patch includes a change to the support matrix
14:47:59 <whoami-rajat> abdi, i think you proposed the HPE XP driver right?
14:48:15 <abdi> Yes
14:48:24 <whoami-rajat> i see the changes done here https://review.opendev.org/c/openstack/cinder/+/815582/19/doc/source/reference/support-matrix.ini
14:48:32 <whoami-rajat> and they're reflected in the support matrix so looks good
14:49:07 <abdi> Wanted to make sure nothing else was needed from us.
14:49:18 <abdi> Thank you.
14:49:36 <whoami-rajat> as of now, I don't see anything apart from maintaining the CIs
14:49:38 <whoami-rajat> let me open the open discussion
14:49:41 <whoami-rajat> #topic open discussion
14:50:03 <zaitcev> I have review beg, or swap.
14:50:06 <eharney> i have five patches pending that are requirements changes, i think we need to land those soon?
14:50:15 <zaitcev> https://review.opendev.org/c/openstack/cinder/+/852654
14:50:49 <Sathya> Hi, Cinder retype - To allow volume migration with additional extra spec to enter driver specific code
14:51:01 <Sathya> i have submited a patch
14:51:07 <senrique> i have a bug that i would like to highlight
14:51:09 <whoami-rajat> eharney, I mentioned the os-brick ones earlier today, should be able to land those soon
14:51:31 <whoami-rajat> zaitcev, you can add it to the review request section https://etherpad.opendev.org/p/cinder-antelope-meetings#L120
14:51:36 <Sathya> https://review.opendev.org/c/openstack/cinder/+/869999 Reviewers can you please have a look at this
14:51:57 <rosmaita> whoami-rajat:  would be good to do a quick review of the mins listed in os-brick requirements.txt before release
14:52:22 <whoami-rajat> rosmaita, good idea, will do that
14:52:42 <Tony_Saad> Dell has a handful of review requests. most notably https://review.opendev.org/c/openstack/cinder/+/844563
14:52:44 <Roamer`> um, yeah, while on the subject of reviews... turns out I did something a bit silly concerning the series of bugfixes for the StorPool driver: I somehow forgot the obvious fact that patches listed for review from one meeting are not automatically carried over to the next one. So... I added the StorPool patches for review for the 2023-01-25 meeting (and one of them was even approved and
14:52:50 <Roamer`> merged, thanks!), but then I did not add them for last week's meeting or for this one. So... should I add them now?...
14:53:09 <senrique> Regarding the vmdk vulnerability.. there's a new bug https://bugs.launchpad.net/cinder/+bug/2004565
14:53:39 <senrique> i think it's not critical, but i'm not sure how target it
14:54:25 * enriquetaso needs to do more reviews
14:55:23 <rosmaita> enriquetaso: it's not exploitable, so it's a hardening opportunity ... patch is pretty small, hopefully can get reviewed soon
14:55:49 <eharney> enriquetaso: rosmaita: please add a comment to the bug pointing to the patch
14:56:09 <rosmaita> will do
14:56:12 <whoami-rajat> cinder team ^ please take a look at the review request section from time to time
14:56:29 <enriquetaso> oh true, we talked about it last week rosmaita
14:56:31 <enriquetaso> my bad
14:56:43 <jbernard> zaitcev: i will look at your sparse patch today
14:57:12 <whoami-rajat> zaitcev, since it's a feature, I've added it to the list of features here https://etherpad.opendev.org/p/cinder-antelope-features#L32
14:57:24 <whoami-rajat> but others please add your features if you want to get them in for Antelope release
14:57:35 <whoami-rajat> s/others/everyone
14:57:41 <zaitcev> Oh. I need a blueprint, then?
14:57:51 <rosmaita> eharney: https://review.opendev.org/c/openstack/cinder/+/871976 (added it to the bug)
14:58:07 <whoami-rajat> zaitcev, did we have a spec for it?
14:59:12 <zaitcev> whoami-rajat: Restore-to-sparse started as a Red Hat bug for me, https://bugzilla.redhat.com/show_bug.cgi?id=1855709
14:59:59 <whoami-rajat> ok, i think this needs some discussion then
15:00:14 <zaitcev> whoami-rajat: So I didn't think to file a blueprint. I'm not used to them, Swift stopped the blueprints. I can do that if the community process requires it.
15:00:16 <whoami-rajat> usually we do a BP and spec first then implement the feature
15:00:44 <whoami-rajat> in some cases, we skip the spec if it's straightforward
15:00:59 <whoami-rajat> but let's discuss about it
15:01:03 <whoami-rajat> we're out of time
15:01:07 <whoami-rajat> thanks everyone for joining
15:01:10 <whoami-rajat> #endmeeting