08:03:01 <yasufum> #startmeeting tacker
08:03:01 <opendevmeet> Meeting 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:01 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:03:01 <opendevmeet> The meeting name has been set to 'tacker'
08:03:42 <yasufum> #link: https://etherpad.opendev.org/p/tacker-meeting
08:03:56 <yasufum> So, let's start the meeting.
08:04:03 <yasufum> hi
08:04:15 <kuno316> hi
08:04:26 <hi-koba_kddi> hi
08:04:47 <yasufum> I've started to fix remained patches again from last week.
08:05:32 <yasufum> I found a problem while fixing the fourth patch,
08:05:43 <yasufum> https://review.opendev.org/c/openstack/heat-translator/+/928412
08:06:31 <yasufum> , not related to the fourth patch itself.
08:07:03 <yasufum> So, I created another patch for fix the new issue.
08:08:10 <yasufum> The cause of the new issue is a change of file path which is referred from some test.
08:08:27 <yasufum> So, the solution is simple, just update the path.
08:08:53 <yasufum> However, there is additional failure happened in the new patch.
08:09:08 <yasufum> https://review.opendev.org/c/openstack/heat-translator/+/952627
08:09:27 <yasufum> The reason of the failure is not clear yet.
08:09:39 <yasufum> That's all my update.
08:09:47 <yasufum> Any comment?
08:10:18 <yasufum> good
08:10:35 <takahashi-tsc> hmm...I'm not sure why...
08:10:53 <yasufum> yeah
08:12:13 <yasufum> Anyway, go to the next item.
08:13:47 <yasufum> All the candidate patches of specs for this release merged.
08:13:57 <yasufum> Thank you for reviewing, team.
08:14:30 <yasufum> Although some tiny discussion is still remained
08:15:36 <yasufum> I'm expecting it will be fixed in a IRC meeting or comment on gerrit later.
08:15:56 <yasufum> Is there any comment, koba-san?
08:16:06 <hi-koba_kddi> Thank you for the reviews
08:16:22 <hi-koba_kddi> I want to ask about a comment I got in the spec review.
08:16:54 <hi-koba_kddi> We are proposing a feature to optionally recreate the volume in a v1 heal request.
08:17:22 <hi-koba_kddi> But the key name for this option is not defined in ETSI NFV.
08:17:32 <yasufum> yes
08:18:30 <hi-koba_kddi> Right now, our patch makes the key name configurable.
08:19:32 <hi-koba_kddi> Should we contact ETSI NFV? I'm not used to the process, even if it's simple...
08:21:05 <hi-koba_kddi> Any comments are welcome.
08:22:16 <yasufum> thanks
08:23:00 <kuno_00316> formal 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:24:01 <hi-koba_kddi> Hmm, I see.
08:25:30 <takahashi-tsc> In my understanding, someone need to create some PPT discussion paper, right?
08:25:49 <yasufum> My comment was simple that it should be self-explanatory.
08:26:15 <yasufum> But it's better if it's a part of the standards.
08:27:27 <yasufum> takahashi-tsc: Do you think it's time comsuming?
08:27:36 <yasufum> or take a long time?
08:29:31 <takahashi-tsc> I don't think we need so much time. and depending on our message to NFV. What is our reqeust?
08:31:26 <hi-koba_kddi> I don't know the details.. It's a suggestion for the format of the healRequest in SOL003.
08:34:02 <yasufum> IMO, it's simple change as koba-san noticed, and no need to make a proposal for the standards.
08:34:44 <yasufum> But it might be better to ask kuno-san's opinion.
08:34:58 <yasufum> or takahashi-san.
08:36:48 <yasufum> hi-koba_kddi: discuss the topic in the next meeting by refering your spec?
08:37:16 <hi-koba_kddi> yes.
08:37:19 <takahashi-tsc> Hmm.. as everyone said, this is small change and I'm not sure we should tell something to NFV.
08:37:51 <takahashi-tsc> For example, we can present our implementation with creating PPT discussion paper and just ask NFV members if they have any comments or concern.
08:38:26 <takahashi-tsc> Just my personal opinion, and I'm not sure it is actually needed.
08:40:05 <hi-koba_kddi> Sorry 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:41:19 <kuno_00316> If 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:42:35 <yasufum> OK, thanks.
08:45:37 <yasufum> hi-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:56 <hi-koba_kddi> ok
08:46:39 <yasufum> Thanks.
08:47:01 <hi-koba_kddi> I'll summarize the changes and key points.
08:47:06 <yasufum> ok
08:47:29 <yasufum> So, let's move on to the next item.
08:48:28 <yasufum> shivam might not be available today.
08:48:44 <yasufum> Do you know is therer any update, takahashi-san?
08:48:48 <takahashi-tsc> About Zuul fix, right? Today we do not have any discussion topics. Fixing issues is in-progress.
08:49:01 <yasufum> good
08:49:45 <yasufum> OK
08:49:53 <yasufum> Now all the topic done for today,
08:50:09 <yasufum> Thank you guys for discussion.
08:50:17 <yasufum> Let's close this meeting.
08:50:26 <hi-koba_kddi> Thanks
08:51:24 <yasufum> Before closing, I'll skip the next week meeting due to summar summar vacation.
08:51:56 <yasufum> I'm going to send a e-mail on the ML.
08:52:03 <hi-koba_kddi> ok
08:52:12 <yasufum> Thank you for joining, bye!
08:52:18 <takahashi-tsc> sure, I will be on summer vacation next week
08:52:21 <takahashi-tsc> thank you
08:52:32 <yasufum> #endmeeting