Thursday, 2022-04-14

*** dasm|off is now known as dasm10:46
pdeore#startmeeting glance14:00
opendevmeetMeeting started Thu Apr 14 14:00:09 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
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
opendevmeetThe meeting name has been set to 'glance'14:00
pdeore#topic roll call14:00
pdeore#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:00
croelandto/14:00
pdeoreo/14:00
mrjoshio/14:00
jokke_o/14:00
pdeorelet's wait few minutes for everyone to join14:01
pdeoreI think dansmith is on PTO 14:01
rosmaitao/14:01
abhishekko/14:01
pdeoreEveryone is here, let's start 14:02
pdeore#topic Updates14:02
pdeoreAbhishek has sent the Zed PTG summary on openstack-discuss ML,14:02
pdeore#link http://lists.openstack.org/pipermail/openstack-discuss/2022-April/028115.html14:02
pdeoreSummary includes recap of what we discussed during PTG and the links to recordings as well14:02
abhishekk++14:03
pdeoreThanks abhishekk !!14:03
abhishekkI will propose priorities under or glance-specs repo early next week14:03
abhishekks/or/our14:03
pdeoreack14:03
pdeoremoving ahead14:04
pdeore #topic release/periodic jobs14:04
pdeoreMilestone 1 is one month from now, 14:04
pdeoreSo, let's try to achieve the targets we decided during PTG for Milestone 1 :) 14:04
pdeore#link https://etherpad.opendev.org/p/zed-glance-ptg#L39914:04
abhishekkfingers crossed :P14:05
pdeoreyeah :D14:05
pdeoreThe periodic jobs are all green, except 3 TIME OUTS14:06
pdeore#topic Spec For Review14:06
pdeoreThere are some specs up for review which needs some attention14:06
pdeoreNew glance-download import method - https://review.opendev.org/c/openstack/glance-specs/+/83613214:06
pdeoreExpanding store details - https://review.opendev.org/c/openstack/glance-specs/+/83560614:06
pdeoreDelete API for metadef resource types - https://review.opendev.org/c/openstack/glance-specs/+/81819214:06
pdeoreImage Export Draft - https://review.opendev.org/c/openstack/glance-specs/+/83712714:06
pdeorespec-lite: ability to purge all rows by glance-manage - https://review.opendev.org/c/openstack/glance-specs/+/819622 (one +2)14:06
abhishekkI think mrjoshi still needs to update store details spec with Security impact14:07
abhishekkand there are some comments on draft of Image export14:07
abhishekkwe will have a discussion over glance-download import method next week14:08
pdeoreI have updated the Delete API for resource types spec as well 14:09
abhishekkyes, will have a look early next week14:09
pdeoreso, requesting all to go thro' all the specs whenever possible 14:09
pdeoreabhishekk, Thanks ! :)14:10
pdeoremoving ahead14:10
pdeore#topic Secure RBAC14:10
pdeoreSo, after discussing with gmann, seems we need to wait till last week of April for glance SRBAC updates as most of the RBAC team member are unavailable for Policy pop up meeting14:10
pdeoreI'm going so set up a call with RBAC team once they are available, so if anyone from glance team is interested to be part of the SRBAC discussion, please let me know, I will send you the invite for the same :)14:11
abhishekkI will try to be there14:11
pdeorecool14:11
pdeorethat's it from me14:12
pdeoreI think next is croelandt :)14:12
croelandtI just had a couple of easy patches to review14:12
croelandtI was also wondering if, as soon as a $branch-em tag exists, the $branch can be considered unmaintained and all patches abandoned :)14:13
abhishekk1st one is merged, and for 3rd we need jokke's view14:13
abhishekkcroelandt, that should be triggered automatically :D14:14
croelandtabhishekk: yeah we still have a few patches to old branches :)14:14
croelandtbut it should, yeah14:14
jokke_croelandt: it's $branch-eol tag iirc that flags the end of an branch ... I have no idea what the -em tag is for14:15
croelandtjokke_: then pike is still maintained?14:16
abhishekkend of maintenance ?14:16
croelandtthe last eol is ocata-eol14:17
abhishekkthere is certain criteria for moving branches to eol14:18
abhishekkeol means we don't backport security patches as well14:18
abhishekkbut for em I think we do backport it if it is security issue (AFAIK)14:18
croelandthm I see14:19
jokke_croelandt: yes the stable/pike branch still exists14:19
rosmaitait's "backport as a courtesy" for security issues into -em branches14:19
abhishekkright14:19
jokke_when the -eol tag is applied the branch gets deleted14:19
abhishekkthis I didn't aware about14:20
croelandtjokke_: but what do we backport all the way back to Pike?14:20
rosmaitawe eol'd pike in cinder a while back14:20
jokke_croelandt: as far as I'm concerned nothing and we probably should eol bunch of branches. These were supposed to be taken over by the extended stable management which never seemed to formalize14:21
croelandtI see14:21
croelandtI like the strategy of having as few branches as possible14:21
croelandt+1 to that :D14:21
abhishekkI think we can surely do eol until rocky14:21
jokke_well in theory up to Victoria ... we officially support only current -214:22
jokke_that used to be the case until this extended maintenance 14:23
jokke_we killed the -3 pretty soon after the new cycle started14:23
abhishekk-3 ?14:23
jokke_current -214:23
jokke_current -3 eve14:24
abhishekkhmm14:24
abhishekkI think we also need to notify on ML about marking eol?14:24
abhishekkis this correct?14:25
jokke_so z being the current we would leave y and x and for courtesy w but even that would be stretching14:25
abhishekkI think we should keep W as we introduced RBAC in W14:26
jokke_I don't think there is any specifi policy about that 14:26
abhishekkok, I thought I saw some mails about EOL announcement14:26
jokke_and by "that" I mean ML post about it14:27
abhishekkso asked for confirmation14:27
abhishekkyep, got it14:27
abhishekkOk, I think I will propose some patches early next week to mark some of our branches as eol14:29
abhishekkand add jokke_ and rosmaita as reviewer14:29
jokke_just make sure there is no patches pending review on those branches and abandon them first if any14:30
abhishekkyep14:30
jokke_or ping for merge if approrpriate14:30
abhishekksure14:30
pdeoreshall we move to Open Discussion ?14:31
abhishekkyep14:32
pdeore#topic Open Discussion14:32
pdeoreanyone has anything to discuss?14:32
jokke_nothing from me14:32
alistarleI miss beginning of the meeting, are the glance-download already done ?14:32
croelandtnothing from me14:32
alistarle*glance-downlaod discussion :p 14:33
abhishekkalistarle, not yet, we are going to discuss it in next meeting14:33
abhishekkWas busy this week in some internal training so couldn't get time to have a look at it14:34
abhishekkbut I got some requests about how we can use this in environment which does not use federated tokens14:34
abhishekksorry for the delay from my side on reviews14:35
alistarleHmmm I think it will be handled like if the region is not found, like "No glance endpoint found for region XXX"14:35
alistarleNo problem for the review time :)14:36
abhishekkrequesting every core to have a look at the glance download spec14:36
rosmaitaack14:36
pslestangabhishekk: exactly as alistarle said, we use the catalog provided by the context, if the region does not exist for the service it will raise an error14:36
abhishekkI think have you considered other options like all-stores and allow-failure options?14:37
pslestangNot yet but I will14:37
abhishekkpslestang, I think it will be better to mention this in the spec14:37
pslestangack14:38
abhishekkallow-failure is important if there is multistore environment14:38
jokke_neither of them is related to the specific internal plugin but the handling of the import TaskFlow as whole14:38
abhishekkand we can have more discussion in next week14:39
jokke_so What I mean is that those are irrelevant when developing the download plugin ... we aren't going to delete the image from the source on either case :P14:40
pslestangok so I will wait for discussion about that topic nxt week before modifying the specs about all-stores/allow-failure14:40
abhishekkbut we do revert from all stores and delete it from staging, and I added my suggestion about it on the spec14:41
jokke_abhishekk: both of those things happens after the internal plugin has been ran14:41
abhishekks/suggestion/question14:41
abhishekkyes, you are right14:42
pslestangand one thing to remind is that glance-download is supposed to be based on web-download, so we only modify the run method and all the other things will be as it is implemented into web-download plugin 14:43
abhishekkyep, so that means it will not have any impact14:43
abhishekkbut just make sure while you do test it locally14:43
pslestangok14:43
abhishekkcool14:45
abhishekkI don't have anything else to discuss as well14:46
pdeorecool.. 14:47
pdeoreThanks everyone for joining !!14:47
abhishekkthank you!14:47
pdeoreHave a great long weekend !! :)14:47
abhishekkhave a nice and long weekend14:47
abhishekkjust FYI all, tomorrow is holiday for us(assuming everyone has it)14:48
jokke_Tomorrow and Monday here in Ireland14:49
abhishekkcool, enjoy extra long weekend :D14:49
pdeore#endmeeting14:51
opendevmeetMeeting ended Thu Apr 14 14:51:07 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:51
opendevmeetMinutes:        https://meetings.opendev.org/meetings/glance/2022/glance.2022-04-14-14.00.html14:51
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/glance/2022/glance.2022-04-14-14.00.txt14:51
opendevmeetLog:            https://meetings.opendev.org/meetings/glance/2022/glance.2022-04-14-14.00.log.html14:51
*** dasm is now known as dasm|off16:20

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