Monday, 2025-08-04

*** mhen_ is now known as mhen01:41
yasufumHi tacker team.08:01
takahashi-tschi08:02
yasufum#startmeeting tacker08:03
opendevmeetMeeting started Mon Aug  4 08:03:01 2025 UTC and is due to finish in 60 minutes.  The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot.08:03
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:03
opendevmeetThe meeting name has been set to 'tacker'08:03
yasufum#link: https://etherpad.opendev.org/p/tacker-meeting08:03
yasufumSo, let's start the meeting.08:03
yasufumhi08:04
kuno316hi08:04
hi-koba_kddihi08:04
yasufumI've started to fix remained patches again from last week.08:04
yasufumI found a problem while fixing the fourth patch,08:05
yasufumhttps://review.opendev.org/c/openstack/heat-translator/+/92841208:05
yasufum, not related to the fourth patch itself.08:06
yasufumSo, I created another patch for fix the new issue.08:07
yasufumThe cause of the new issue is a change of file path which is referred from some test.08:08
yasufumSo, the solution is simple, just update the path.08:08
yasufumHowever, there is additional failure happened in the new patch.08:08
yasufumhttps://review.opendev.org/c/openstack/heat-translator/+/95262708:09
yasufumThe reason of the failure is not clear yet.08:09
yasufumThat's all my update.08:09
yasufumAny comment?08:09
yasufumgood08:10
takahashi-tschmm...I'm not sure why...08:10
yasufumyeah08:10
yasufumAnyway, go to the next item.08:12
yasufumAll the candidate patches of specs for this release merged.08:13
yasufumThank you for reviewing, team.08:13
yasufumAlthough some tiny discussion is still remained08:14
yasufumI'm expecting it will be fixed in a IRC meeting or comment on gerrit later.08:15
yasufumIs there any comment, koba-san?08:15
hi-koba_kddiThank you for the reviews08:16
hi-koba_kddiI want to ask about a comment I got in the spec review.08:16
hi-koba_kddiWe are proposing a feature to optionally recreate the volume in a v1 heal request.08:16
hi-koba_kddiBut the key name for this option is not defined in ETSI NFV.08:17
yasufumyes08:17
hi-koba_kddiRight now, our patch makes the key name configurable.08:18
hi-koba_kddiShould we contact ETSI NFV? I'm not used to the process, even if it's simple...08:19
hi-koba_kddiAny comments are welcome.08:21
yasufumthanks08:22
kuno_00316formal one way is Liaison from OpenStack to ETSI via contact person (Takahashi-san), but another option is someone (including me) can bring contribution to NFV.08:23
hi-koba_kddiHmm, I see.08:24
takahashi-tscIn my understanding, someone need to create some PPT discussion paper, right?08:25
yasufumMy comment was simple that it should be self-explanatory.08:25
yasufumBut it's better if it's a part of the standards.08:26
yasufumtakahashi-tsc: Do you think it's time comsuming?08:27
yasufumor take a long time?08:27
takahashi-tscI don't think we need so much time. and depending on our message to NFV. What is our reqeust?08:29
hi-koba_kddiI don't know the details.. It's a suggestion for the format of the healRequest in SOL003.08:31
yasufumIMO, it's simple change as koba-san noticed, and no need to make a proposal for the standards.08:34
yasufumBut it might be better to ask kuno-san's opinion.08:34
yasufumor takahashi-san.08:34
yasufumhi-koba_kddi: discuss the topic in the next meeting by refering your spec?08:36
hi-koba_kddiyes.08:37
takahashi-tscHmm.. as everyone said, this is small change and I'm not sure we should tell something to NFV. 08:37
takahashi-tscFor example, we can present our implementation with creating PPT discussion paper and just ask NFV members if they have any comments or concern.08:37
takahashi-tscJust my personal opinion, and I'm not sure it is actually needed.08:38
hi-koba_kddiSorry for making this a bit confusing. We made the key name changeable because it's not in the standard... and that's why this discussion started.08:40
kuno_00316If you want to changes NFV spec, I would suggest to contribute or liaison to NFV. but if it is just implementation to use NFV spec, we do not need to contribute it to NFV.08:41
yasufumOK, thanks.08:42
yasufumhi-koba_kddi: On the next meeting, could you tell us about your change and let us know if you have any concern if it's not included in the standards?08:45
hi-koba_kddiok08:45
yasufumThanks.08:46
hi-koba_kddiI'll summarize the changes and key points.08:47
yasufumok08:47
yasufumSo, let's move on to the next item.08:47
yasufumshivam might not be available today.08:48
yasufumDo you know is therer any update, takahashi-san?08:48
takahashi-tscAbout Zuul fix, right? Today we do not have any discussion topics. Fixing issues is in-progress.08:48
yasufumgood08:49
yasufumOK08:49
yasufumNow all the topic done for today,08:49
yasufumThank you guys for discussion.08:50
yasufumLet's close this meeting.08:50
hi-koba_kddiThanks08:50
yasufumBefore closing, I'll skip the next week meeting due to summar summar vacation.08:51
yasufumI'm going to send a e-mail on the ML.08:51
hi-koba_kddiok08:52
yasufumThank you for joining, bye!08:52
takahashi-tscsure, I will be on summer vacation next week08:52
takahashi-tscthank you08:52
yasufum#endmeeting08:52
opendevmeetMeeting ended Mon Aug  4 08:52:32 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:52
opendevmeetMinutes:        https://meetings.opendev.org/meetings/tacker/2025/tacker.2025-08-04-08.03.html08:52
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/tacker/2025/tacker.2025-08-04-08.03.txt08:52
opendevmeetLog:            https://meetings.opendev.org/meetings/tacker/2025/tacker.2025-08-04-08.03.log.html08:52

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