14:00:05 #startmeeting glance 14:00:05 Meeting started Thu Mar 16 14:00:05 2023 UTC and is due to finish in 60 minutes. The chair is pranali. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:05 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:05 The meeting name has been set to 'glance' 14:00:05 #topic roll call 14:00:05 #link https://etherpad.openstack.org/p/glance-team-meeting-agenda 14:00:13 o/ 14:00:58 o/ 14:01:07 o/ 14:01:24 o/ 14:01:40 we have very short agenda for today, could be over in 5 -10 mins :) 14:02:11 let's start 14:02:13 #topic release/periodic jobs updates 14:02:34 Bobcat virtual PTG is just a week away 14:02:36 #link https://etherpad.opendev.org/p/bobcat-ptg-glance-planning 14:03:01 so I request all team members to have a look at PTG planning etherpad and let me know if I missed any important topics and also please add your name in the list of attendees, if you haven't added it yet 14:03:29 I'll finalize the schedule by Monday and will publish it on ML 14:04:20 anyone has any suggestion/topic for PTG ? 14:04:32 looks good to me 14:04:46 keep some slots open for last minute discussions 14:04:53 cool 14:05:16 yes, we have friday free for those 14:05:25 I add new spec, should we talk about it before PTG 14:05:35 https://review.opendev.org/c/openstack/glance-specs/+/877182 14:09:33 amnik, sure plz go ahead 14:11:15 I have an idea to create new import method, glance-builder to enable users to choose which plugins apply to the image not from config file. 14:11:38 so users can customize the flow. 14:14:23 jokke_, abhishekk, rosmaita any views on this? 14:14:39 * abhishekk at different meeting atm 14:15:10 i don't know 14:15:41 ack 14:15:42 you'd have to make an allowance for some plugins that operators want used unconditionally 14:15:58 otherwise, an end user could configure something to bypass security checks 14:16:01 I would need to look at the spec to form a opinion. my first thought is 'though that this puts a lot of of pressure to the end user and we have pretty much no import plugins that would benefit of this 14:16:17 jokke_: ++ 14:16:49 maybe the way to go would be to allow the operator to configure different import pipelines or something that an end user can pick 14:17:52 Like the whole point of the import flow was that it's very uniform experience for the user and they don't need to worry or know what async operations needs to happen in the cloud side for their import to be successful 14:18:08 amnik: do you have a real use case for this, or is it just a good idea? 14:19:28 ^^ 14:19:38 rosmaita, use case for this idea i think something like EC2 image builder, that users create their own pipepline to create thier own image 14:20:42 operators develop plugins and users choose from them to create their own image. 14:21:18 that seems a bit different from import ... we expect that the image has been created already by whatever means 14:21:57 i'm not saying you shouldn't pursue this, just that it may not be a good fit for image import 14:23:11 This is obviously just my 2cents and it has diminishing weight. Glance has always had the stance that we store & catalog the images, not build them. And at least for now I have no interest or means to work on changing that 14:23:13 in EC2 image builder also image created before and users choose from base image 14:24:24 and add something to it like import method. 14:25:46 jokke_: we do not build image, we add something to it in pipeline. 14:26:20 can you give me an example? Suppose that i have an ubuntu focal image, what would you do to it with a plugin? 14:27:47 rosmaita: for example add password complexity feature to it. or install specific package in it to customize it. 14:29:10 password complexity could be a plugin to config pam module 14:29:16 ok, but seems like that's better done using a package manager once you've booted an instance 14:29:41 Or cloudinit to automate that on the first boot 14:30:13 seems like we'd be constantly have to be updating the plugins, which doesn't seem feasible for this team 14:31:16 rosmaita: ++ 14:31:59 rosmaita: it maybee more comfortable to add this changes automatically in import method before creating instance 14:32:45 Just after a quick pass on the spec, if the team decides to explore this, I would strongly advice to trash the approach to use the database for any level of plugin management. The import plugin adoption is designed exactly to avoid any of that hassle and them plugins to get out of sync between the db and what's available on the actual host 14:34:30 And I don't think anyone here would be comfortable to create an API where users could get the host running glance to execute some arbitary code that has not been deployed by the operator in the first place 14:35:57 amnik, if you want to discuss more about this I will keep one slot for it 14:36:28 moving ahead 14:36:30 Jokke_: good, I agree with what team decided. I get final opinion on spec. 14:37:14 periodic jobs everything is green today \o/ 14:37:17 pranali: No thank you, I don't have disscuss for now 14:37:29 amnik, ack Thanks ! 14:37:41 moving to open discussions 14:37:43 #topic Open Discussions 14:38:06 how about canceling next week's meeting and directly meet in PTG ? if we don't have any important topic to be discussed in next week 14:38:35 if you have anything then please add it in the agenda, otherwise i will cancel the meeting 14:39:04 cancelling sounds good to me 14:39:40 cool 14:39:48 that's it from me for today 14:40:02 anyone has anything else to discuss? 14:40:07 Just letting ye all know. My focus is moving away from just Glance. So I'd say expectations wise, I might be skipping a lot more meetings, reviews, planning sessions etc. 14:40:19 :( 14:40:27 ohh :( 14:40:59 I will stay with RH and keep working on OpenStack, but shifting my focus on the observability side of things 14:41:32 great change to get some fresh views and learn new things after doing Glance for 9 years 14:41:57 jokke_, will you be there during glance PTG sessions? 14:42:37 pranali: not sure yet. Most likely not all of them anyways 14:43:05 ohh :( 14:43:15 Basically started onboarding into my new team this week 14:43:52 jokke_, all the best for your new plans :) 14:44:24 thanks 14:44:50 It's been incredible journey and I'm not going far ;) 14:46:00 :) 14:46:19 we just have 4 mins left :) 14:46:28 anyone as anything else? 14:46:43 or we can conclude for the day? 14:47:31 That's all from me. Just wanted to let you know now when I do 14:48:15 ack :) 14:48:41 Thanks everyone for joining !! 14:48:53 #endmeeting