Tuesday, 2023-03-14

manpreetk_.07:48
yasufumHi tacker team.08:00
manpreetk_hi08:00
yuta-kazatohi08:00
uehahi08:00
hiromuhi08:00
yasufum#startmeeting tacker08:01
opendevmeetMeeting started Tue Mar 14 08:01:29 2023 UTC and is due to finish in 60 minutes.  The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot.08:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:01
opendevmeetThe meeting name has been set to 'tacker'08:01
yasufumhi08:01
yasufum#link https://etherpad.opendev.org/p/tacker-meeting08:02
yasufumWe have five topics, so lets start from the first one.08:03
yasufum#topic Discussion for Tacker Antelope RC208:03
yasufumyuta-kazato: is it your update?08:04
yuta-kazatoyes. I will explain and propose them.08:05
yasufumgo ahead please08:05
yuta-kazatoThanks08:05
yuta-kazatoLast week in IRC, RC2 was agreed to.08:06
yuta-kazatoThen, I updated the status and ethepad for release team.08:06
yuta-kazato#link https://etherpad.opendev.org/p/tacker-antelope-fixes-rc08:06
yuta-kazatoAs you know, 4 patches have been merged and 1 patch (Extend FT tests for Individual Vnfc Mgmt) has move the target to Bobcat.08:07
yuta-kazatoThank you for all your contributions.08:07
yuta-kazatoHowever, the last one patch "Enhancement of Tacker API resource access control" have been reviewed..08:08
yuta-kazato#link https://review.opendev.org/c/openstack/tacker/+/87122408:08
yuta-kazatoSummary is given below.08:09
yuta-kazatoStatus: Final reviewing (reviewed by core/PTL and fixed them.)08:09
yuta-kazatoReviews: 17 unresolved and 246 resoloved comments.08:10
yuta-kazatoUpdated PS: Patchset 33, PS32 passed Zuul tests.08:10
yuta-kazatoIn fact, 6 reviewers have completed the review of main codes and only document fixes remain.08:10
yuta-kazato(unresolved comments by hamano-san.)08:10
yuta-kazatoHere's a suggestion, I think there has been enough reviews done.08:12
yuta-kazatoAnd this patch should be backported to "improve the security features" of Tacker Antelope.08:13
yuta-kazatoTherefore, we would like to final review and backport in RC2 after the document fix (proposed extend-deadline: 3/15)08:13
yuta-kazatoWould you understand and agree with this proposal?08:13
yuta-kazatoThat's all updates and proposal from my side, thanks.08:14
yasufumthanks08:15
yasufumany comment?08:17
yasufumYou've just suggested to give up one of them. So I don't opposite to the suggestion.08:18
yasufumIt seems no other comments.08:19
yasufumSo, move on to the next topic.08:19
yuta-kazatoThanks for all your undestading.08:19
yuta-kazatoAs an update, documentation corrections have also been completed at PS35. (waiting for Zuul)08:19
yuta-kazatohttps://review.opendev.org/c/openstack/tacker/+/871224/34..3508:19
yasufumOK, thanks.08:20
yasufumNext two items are from ma-ooyama, but it was already merged.08:21
uehaI see the CI status of PS35, this patch's UT is failure as for now..08:21
yasufumSorry, not for the second one.08:21
yasufumma-ooyama: anyway, is there any update for your topics?08:21
yasufumOops, ma-ooyama is not here today.08:22
yasufumWe can skip them.08:22
yasufumNext one is08:24
yasufum#topic About how to abandon the past spec which is not valid08:24
yasufumedagawa_kc: can you share your topic?08:24
edagawa_kcSure.08:25
edagawa_kcI would like to discuss how to abandon the spec which already merged officially.08:26
edagawa_kcIn Yoga cycle, I have posted the spec and then it has been merged officially. 08:26
edagawa_kcAfter that, Asahina-san took over its implementation, and then a change has been posted in this cycle.08:27
edagawa_kcThe change solves the original problem described in the spec with the different way, so actually the spec is not valid any more.08:28
edagawa_kcTherefore, I would like to ask you how I should abandon this spec, although which has been already merged officially.08:28
edagawa_kcthat's all from my side.08:29
yasufumI think we don't need to do anything actually, but any comment?08:31
takahashi-tscI also guess so, but just in case. is it OK to remain the spec which is not implemented? 08:33
yasufumI think it's the same as some old specs left as unimplemented.08:35
takahashi-tscOK, BTW, blueprint of this spec may be created. Status of the blueprint should be changed?08:36
yasufumAh08:36
yasufumSure, it might be useful.08:37
takahashi-tscOK, thanks. edagawa_kc: please change the status!08:38
yasufumThanks for the suggestion.08:38
edagawa_kcI see. I will change the status of the blueprint. Thank you.08:38
yasufumOK, let's move on to the final topic of mine.08:40
yasufum#topic Schedule of the next vPTG08:40
yasufumI just want to fix our planning of the next vPTG.08:41
yasufumAs described on the etherpad, it's enough three days for our sessions.08:41
yasufumThe event will be held from 27 to 31 March.08:42
yasufumSo, I'd suggest that March 28-30 and time slot is the same as previous vPTGs, 05-07 UTC or 15-17 JST.08:42
yasufumAgree?08:43
manpreetk_Umm in previous PTGs time slot used to be 06-08 UTC, is there any reason for 05-07 UTC?? 08:43
yasufumSorry, it's my mistake. You're right.08:43
manpreetk_ok no worries.08:44
yasufumthanks08:45
uehaI agree (March 28-30, *06-08* UTC or 15-17 JST)08:46
yuta-kazato+108:46
manpreetk_+108:46
takahashi-tsc+108:46
yasufumthanks all08:46
yasufumI'll announce our planning on the ML.08:48
yasufumFor a cross-project session suggested from hiromu, we also have to schedule it later.08:49
yasufumAnyway, it's enough for today.08:49
yasufumThanks.08:49
yasufumSo, I'd like to close this meeting if no other comment.08:50
yasufumGood08:51
yasufumThanks for joining, bye!08:51
takahashi-tscthanks08:51
manpreetk_Thanks and Bye.08:51
edagawa_kcBye.08:51
hiromubye08:51
uehathanks, bye08:51
yasufum#endmeeting08:51
opendevmeetMeeting ended Tue Mar 14 08:51:47 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:51
opendevmeetMinutes:        https://meetings.opendev.org/meetings/tacker/2023/tacker.2023-03-14-08.01.html08:51
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/tacker/2023/tacker.2023-03-14-08.01.txt08:51
opendevmeetLog:            https://meetings.opendev.org/meetings/tacker/2023/tacker.2023-03-14-08.01.log.html08:51
yuta-kazatobye08:51
uehameeting closed, but I just inform that08:52
uehaRegarding the UT error of patch 871224 I told earlier, it occurred due to ma-ooyama's patch was merged and need to fix according to it. It was resolved, so it will be posted soon. Thanks.08:52
yuta-kazatoThanks, ueha-san.08:53
uehayou're welcome :)08:53
gmannforgot to start the policy meeting17:09
gmann#startmeeting policy_popup17:09
opendevmeetMeeting started Tue Mar 14 17:09:58 2023 UTC and is due to finish in 60 minutes.  The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot.17:09
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:09
opendevmeetThe meeting name has been set to 'policy_popup'17:09
gmann#link https://etherpad.opendev.org/p/rbac-goal-tracking#L15417:10
gmanntwo review in agenda which is done17:10
gmannI will be around for couple of min if any question anyone wanted to discuss17:10
gmannif nothing let's close meeting17:17
gmann#endmeeting17:17
opendevmeetMeeting ended Tue Mar 14 17:17:13 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:17
opendevmeetMinutes:        https://meetings.opendev.org/meetings/policy_popup/2023/policy_popup.2023-03-14-17.09.html17:17
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/policy_popup/2023/policy_popup.2023-03-14-17.09.txt17:17
opendevmeetLog:            https://meetings.opendev.org/meetings/policy_popup/2023/policy_popup.2023-03-14-17.09.log.html17:17

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