Wednesday, 2023-02-08

*** dasm|off is now known as dasm|rover13:51
whoami-rajat#startmeeting cinder14:00
opendevmeetMeeting 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
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
opendevmeetThe meeting name has been set to 'cinder'14:00
whoami-rajat#topic roll call14:00
felipe_rodrigueso/14:00
Roamer`_o/14:00
jungleboyjo/14:00
*** Roamer`_ is now known as Roamer`14:00
enriquetasohi14:00
Tony_Saado/14:00
simondodsleyo/14:00
kgubeo/14:01
nahimsouza[m]o/14:01
keerthivasansuresho/14:03
rosmaitaRajat is disconnected from irc, will be a minute14:04
whoami-rajat__sorry i got disconnected, my znc bouncer is having issues14:05
whoami-rajat__#link https://etherpad.opendev.org/p/cinder-antelope-meetings14:05
rosmaitawhoami-rajat__: did you start the meeting?14:06
whoami-rajat__assuming the roll call is done, let's start with announcements14:06
whoami-rajat__rosmaita, yes, it disconnected after that14:06
whoami-rajat__or at least what i think happened14:06
rosmaitasorry, i'm still not used to the meeting bot not being able to update the channel topic14:06
Roamer`FWIW, yeah, the opendevmeet bot did announce that the meeting started14:07
whoami-rajat__logs show it started https://meetings.opendev.org/irclogs/%23openstack-meeting-alt/%23openstack-meeting-alt.2023-02-08.log.html14:07
whoami-rajat__so on to announcements14:08
whoami-rajat__but yeah thanks for reminding me to check14:08
whoami-rajat__#topic announcements14:08
whoami-rajat__first, os-brick release this week (10th Feb)14:08
whoami-rajat__#link https://review.opendev.org/c/openstack/releases/+/87277814:09
whoami-rajat__the release patch is up but I've put a -1 to discuss some patches14:09
whoami-rajat__we've an etherpad to track the changes we need in the release14:09
whoami-rajat__so far 2 have been added14:09
whoami-rajat__#link https://etherpad.opendev.org/p/os-brick-antelope-patches14:09
whoami-rajat__but i wanted to discuss about the changes done by stephen to move to privsep14:10
whoami-rajat__#link https://review.opendev.org/q/topic:privsep+project:openstack/os-brick+status:open14:10
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 conflict14:11
whoami-rajat__but wanted to know what the team thinks14:11
rosmaitawell, we really need to get that done, though it sucks to merge a big possibly destabilizing change right before release14:12
whoami-rajat__yeah that's what i was worried about14:12
whoami-rajatok I'm back14:14
rosmaitai guess it doesn't make any sense to have part of os-brick de-privsep'd, but part not14:14
whoami-rajatyeah true, doesn't help us achieve the final goal (for nova to drop the rootwrap dependency)14:15
whoami-rajatand i think stephen is also not around if someone has concerns14:15
whoami-rajatso let's postpone it to next release14:15
whoami-rajatbut do take a look at the other changes on the etherpad14:15
whoami-rajat#link https://etherpad.opendev.org/p/os-brick-antelope-patches14:15
rosmaitai think that makes sense ... and we can make it a priority to do that early in bobcat14:16
whoami-rajat+1 sounds good14:16
whoami-rajatok moving on to next announcement14:16
whoami-rajatCinder Antelope Features (Deadline: 17th Feb)14:16
whoami-rajatwhich is next week14:16
whoami-rajat#link https://releases.openstack.org/antelope/schedule.html#a-ff14:17
whoami-rajatI've created this etherpad to track all the features we have this cycle14:17
whoami-rajat#link https://etherpad.opendev.org/p/cinder-antelope-features14:17
whoami-rajatI've added all the features from the review request section14:17
whoami-rajatalso we got some merged early in the cycle so that's good14:17
whoami-rajatbut a lot of them remain14:18
whoami-rajatso requesting everyone to take a look at them to avoid last minute issues14:18
*** tosky_ is now known as tosky14:19
whoami-rajatnext, Testing runtime for 2023.2 (Bobcat)14:20
whoami-rajat#link https://review.opendev.org/c/openstack/governance/+/87223214:20
whoami-rajatthere is a proposal patch for next release testing runtimes14:20
whoami-rajatwhich i assume are going to be the final ones as well14:20
whoami-rajatUbuntu 22.0414:20
whoami-rajatDebian 1114:20
whoami-rajatPython 3.9 (available as default in Debian 11)14:20
whoami-rajatPython 3.10 (available as default in Ubuntu 22.04)14:20
whoami-rajatso we need to get py310 running in all of our gates14:21
whoami-rajati know cinder is running it as voting but not sure about other projects14:21
whoami-rajator i think it's part of template now14:22
whoami-rajatanyway i will check that14:22
rosmaitait is, it's required for antelope14:22
rosmaitahttps://governance.openstack.org/tc/reference/runtimes/2023.1.html14:22
whoami-rajatoh ok, then we're good14:23
whoami-rajatthanks14:23
simondodsleyso we should also ensure all 3rd party cis are running jammy as well14:23
whoami-rajatyes, that should be the best thing to do14:23
rosmaitasimondodsley: good point, and at least py3914:23
whoami-rajatso basically we're removing py38 support and minimum testing is with py3914:23
whoami-rajatas rosmaita said14:23
whoami-rajatwe need to do a compliance check at some point14:24
whoami-rajatbut I will worry about it after the feature freeze14:24
whoami-rajatok, last announcement14:25
whoami-rajatCleanup of PyPI maintainer list for OpenStack Projects14:25
whoami-rajatrosmaita, brought this topic up last week and we had some projects that had external maintainers apart from openstackci14:25
whoami-rajatSean, Gorka and Walt have transferred the ownership to openstackci14:25
whoami-rajatthanks for the quick response14:26
rosmaita\o/14:26
whoami-rajatMike Perez and Ivan haven't been around lately but we can assume they are OK to make the change14:26
whoami-rajatI've updated the etherpad so we should be good there14:26
whoami-rajat#link https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup#L3614:26
whoami-rajatthat's all i had for today, anyone got anything for announcements?14:27
whoami-rajatguess not14:28
whoami-rajatlet's move to topics then14:28
whoami-rajat#topic cinder A/A support. How to get checkmark here https://docs.openstack.org/cinder/zed/reference/support-matrix.html 14:29
whoami-rajathappystacker doesn't seem to be around14:29
whoami-rajatbut I've replied to his query on the etherpad14:29
Tony_Saadim filling in for happystacker14:29
whoami-rajatassuming that's what he was querying about14:29
whoami-rajatoh ok14:29
whoami-rajatsure Tony_Saad go ahead14:29
Tony_Saadhe cannot connect 14:29
whoami-rajatTony_Saad, sure you can continue14:31
Tony_Saadjust looking for some information about about A/A support 14:32
Tony_SaadGuidance for installation and configuration of HA environment14:32
Tony_SaadHow to get checkmark here: https://docs.openstack.org/cinder/zed/reference/support-matrix.html ?14:33
whoami-rajatTony_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#L11814:34
simondodsleyPure added this support some time ago - this is the patch we applied. Might help. https://review.opendev.org/c/openstack/cinder/+/77978114:35
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:35
jbernardTony_Saad: our in-tree doc is here: https://opendev.org/openstack/cinder/src/branch/master/doc/source/contributor/high_availability.rst14:36
whoami-rajatI couldn't find any document regarding A/A deployment but geguileo did most of the work so he might know better14:37
simondodsleythere isn14:37
geguileowhoami-rajat: I don't think there's any A/A deployment configuration14:37
geguileodocs14:37
simondodsleythere isn't any tempest test for this. We have to take it on your word that you tested your driver in an A/A configuration14:38
geguileoit's to not configure host/backend_host, configure cluster, deploy a DLM and configure it in cinder.conf14:38
whoami-rajatok so I'm not that bad at google search14:38
Tony_Saadhappystacker question is how to get the checkmark?14:38
simondodsleysee the pure patch I just listed14:39
geguileoTony_Saad: We are going with an honor system14:39
geguileoVendor says it works, we believe them14:39
eharneybe aware that you have to also audit the design of your driver and know that it will work correctly in an A/A environment14:39
Tony_SaadThanks I will relay the information to happystacker 14:40
geguileoTony_Saad: so basically submit patch to set the flag, and answer the questions from the reviewers14:41
geguileowho will ask pertinent questions to confirm that things have been tested/audited14:41
Tony_SaadThank you!14:43
whoami-rajatanything else on this topic Tony_Saad ?14:43
Tony_SaadFrom me no. From Happystack maybe. but that will have to wait for next meeting14:44
Tony_SaadThanks!14:45
abdiWhoami-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.html14:45
whoami-rajatgreat14:45
whoami-rajatabdi, they are added with the driver patch14:45
abdiThank you.  So no action on my end?  14:46
simondodsleyyour patch will need to update the matrix14:47
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 matrix14:47
whoami-rajatabdi, i think you proposed the HPE XP driver right?14:47
abdiYes14:48
whoami-rajati see the changes done here https://review.opendev.org/c/openstack/cinder/+/815582/19/doc/source/reference/support-matrix.ini14:48
whoami-rajatand they're reflected in the support matrix so looks good14:48
abdiWanted to make sure nothing else was needed from us. 14:49
abdiThank you. 14:49
whoami-rajatas of now, I don't see anything apart from maintaining the CIs14:49
whoami-rajatlet me open the open discussion14:49
whoami-rajat#topic open discussion14:49
zaitcevI have review beg, or swap.14:50
eharneyi have five patches pending that are requirements changes, i think we need to land those soon?14:50
zaitcevhttps://review.opendev.org/c/openstack/cinder/+/85265414:50
SathyaHi, Cinder retype - To allow volume migration with additional extra spec to enter driver specific code14:50
Sathyai have submited a patch14:51
senriquei have a bug that i would like to highlight 14:51
whoami-rajateharney, I mentioned the os-brick ones earlier today, should be able to land those soon14:51
whoami-rajatzaitcev, you can add it to the review request section https://etherpad.opendev.org/p/cinder-antelope-meetings#L12014:51
Sathyahttps://review.opendev.org/c/openstack/cinder/+/869999 Reviewers can you please have a look at this14:51
rosmaitawhoami-rajat:  would be good to do a quick review of the mins listed in os-brick requirements.txt before release14:51
whoami-rajatrosmaita, good idea, will do that14:52
Tony_SaadDell has a handful of review requests. most notably https://review.opendev.org/c/openstack/cinder/+/84456314:52
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
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:52
senriqueRegarding the vmdk vulnerability.. there's a new bug https://bugs.launchpad.net/cinder/+bug/200456514:53
senriquei think it's not critical, but i'm not sure how target it 14:53
*** senrique is now known as enriquetaso14:53
* enriquetaso needs to do more reviews14:54
rosmaitaenriquetaso: it's not exploitable, so it's a hardening opportunity ... patch is pretty small, hopefully can get reviewed soon14:55
eharneyenriquetaso: rosmaita: please add a comment to the bug pointing to the patch14:55
rosmaitawill do14:56
whoami-rajatcinder team ^ please take a look at the review request section from time to time14:56
enriquetasooh true, we talked about it last week rosmaita 14:56
enriquetasomy bad14:56
jbernardzaitcev: i will look at your sparse patch today14:56
whoami-rajatzaitcev, since it's a feature, I've added it to the list of features here https://etherpad.opendev.org/p/cinder-antelope-features#L3214:57
whoami-rajatbut others please add your features if you want to get them in for Antelope release14:57
whoami-rajats/others/everyone14:57
zaitcevOh. I need a blueprint, then?14:57
rosmaitaeharney: https://review.opendev.org/c/openstack/cinder/+/871976 (added it to the bug)14:57
whoami-rajatzaitcev, did we have a spec for it?14:58
zaitcevwhoami-rajat: Restore-to-sparse started as a Red Hat bug for me, https://bugzilla.redhat.com/show_bug.cgi?id=185570914:59
whoami-rajatok, i think this needs some discussion then14:59
zaitcevwhoami-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
whoami-rajatusually we do a BP and spec first then implement the feature15:00
whoami-rajatin some cases, we skip the spec if it's straightforward15:00
whoami-rajatbut let's discuss about it15:00
whoami-rajatwe're out of time15:01
whoami-rajatthanks everyone for joining15:01
whoami-rajat#endmeeting15:01
opendevmeetMeeting ended Wed Feb  8 15:01:10 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
opendevmeetMinutes:        https://meetings.opendev.org/meetings/cinder/2023/cinder.2023-02-08-14.00.html15:01
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/cinder/2023/cinder.2023-02-08-14.00.txt15:01
opendevmeetLog:            https://meetings.opendev.org/meetings/cinder/2023/cinder.2023-02-08-14.00.log.html15:01
whoami-rajatzaitcev, blueprints are good to target the features, it's not a must have but good to have thing15:02
zaitcevwhoami-rajat: I'll bring it up, maybe you'll let it slip this time using your PTL powers. Or maybe not. I'm open to doing a BP too.15:05
*** dasm|rover is now known as dasm|afk15:36
*** dasm|afk is now known as dasm|offline22:05

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!