Thursday, 2023-01-19

*** dasm is now known as dasm|off01:10
*** soniya is now known as soniya29|rover05:41
*** soniya29|rover is now known as soniya29|rover|brb09:44
*** soniya29|rover|brb is now known as soniya29|rover11:25
*** dasm|off is now known as dasm13:08
pdeore#startmeeting glance13:59
opendevmeetMeeting started Thu Jan 19 13:59:42 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
mrjoshi__o/14:00
abhishekko/14:01
pdeorelets wait few minutes for others to join14:01
rosmaitao/14:01
pdeorelet's start, others may join in between14:02
pdeore#topic release/periodic jobs updates14:02
pdeoreMilestone 3 is 4 weeks away14:02
pdeoreThis is Spec freeze week and we have 2 important specs to get in, which we will see in next topic14:02
pdeorePeriodic job all green except TIME_OUT for fips jobs 14:03
pdeoremoving to next14:03
jokke_o/14:03
pdeore#topic Specs14:03
pdeore#link https://review.opendev.org/c/openstack/glance-specs/+/863209  - Repropose new location APIs spec14:03
pdeore#link https://review.opendev.org/c/openstack/glance-specs/+/868901  - (spec-lite) (cinder) Add suport to allow extend attached volumes14:03
pdeoreBoth these specs looks good to me as per the discussion happened so far on this , so kindly please have a look if you have not yet reviewed the updated one 14:04
pdeoretoday is the last day for approving specs, so if I don't see any objection on the specs today, tomorrow I will approve it14:05
abhishekkack14:05
pdeoreafter tomorrow no new/old specs will be approved for this cycle14:06
pdeoreso kindly please have a look14:06
pdeoremoving to next14:07
pdeore#topic Catching up with reviews14:07
pdeoreUpdate Migration Constant 14:07
pdeore#link https://review.opendev.org/c/openstack/glance/+/861752/14:07
pdeoreabhishekk, has updated this, kindly please have a look14:07
pdeorenext is14:08
pdeorePin glance-tempest-plugin with 0.2.0 for wallaby job 14:08
pdeore#link https://review.opendev.org/c/openstack/glance-tempest-plugin/+/86400514:08
pdeorethis is blocking other stable/wallaby patches as secure-rbac-protection-functional job is failing for stable/wallaby14:08
abhishekkthis one is important ^^14:08
pdeoreyes, please have a look on priority 14:09
pdeorethat's it from me for today14:10
rosmaitalooking at the glance-t-p patch now14:10
pdeorerosmaita, thanks !14:10
pdeoreshall we move to open discussion ? 14:11
abhishekkyes14:12
pdeore#topic Open Discussion14:12
abhishekkrosmaita, i have got one +2 on service role patch, if you manage to contact keystone guys then we can get it merged and start on glance location api work14:12
abhishekkhttps://review.opendev.org/c/openstack/keystone/+/86342014:12
rosmaitaarrrrrrrrgh .... i thought that was taken care of!14:12
jokke_As we have quite a bit of time I'd like to discuss a bit of the Rajat's cinder expand proposal. Anyone up for it?14:13
abhishekkI think rajat will be busy in cinder midcycle stuff14:14
jokke_maybe rosmaita can aswer quickly couple of my questions.14:15
pdeorejokke_, i think it would be better to comment direct on the patch, I will ping whoami-rajat after meeting for the same14:15
whoami-rajatI'm here but not sure what the context is14:16
abhishekklite spec14:16
jokke_whoami-rajat: ok, cool. Your lite-spec about the cinder extends14:16
whoami-rajatsure14:16
whoami-rajathappy to answer any concerns14:17
jokke_I'm just wondering if my assumptions are correct: 1) we have no programmatic way to know if the volume happens to support the live expansion 2) we cannot shrink the volume afterwards (or what's the reason we're stuck with 1Gb expansions)?14:17
whoami-rajat1) no, we don't, it's a backend feature which isn't reported anywhere so the info is only available in our support matrix and the operator using backend is expected to know if their backend supports this capability14:19
whoami-rajathaving said that, in current master, apart from nfs i think all backends support it14:19
* whoami-rajat quickly checks14:19
jokke_Just wondering if 1 is correct, should we do similar what we do with rdb and ramp up the amount we expand and trim once we're done writing.14:19
whoami-rajathttps://docs.openstack.org/cinder/latest/reference/support-matrix.html#operation_online_extend_support14:19
whoami-rajatthere are few of them but i haven't seen those drivers used a lot recently14:20
whoami-rajat2) no we cannot, cinder only supports extend and not shrink14:20
jokke_ohh14:20
jokke_I had no idea14:20
whoami-rajatyeah, cinder needs to cater for all backend use cases and some backends don't support shrink so it didn't make sense for cinder to do it either14:21
whoami-rajateven though some backends support it like rbd, we can't generalize it for all backends14:21
jokke_I was worried that the manual config would be error prone, but I guess it's pretty much the only way to improve things then :(14:21
jokke_whoami-rajat: well, you do online extends even all backends don't support it either ;)14:22
whoami-rajati know the 1GB expansion isn't great but that's the only way we can get accurate volume size and not overcommit storage14:22
jokke_do we reserve correct size volume to start with _if_ we know the image size beforehand (Imports)?14:23
whoami-rajatthe add method in cinder store does get a size parameter but I've no idea how it gets populated, I haven't seen in my testing the size being used and it always starts with 114:24
whoami-rajatbut if it's passed, cinder store should use that as initial volume size14:24
whoami-rajathttps://github.com/openstack/glance_store/blob/master/glance_store/_drivers/cinder.py#L960-L96214:25
jokke_ok, could you quickly add that to the spec as secondary improvement objective (so we don't need another spec for that)? As the volume operations are that heavy I think we should look into reserving correct size volume in the first place if we do have the image file on hand so we know it's size14:26
jokke_I'd be happy to +2 that as whole14:26
whoami-rajatI can but is it a future effort or expected to be done in the same effort? since it seems like a different issue of size not being passed correctly14:27
jokke_oh sorry,, missed that while I was writing14:28
jokke_so all we need is to make sure we actually populate that parameter from glance side, it would not need changes in the store14:28
jokke_then the proposal is fine as it is as sounds like it's all we really can do14:28
whoami-rajatyes, correct14:28
whoami-rajatok i will add that to the spec14:28
whoami-rajatthanks for the feedback14:29
jokke_amazing, thanks14:29
pdeorewhoami-rajat, Thanks for joining !14:29
jokke_whoami-rajat: and sory for distracting you from the midcycle efforts14:30
whoami-rajatpdeore, no problem, thanks!14:30
whoami-rajatjokke_, oh midcycle was yesterday, but I've another meeting to attend14:30
whoami-rajatthanks guys!14:30
jokke_cheers, I have nothing else for now14:31
pdeoreanyone has anything else to discuss ? or we can wrap up early14:31
abhishekk#metoo14:31
pdeorecool14:31
pdeoreThanks everyone for joining !14:31
jokke_tyty14:31
abhishekkthank you!14:31
pdeore#endmeeting14:31
opendevmeetMeeting ended Thu Jan 19 14:31:40 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:31
opendevmeetMinutes:        https://meetings.opendev.org/meetings/glance/2023/glance.2023-01-19-13.59.html14:31
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/glance/2023/glance.2023-01-19-13.59.txt14:31
opendevmeetLog:            https://meetings.opendev.org/meetings/glance/2023/glance.2023-01-19-13.59.log.html14:31
*** dasm is now known as Guest184615:29
*** Guest1846 is now known as dasm15:30
*** dasm is now known as dasm|off23:13

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