14:00:07 #startmeeting glance 14:00:07 Meeting started Thu Jun 30 14:00:07 2022 UTC and is due to finish in 60 minutes. The chair is pdeore. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:07 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:07 The meeting name has been set to 'glance' 14:00:08 #topic roll call 14:00:08 #link https://etherpad.openstack.org/p/glance-team-meeting-agenda 14:00:12 o/ 14:00:16 o/ 14:00:57 o/ 14:01:27 abhishekk, how are feeling now? I thought you will not around today 14:01:34 * abhishekk down with fever so probably will leave after the meeting 14:02:00 not much well 14:02:10 will signoff after the meeting 14:02:19 o/ 14:02:26 ack 14:02:34 I think rosmaita is not around 14:02:45 yeah he is on PTO 14:02:56 lets wait few minutes for everyone to join 14:04:29 ack 14:05:29 I think jokke_ and Cyril are not around, 14:05:54 shall we start or wait for few more mints ? 14:06:05 we should start 14:06:11 ok 14:06:13 #topic release/periodic jobs 14:06:20 Milestone 2 is 2 weeks away from now 14:06:35 JFYI, I have updated the release schedule doc as well with the glance spec freeze date for Zed schedule 14:06:41 #link https://releases.openstack.org/zed/schedule.html 14:07:04 So next week would be review party week, as we have decided during PTG to have this 10 days before milestone release 14:07:06 ack, thank you for updating the schedule 14:07:24 ok 14:07:28 we will discuss about finalizing the date in the dedicated topic today 14:07:30 so we'd need 3,4 cores :) 14:07:38 I'll be out all next week except for tuesday, FYI :) 14:07:47 I will be around 14:08:01 I will also be around 14:08:20 we can make an exception and have this review party one week later after the release or during release week 14:08:48 11th or 12th July 14:08:55 +1 14:09:51 we can spend one hour and go through some important patches 14:10:29 or on scheduled time we may have jokke_ brian me and cyril as core and pdeore as well 14:10:57 Brian isback next week, right? 14:11:13 5th I believe 14:11:16 yes, he will be there on 5th 14:11:25 so mayeb the 7th would be alright after all 14:11:35 sounds good 14:11:43 7th same as meeting time 14:12:15 sounds like a plan 14:12:48 cool, 14:12:49 unless dansmith has objection us doing it without him 14:12:54 lol 14:12:58 cool, pdeore make a note of it 14:13:05 we will miss you dansmith 14:13:17 heh 14:13:25 abhishekk, ack 14:13:44 moving ahead :) 14:13:54 we have released glance-store stable/wallaby with some important bug fixes 14:13:56 dansmith: maybe we call ya an hour before, just to make sure you don't want to join us? :P 14:14:41 Periodic Jobs are all green except fips jobs failing with RETRY_LIMIT 14:14:41 you go right ahead.. I'll be far from cell range (and even pavement) 14:14:56 wow 14:14:56 dansmith: sounds gr8, enjoy 14:15:11 :) 14:15:24 pdeore: any idea what it's retrying? 14:17:02 seems 'nslookup_target' is undefined 14:17:13 that's supposed to be resolved 14:17:21 we should poke ade_lee 14:17:46 ok 14:19:07 ok, moving to next topic 14:19:14 #topic Spec for review 14:19:25 [APIImpact] Add DELETE api for metadef resource types #link https://review.opendev.org/c/openstack/glance-specs/+/818192 14:19:46 This is the only spec remaining from our review list, which is a low priority but good to have I think. 14:20:12 I assume that everyone is agreed on having the separate Delete api for resource type rather than auto-deleting with some periodic operation. 14:20:53 I will have a look at it, I am pro for having API for it 14:21:12 tbh, 14:21:33 I haven't really gotten a clear understanding of why we can't delete when the last use is deleted 14:21:56 I think both rosmaita and I preferred that approach, but I'm not sure I ever got clarity on why it wasn't okay 14:22:37 i didn't aware about that approach, will think on it 14:22:55 Bcz I think it can be used later by someone if available.. 14:23:04 but what does that matter? 14:23:12 not much 14:23:21 they're auto-created in the first place, why not auto-delete them when they're no longer used? 14:24:30 if they are auto-created then I guess we can delete it if it is not used on last delete 14:24:41 that's what we were thinking 14:25:28 I tend ot agree with Brian and Dan here. I think the fact that there is no create api at all for the resource type is good indication that we likely don't need user action to delete them either 14:25:32 yeah right, that's why we had a discussion during PTG to have create & delete both similar to other metadef apis 14:26:09 right, it's just an extra step for the user (or client or whatever) to have to delete them to clean up 14:27:41 crazy question. Does the resource type contain any valuable information for it to exists as it's own resource in the db in first place? 14:27:45 yeah so if we are not having create then let's not have delete as well 14:28:18 pdeore, I guess this approach will reduce your work as well 14:28:21 not really I think 14:28:28 yeah :) 14:28:49 Like is there a reason why it wouldn't be extra field on the namespace entry rather than being it's own thing in general 14:29:14 it's used by multiple things when it's used, 14:29:25 so I think that's why it is its own entity, for the relation 14:29:30 ok, so makes sense to keep it as it's own entity 14:29:33 but it's auto-created when you create a namespace that uses it 14:29:35 yeah 14:32:11 Next crazy question I have then is, if we decide to take the route of auto-delete instead of new API call, do we even need full spec for this? 14:32:36 Or can that be converted to -lite and done as best effort refactoring as convenient? 14:33:00 sounds good to me 14:33:10 not sure we even need a lite spec 14:33:11 could be a bug 14:33:15 but sure :) 14:33:42 if we convert it to bug then we don't need to worry about spec freeze :D 14:33:52 but I think lite spec will be good 14:33:53 \o/ 14:34:00 /o\ 14:34:02 cool :) 14:34:03 :D 14:34:59 I will discuss this offline with pdeore later 14:35:03 lets move ahead 14:35:10 yeah, sure 14:35:22 #topic Columbus PTG Team signup 14:35:27 this is me 14:35:50 I need to fill a survey for Infra about head counts for October PTG 14:36:02 who is planning to attend this time? 14:36:17 I am thinking to give approx 7/8 head count 14:36:41 I have no idea as I haven't heard anything about our travel planning for it yet 14:36:51 we will soon 14:38:29 ok, I will give tentative count for this and we can modify it later 14:38:40 Reminded that air travel is not compatible with our CO2 emissions goals for the end of the century 14:38:43 Reminder* 14:39:00 ++ 14:39:05 and we should probably start by stopping intercontinental travel 14:39:15 and therefore downsizing meetings :/ 14:39:16 croelandt: fortunately I'm on the coast line, so they can hire a yacht to take me over the pond :P 14:39:28 :D 14:39:33 * croelandt checks whether yachts are worse than planes 14:39:47 depends on the yacht 14:40:21 jokke_, if you get one then take a small detour and pick me up as well 14:41:18 abhishekk: then we can meet at Dan's house and take road trip from there 14:41:32 it's a long road trip from here :) 14:41:34 cause that's so carbon neutral plan as any 14:41:50 I am in :D 14:41:59 and especially not carbon-neutral in any of my cars :) 14:42:00 dansmith: other option is that you hop on, it's longer but nicr trip if we get around via Panama 14:42:17 nothing is truly carbon-neutral 14:43:40 lets move to open discussion, we can discuss the possible road trip a week after once dansmith is back 14:43:55 heh 14:44:10 moving to open discussions :D 14:44:11 #topic Open Discussions 14:44:34 there are few glance patches open,please have a look at those 14:44:49 important is glance-download and immediate caching 14:46:15 oh speaking of which 14:46:31 the fips job fix is submitted by Ada, just not reviewed 14:46:41 847089 14:46:43 ack 14:46:46 if you're looking at the glance patch, 14:46:58 yup 14:47:00 he decided to fix it globally, so I thought that glance patch was not required anymore 14:47:13 specially mentioning the nslookup_target 14:47:31 right, 14:47:40 although I see he depends on the base patch, so maybe both are required, 14:47:44 but from the discussion I thought not 14:47:49 well it's depending on the zuul job patch 14:48:00 so I'd expect it being still needed 14:48:21 yeah, okay maybe so 14:49:44 if get time I will have a look at that patch 14:50:37 it's just zuul config, so if he says it's required we might as well just slam it in 14:50:50 ack 14:51:01 I just rechecked the experimental job so we'll see 14:51:12 cool 14:51:16 I think we are good for today, nothing else from me other than some review requests 14:51:37 ack 14:51:37 nothing from me 14:51:54 let's wrap up then .. 14:52:04 thank you all o/ 14:52:06 Thanks everyone for joining !! 14:52:09 have a nice weekend 14:52:27 #endmeeting