Thursday, 2023-05-11

croelandtabhishekk: can we push https://review.opendev.org/c/openstack/glance-specs/+/880030 ? :)13:54
abhishekkcroelandt, pdeore is PTL now, she has the power to approve or reject :D13:58
croelandtoh right only the PTL can approve?13:59
pdeore#startmeeting glance13:59
opendevmeetMeeting started Thu May 11 13:59:26 2023 UTC and is due to finish in 60 minutes.  The chair is pdeore. Information about MeetBot at http://wiki.debian.org/MeetBot.13:59
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:59
opendevmeetThe meeting name has been set to 'glance'13:59
pdeore#topic roll call13:59
pdeore#link https://etherpad.openstack.org/p/glance-team-meeting-agenda13:59
pdeoreo/13:59
pdeorecroelandt, abhishekk I was thinking to wait for today, if there are no objections then I will set the +W14:00
pdeoreshall we start? I think everyone is here :)14:01
mrjoshio/14:01
croelandto/14:01
pdeoreok, let's start14:01
pdeore#topic release/periodic jobs updates14:01
rosmaitao/14:01
pdeoreWe are in M1 release week, and i think we are good to tag M114:01
pdeorewaiting for the config refresh patch to merge, then I will submit the release patch today14:02
abhishekko/14:02
pdeorefor glance_store release we need to wait for os-brick release 14:02
abhishekkrosmaita, could you please keep watch on it?14:02
pdeorerosmaita, can we update the glance_store hash after os-brick release14:02
abhishekkyou can update the hash now but release should be done after os-brick release14:03
rosmaitaok, so what i would like to do is this14:03
rosmaitathe os-bricks have been released14:03
dansmitho/14:04
rosmaitabut the upper constraints have not been updated14:04
rosmaitadue to a pep8 problem14:04
rosmaitaanyway, the glance-store change has merged, but i think we should update the min version of os-brick in setup.cfg14:04
rosmaitabefore doing the new glance_store releases14:04
rosmaitai have patches up for that14:05
rosmaitagimme a sec to find the link14:05
rosmaitahttps://review.opendev.org/q/topic:bug/2004555+project:openstack/glance_store14:05
pdeoreack,14:05
rosmaitaanother problem is that as far as i can tell, the stable/2023.1 upper constraints are not being updated by the bot14:06
rosmaitabut i can push a patch for that by hand14:06
rosmaitaafter the pep8 stuff is fixed in requirements14:07
pdeorethe master patch is already merged, so we can update the hash, right?14:07
rosmaitawe haven't released os-brick from master yet14:07
pdeoreyeah, https://review.opendev.org/c/openstack/releases/+/88258014:08
pdeorewe will have to wiat for this14:08
rosmaitaor, not, if we don't update the 'extras' in setup.cfg14:09
rosmaitapdeore: thanks for pointing out that patch, didn't realize elod had updated it14:10
dansmithso one option would be to just release it without the dep and then follow up later with a bump right?14:10
dansmithso that people *can* get the fix if they put the versions together14:10
dansmithwhich right now they can't easily14:10
rosmaitathere is that14:11
pdeoreok, so we can release the store after os-brick release without the dep?14:13
rosmaitawell, if we don't change the req, you can release glance_store now14:14
dansmiththat would be my preference, but on the gradient of concern, glance's exposure to this is probably the lowest of the three projects, so it's certainly less concerning than nova14:14
pdeoreok14:15
rosmaitapdeore: the situation is that the change in glance_store adds some parameters to a os-brick call that haven't changed, so using an old os-brick won't break anything with the new glance_store code14:15
rosmaita(not sure i said that clearly)14:16
pdeoreyeah i got your point14:16
rosmaitaanyway, new glance_store + old os-brick should be fine, just doesn't give you full protection for the CVE14:16
pdeorerosmaita, Is it possible for you to keep watch on this ? I will try to as much late as possible though14:17
rosmaitabut it's the "accidental part" anyway, so pretty low probability14:17
rosmaitai can do it, my time zone is good for this14:17
pdeorerosmaita, gr8 Thanks ! 14:17
pdeoreok, let's move to next topic14:18
pdeorePeriodic job all green except oslo-tips failure,  may be again version conflict issue14:18
rosmaitawhat we can do is, if the upper constraint hasn't changed by say 1800UTC, we can release without the req change14:18
pdeorerosmaita, ok14:18
rosmaita(sorry, i know you wanted to move on)14:18
rosmaitaone more question14:18
rosmaitaactually, not ... 14:19
pdeorenp, I thought we are done :)14:19
rosmaitawe will  release all the glance_store versions at 1800 UTC14:19
pdeorerosmaita, ack14:19
rosmaitai can ping dansmith to verify the hashes on the release patch14:19
dansmithsure14:19
rosmaitaok, that's all from me, thank you14:20
pdeorecool14:20
pdeorerosmaita, Thanks 14:20
pdeoreshall we move ahead ?14:20
dansmithI think it's safe :)14:21
pdeoreok, let me continue with the next peridoc job updates :)14:21
pdeoreso as I said 2 oslo-tips jobs are still failing with version conflict issue again I think14:22
pdeorebut i still wonder how the jobs which were failing till last week started passing without merging the changes submitted by croelandt ?14:23
pdeoreor I'm missing some context on this?14:23
croelandthm14:23
rosmaitait's magic14:24
croelandtyeah14:24
pdeore:D 14:24
croelandteverything is magic14:24
pdeorethen I think we should wait everytime for this magic to be happened :P14:24
pdeorecroelandt, you have abandon the py38 to p310 patch right?14:25
croelandthm not really14:25
pdeoreso we need only the one where nodeset is changed14:25
croelandtwe wanted to wait & see the results ont he tips jobs14:25
pdeoreohh ok14:25
croelandtbut we never test py310 with tips then?14:26
* croelandt is confused14:26
pdeorei think we did14:26
pdeoreohh no, not tested14:27
croelandtdamn it feels like this should be tested somehow14:27
rosmaita"this" == ?14:27
pdeoreok, let's test that and check if these recently failing ones are passing or not14:28
pdeorehttps://review.opendev.org/c/openstack/glance/+/88218514:28
abhishekkthis == py310 I think14:28
croelandtrosmaita: the tips14:28
pdeoremove to next ?14:29
pdeoremoving ahead :)14:30
pdeore#topic Important reviews14:30
pdeore#link https://review.opendev.org/c/openstack/glance/+/881940 - Add new add loc api14:30
pdeore#link https://review.opendev.org/c/openstack/glance/+/882498 - Add get loc api14:30
pdeoreI have submitted the new location apis changes, kindly please have a look14:30
croelandtWould we like these merged for M1 or was it just the spec?14:30
dansmithpdeore: I really want to review that I have just been slammed lately14:31
pdeorecroelandt, it would be nice if we can get those in m1 :)14:31
* croelandt stretches fingers14:31
pdeore#link https://review.opendev.org/c/openstack/glance-specs/+/880030 - Reproposed New Location API spec 14:32
pdeoreon spec we have 2 +2s 14:32
pdeoreI will go ahead and will set +W if there are no objections on the design until tommorw.14:32
pdeorethe sdk part for these new loc api, I've started working on, will submit the patch tmrw14:33
pdeoreany questions?14:33
* croelandt has none14:34
pdeorecool, moving to next14:34
pdeore#topic Specs14:34
pdeorewe have 2 more specs for review, so kindly please have a look14:34
pdeore#link https://review.opendev.org/c/openstack/glance-specs/+/880627 - Reproposed Image Encryption Spec14:34
pdeore#link https://review.opendev.org/c/openstack/glance-specs/+/881951 - Spec-lite Add new Location Strategy14:34
rosmaitaack14:35
pdeoremoving to next14:35
pdeore#topic Can we delete multiple images from the same store14:35
pdeoremrjoshi_ ^14:35
pdeore#link https://review.opendev.org/c/openstack/python-openstackclient/+/882086/3/openstackclient/image/v2/image.py#185414:36
mrjoshi_this is regarding the ``glance stores-delete`` which deletes image from store14:36
mrjoshi_I recently added a patch for adding support of ``glance stores-delete`` equivalent in  the openstack client .14:36
mrjoshi_There's a comment from stephen regarding it ,Currently we can only delete a single image from the store , what if user's want to delete multiple images from the same store?14:37
rosmaitathey make multiple requests14:37
mrjoshi_Can't we have it in a single request14:38
rosmaitawe don't have it for image-delete, do we?14:38
mrjoshi_we do 14:38
croelandtwe can do openstack image delete IMG1 IMG2 IMG3... ?14:38
mrjoshi_yes14:38
abhishekkwe can certainly do glance image-delete 1 2 314:39
croelandtfor the sake of consistency, it would make sense to have this behaviour everywhere14:39
croelandtas a user it infuriates me when commands are not consistent14:39
rosmaitathat's not in the API, though, is it?  (batch delete, i mean)14:39
abhishekkThe proposal is to deleted different images from same store at once (we can decide this in next PTG)14:40
abhishekkno that is not in API14:40
croelandtbut this could be in the CLI, right?14:40
abhishekkyes14:40
abhishekkits easy to do it in CLI14:40
rosmaitaso it wouldn't require any glance-side changes, not sure what the issue is here14:41
abhishekklet me tell you14:41
abhishekkwe are adding support to delete image from a store in SDK14:41
abhishekkthe maintainer suggested rather than adding new command like image store delete we should pass --store option to existing delete command14:41
abhishekkand then he asked us whether we want to add support to delete multiple images from same store14:42
abhishekkSo we can have image delete store image1, 2, 3 and so on14:42
rosmaitaso, that's an SDK design decision, that is, whether they want the SDK to diverge from the actual API14:44
croelandtseems fine to me to have the SDK do 3 calls to the API to delete 3 images14:44
croelandtrather than have the user type 3 commands to do the same 3 calls14:44
pdeore+114:46
pdeorewe have only few mins left14:47
mrjoshi_so if everyone agrees can we implement this in the patch or should we have a separate patch for it?14:47
croelandtmostly an SDK decision to be honest14:48
abhishekkyou can tell them that we can work on it later14:49
mrjoshi_ok14:49
pdeoreshall we move to open discussions now?14:50
croelandtyes14:51
pdeore#Open Discussions14:51
pdeoreI will be on PTO from 18th-25th May14:51
abhishekkI don't have anything to for Open discussion14:52
croelandtWould be nice to fix this before M1 as well :) https://review.opendev.org/c/openstack/python-glanceclient/+/88069614:52
pdeoreso won't be there for next 2 weekly meetings, any volunteer to chair the meeting for next 2 week?14:52
croelandt18th is a public holiday in France14:52
croelandtand I might take some PTO after that, gotta check my balance :p14:52
abhishekkwe can call off 18th14:53
abhishekkand 25th if anything comes urgent then I will chair it14:53
pdeoreok, I will send the mail accordingly14:53
pdeoreabhishekk, Thanks ! :)14:54
pdeoreThat's it from me 14:54
pdeoreanyone has anything else to discuss?14:54
pdeoreok, assuming nothing left.. let's conclude for today !14:55
pdeoreThanks everyone for joining !!14:56
pdeore#endmeeting14:56
opendevmeetMeeting ended Thu May 11 14:56:17 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:56
opendevmeetMinutes:        https://meetings.opendev.org/meetings/glance/2023/glance.2023-05-11-13.59.html14:56
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/glance/2023/glance.2023-05-11-13.59.txt14:56
opendevmeetLog:            https://meetings.opendev.org/meetings/glance/2023/glance.2023-05-11-13.59.log.html14:56
*** pdeore is now known as pdeore|afk14:57

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