13:59:26 <pdeore> #startmeeting glance
13:59:26 <opendevmeet> Meeting started Thu Jun  1 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:26 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:59:26 <opendevmeet> The meeting name has been set to 'glance'
13:59:26 <pdeore> #topic roll call
13:59:26 <pdeore> #link https://etherpad.openstack.org/p/glance-team-meeting-agenda
13:59:33 <pdeore> o/
13:59:37 <abhishekk> o/
13:59:40 <dansmith> o/
14:00:09 <pdeore> lets wait few minutes for others to join
14:01:26 <mrjoshi_> o/
14:01:43 <pdeore> ok let's start, Cyril is on leave
14:01:48 <pdeore> #topic release/periodic jobs updates
14:01:51 <abhishekk> I think rosmaita is in another meeting
14:01:56 <pdeore> yeah
14:02:13 <pdeore> M2 is 1 month from now i.e, in first week of July which will be spec freeze for us as well
14:02:34 <pdeore> So, Kindly please give your some time on spec reviews before the deadline :)
14:03:01 <pdeore> we will discuss about the specs in detail in next topic
14:03:13 <pdeore> Periodic job all green except some functional-py39 jobs failing intermittently ..
14:03:33 <abhishekk> need to check those failures ^^
14:03:49 <rosmaita> o/
14:04:12 <pdeore> yeah will check that
14:04:38 <pdeore> moving to next
14:04:46 <pdeore> #topic Important reviews
14:05:08 <pdeore> As discussed during PTG regarding the RBD trash feature, eharney has submitted the patch in last week
14:05:09 <pdeore> #link https://review.opendev.org/c/openstack/glance_store/+/884524
14:05:22 <pdeore> now we would need to work on the spec for the same
14:05:48 <eharney> yes should i start a draft of that shortly?
14:06:10 <pdeore> eharney, yeah sure
14:06:21 <eharney> ok, will do
14:06:42 <abhishekk> eharney, thanks, I have added couple of questions on the patch, please confirm
14:06:50 <pdeore> eharney, thanks !
14:06:52 <abhishekk> *when you have time
14:07:11 <eharney> sure, thanks, will give them a look today
14:07:48 <abhishekk> ack, thank you!
14:08:25 <pdeore> let's move to the next topic
14:08:34 <pdeore> #topic Specs
14:08:55 <pdeore> We have few specs up for review which need cores attention, so kindly please have a look,
14:09:03 <pdeore> #link https://review.opendev.org/c/openstack/glance-specs/+/883491
14:09:28 <dansmith> I think we (and when I say we I mean you) should merge the location api spec update :)
14:09:32 <pdeore> Rajat has updated the new location api spec please have a look, I hope this would be the final design now :P
14:10:22 <pdeore> dansmith, yeah ofcourse :D but need 2 +2 again :D
14:10:26 <abhishekk> Even while implementing if we found loophole we can amend it again
14:10:32 <dansmith> pdeore: you've got them
14:10:34 <abhishekk> it has 2 +2s
14:10:45 <pdeore> ohh i missed that :/
14:10:50 <dansmith> rosmaita was -1 only on a formatting thing also, so I expect he would be +2 on the current version as well
14:13:16 <pdeore> rosmaita, if you have time please have a final look on this, so that I will approve it :)
14:13:29 <rosmaita> ack
14:13:30 <pdeore> ok, next is
14:13:32 <pdeore> #link https://review.opendev.org/c/openstack/glance-specs/+/881951 - Spec Lite: Add new location strategy
14:14:05 <pdeore> abhishekk, ohh you updated it ? Thanks !
14:14:31 * abhishekk learning from dansmith to work fast :D
14:14:38 <dansmith> lol
14:14:52 <pdeore> and i more we have is , #link https://review.opendev.org/c/openstack/glance-specs/+/880627
14:15:00 <pdeore> Repropose Spec for the Glance part of Image Encryption (Bobcat)
14:15:08 <abhishekk> for this you need Luzi to confirm
14:15:09 <pdeore> abhishekk, :D
14:15:19 <pdeore> abhishekk, yeah
14:15:47 <pdeore> ohh i missed to add her on this , will do that
14:15:54 <abhishekk> ack
14:16:18 <pdeore> ok, i think that's it from me
14:16:22 <pdeore> moving to next topic
14:16:24 <pdeore> #topic Missing rbac tests in plugin
14:17:23 <pdeore> yes we have location api, cache api, import api  missing in plugin
14:17:35 <abhishekk> We have some tests missing in tempest plugin for some policies, i think those needs to be added
14:18:13 <pdeore> do we need to add tests for existing location apis? since we are anyways going to add for new loc api ?
14:18:32 <abhishekk> yes, since it will be there for next two cycles (or more)
14:18:39 <dansmith> yes agree
14:18:43 <pdeore> hmmm ok :/
14:19:33 <abhishekk> that's it, I think we should cross check plugin tests with API documentation
14:20:19 <pdeore> abhishekk, yes
14:21:56 <pdeore> I will try to add these missing test while adding tests for new location apis
14:22:26 <dansmith> priority should be the new location implementation though I'd say
14:23:18 <pdeore> dansmith, yeah of course
14:24:26 <pdeore> That's it from me, let's move to open discussions
14:24:40 <pdeore> #topic Open Discussions
14:24:54 <abhishekk> dansmith, I have one question for you related to unified limits
14:25:22 <abhishekk> we have default value say 1000 for image_size_total
14:25:34 <abhishekk> I want to increase the default size, is it possible?
14:25:44 <dansmith> in devstack you mean?
14:26:01 <abhishekk> anywhere, lets say devstack
14:26:04 <abhishekk> Looking at current documentation it is not possible
14:26:13 <dansmith> why do you say that?
14:26:21 <abhishekk> https://docs.openstack.org/api-ref/identity/v3/?expanded=update-registered-limit-detail#update-registered-limit
14:26:44 <abhishekk> it requires either service_id, region or resource_name different
14:27:21 <abhishekk> I don't know the reason behind this condition though
14:27:56 <dansmith> that's only if you want to change them right? they're optional
14:28:03 <abhishekk> As of now, once we registered limit through default value, we will not able to increase or decrease it
14:28:11 <dansmith> if you specify the limit by id, you can change just the default_limit
14:28:29 <abhishekk> no it gives 409 error
14:28:56 <dansmith> then that's a keystone (or osc) bug I think based on that description
14:28:59 <dansmith> what command are you running?
14:29:00 <abhishekk> The UUID of the service to update to which the registered limit belongs. Either service_id, resource_name, or region_id must be different than existing value otherwise it will raise 409.
14:29:11 <dansmith> but those are optional
14:29:21 <abhishekk> openstack registered limit set
14:29:37 <dansmith> if you provide them, you're saying "change X to X" which is why it 409s I think
14:29:41 <dansmith> abhishekk: the full command :)
14:30:01 <abhishekk> ohhh
14:30:25 <abhishekk> let me paste full command, I have not tried just passing limit id and default limit
14:30:29 <dansmith> ... :)
14:31:21 <abhishekk> I will try it and check with you offline
14:31:28 <dansmith> tbh I don't like that 409 behavior because it means deployment tools can't be idempotent, but alas :/
14:31:33 <dansmith> abhishekk: cool
14:32:20 <abhishekk> openstack --os-cloud devstack-system-admin registered limit set 3b75aca754c44cd9b7ff836579cfb9aa --default-limit 200
14:32:25 <abhishekk> this is working
14:32:30 <dansmith> cool I thought so :)
14:32:40 <abhishekk> thanks!!
14:32:45 <abhishekk> That's it from me
14:33:18 <pdeore> ack, anyone has anything else to discuss?
14:33:28 <dansmith> not me
14:33:53 <pdeore> cool
14:34:47 <pdeore> let's conclude for the day
14:34:56 <abhishekk> thank you all!
14:34:56 <pdeore> Thanks everyone for joining!!
14:35:15 <pdeore> #endmeeting