| *** mhen_ is now known as mhen | 01:25 | |
| yasufum | Hi, tacker team. | 08:01 |
|---|---|---|
| yasufum | hi | 08:09 |
| yasufum | hi | 08:10 |
| kuno316 | hi | 08:10 |
| hi-koba | hi | 08:11 |
| yasufum | Do you guys have any topic for today, or skip if nothing? | 08:11 |
| yasufum | since takahashi-san and shivam-san are not here today. | 08:11 |
| kuno316 | I do not have any topic. | 08:12 |
| hi-koba | I have a topic about contributing to standards that we discussed last week. | 08:13 |
| yasufum | fine | 08:13 |
| yasufum | #startmeeting tacker | 08:13 |
| opendevmeet | Meeting started Mon Aug 18 08:13:49 2025 UTC and is due to finish in 60 minutes. The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot. | 08:13 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 08:13 |
| opendevmeet | The meeting name has been set to 'tacker' | 08:13 |
| kuno316 | But I want to know conclusion of last discussion whether Tacker has feedback to NFV related to recreating resource. | 08:14 |
| yasufum | OK | 08:14 |
| hi-koba | In conclusion, the definition has already been added to the standard. | 08:15 |
| hi-koba | I also wrote about it on etherpad. | 08:15 |
| kuno316 | Thank you. | 08:15 |
| hi-koba | I'm thinking if I should change my code to reflect this. | 08:16 |
| yasufum | Is there any concern to change your code actually? | 08:18 |
| hi-koba | I have some concerns. | 08:20 |
| hi-koba | My proposal this time is a VDU-specific Heal. | 08:21 |
| hi-koba | This standard is not limited to that, so we may have to change the Heal of the entire VNF. | 08:22 |
| kuno316 | SOL002 already have VNFC level healing, but NFV member had big concern VNFC/VDU level healing for SOL003 due to breaking layering when I proposed to align spec between SOL002 and SOL003. SOL002 does not work your usecase? | 08:24 |
| hi-koba | I see. | 08:24 |
| hi-koba | Sorry. I haven't seen SOL002 yet. | 08:26 |
| kuno316 | OK, please check SOL002 healing which includes vnfcInstanceId in clause 5.5.2.9 in SOL002 https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/002/05.01.01_60/gs_NFV-SOL002v050101p.pdf | 08:28 |
| hi-koba | I just saw it. It just contains the vnfcInstanceId. | 08:28 |
| kuno316 | Yes. | 08:28 |
| hi-koba | It is not too difficult to change the request conditions for VNFC-specified Heal to conform to this standard. | 08:30 |
| hi-koba | If you don't mind VNF Heal not being included, you can patch it according to this standard. | 08:33 |
| hi-koba | In the first place, if VNFC-level Heal is not recommended as a standard, it would be easier to not follow the standard this time and just patch the current code. | 08:35 |
| kuno316 | NFV recommend VNFC level heal for SOL002 which is EM and VNFM reference point. But NFV does not recommend to add VNFC level healing to SOL003 which is NFVO and VNFM reference point. | 08:39 |
| hi-koba | ummm. I see. | 08:40 |
| kuno316 | In my understanding, VNF LCM API of Tacker follows for both SOL002 and SOL003, it means that Tacker API already follows SOL002 specification. | 08:40 |
| kuno316 | Therefore, it is OK to use vnfcInstanceId in Healing by Tacker. | 08:41 |
| hi-koba | Thank you. KDDI only uses VNFC-level Heal, so the concern was about the VNF-level Heal functionality. | 08:43 |
| kuno316 | According to concept of ETSI NFV spec, since NFVO or OSS does not know VNFC level granularity, VNFM can know which VNFC should be healing by VNFM itself triggered by LCM API (Healing request and cause). I think Tacker does not need to care VNF-Level heal functionality in current capability. | 08:46 |
| hi-koba | ok. | 08:47 |
| hi-koba | Now that I think about it, `healingResource` is a new field, which will affect the CLI, so there are still issues with the modifications... | 08:47 |
| kuno316 | Ogawa-san, do you have any idea? Do you know if Tacker has capability to heal whole VNF function? | 08:48 |
| yasufum | I don't know without checking the docs for now, sorry. | 08:49 |
| kuno316 | Koba-san, according to today's discussion, you do not have any concern to align NFV standard, but you still have concern on impact on other functionality like CLI, is my understanding correct? | 08:53 |
| hi-koba | Yes. | 08:54 |
| hi-koba | As for CLI changes, they will not be available in this release, so they will likely be available next time. | 08:55 |
| hi-koba | It might be better to bundle the patches into the next release. | 08:56 |
| hi-koba | The current code does not comply with the standards, so we will limit it to use at KDDI and not patch it if it is better not to do so. | 08:57 |
| yasufum | hmm | 08:58 |
| yasufum | I have no better idea than your suggestion. So, please do that if you're OK. | 09:01 |
| yasufum | We have no reason to merge such a temporary change out of the standards without any urgent situation. Thanks. | 09:03 |
| yasufum | kuno316: what do you think? | 09:03 |
| kuno316 | I think it is OK to provide step by step. | 09:04 |
| hi-koba | ok. | 09:04 |
| hi-koba | This time, I would like to create it as much as possible according to the standards. | 09:06 |
| yasufum | OK, thanks. | 09:07 |
| hi-koba | If not, we aim to integrate it into the next release. | 09:07 |
| yasufum | good | 09:07 |
| hi-koba | Sorry for the unclear explanation.. and thank you for discussing!! | 09:09 |
| hi-koba | Is there a date set for the Tucker RC-1? | 09:09 |
| yasufum | It's the same as all other projects. | 09:10 |
| hi-koba | Sorry. ok. | 09:10 |
| hi-koba | Sep 08 - Sep 12 R-3 RC1 target week | 09:11 |
| hi-koba | I understand that this is it | 09:11 |
| yasufum | Yes. It's because the schedule is handled by releases team and we have to follow. | 09:11 |
| hi-koba | ok | 09:12 |
| yasufum | link: https://releases.openstack.org/flamingo/schedule.html | 09:12 |
| hi-koba | thanks | 09:13 |
| yasufum | Any other comment, or close this meeting? | 09:13 |
| yasufum | It's over the end of the time for today. | 09:13 |
| hi-koba | I am done | 09:14 |
| yasufum | OK, thanks. | 09:15 |
| yasufum | So, let's close this meeting. | 09:15 |
| yasufum | Thank you for joining, bye! | 09:15 |
| hi-koba | thank you. | 09:15 |
| hi-koba | bye! | 09:15 |
| yasufum | #endmeeting | 09:16 |
| opendevmeet | Meeting ended Mon Aug 18 09:16:01 2025 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:16 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/tacker/2025/tacker.2025-08-18-08.13.html | 09:16 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tacker/2025/tacker.2025-08-18-08.13.txt | 09:16 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/tacker/2025/tacker.2025-08-18-08.13.log.html | 09:16 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!