Tuesday, 2023-04-18

yuta-kazatoHi08:05
takahashi-tschi08:05
uehahi08:05
manpreetk_hi08:06
yu-kinjohi08:06
yuta-kazatoFYI: yasufumi is in Amsterdam this week to participate in Kubecon EU.08:06
yuta-kazatoMaybe he is absent from today's IRC.. Do you hear anything from him?  :takahashi-san, ueha-san08:07
uehaThanks for your informatin, I didn't hear it.08:07
takahashi-tscI also hear nothing... but there is 1 topic. Can I modarate today's meeting?08:08
uehatakahashi-tsc: sure, thank you08:09
takahashi-tsc#startmeeting tacker08:09
opendevmeetMeeting started Tue Apr 18 08:09:07 2023 UTC and is due to finish in 60 minutes.  The chair is takahashi-tsc. Information about MeetBot at http://wiki.debian.org/MeetBot.08:09
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:09
opendevmeetThe meeting name has been set to 'tacker'08:09
takahashi-tsc#link https://etherpad.opendev.org/p/tacker-meeting08:09
yuta-kazatoThanks too.08:09
takahashi-tscThere is 1 topic from yu-kinjo. Will you discuss something at today's call?08:10
yu-kinjoThank you, Takahashi-san08:10
takahashi-tsc#topic allow-VNFD-ID-duplication-among-different-tenants08:11
yu-kinjoContinuing from last week, I want to discuss about bug report "allow-VNFD-ID-duplication-among-different-tenants"08:11
yu-kinjoI received comments about enhanced_tacker_policy from <ueha> and <yuta-kazato> in last IRC.08:12
yu-kinjoI checked https://docs.openstack.org/tacker/latest/user/enhanced_tacker_policy_usage_guide.html08:12
yu-kinjoRegarding VNF packages, I understand that even if they belong to the same project, the access rights can be changed depending on the vendor.08:12
yu-kinjoHowever, I don't think the implementation for this Bug report will change whether "enhanced_tacker_policy" is true or false.08:13
yu-kinjoFor example, permissions to vnf packages whose vendor is "company-A" are limited to "VENDOR_company-A" or "VENDOR_all".08:13
yu-kinjoWhat I want to achieve is "users with rights for the resource can onboard this VNF package to each different project but cannot onboard it twice in the same project."08:14
yu-kinjoFor that, I think the following should be implemented, even if "enhanced_tacker_policy" is false.08:14
yu-kinjoDo not allow duplication of VNFD IDs within the same project, but allow duplication between different projects.08:14
yu-kinjoI think that "vendor" is not needed to consider.08:15
yu-kinjoThat's it.08:15
yu-kinjoDoes anyone has comments or questions?08:15
yu-kinjoespecially ueha-san or yuto-kazato san08:16
takahashi-tscAny comments...?08:18
uehaThank you, do you mean that the following case is no problem?08:18
uehaIf policy_enhancement is enabled and "tenant X/vendor A" user uploaded VNF Package, then "tenant X/vendor B" user can not upload same VNF Package.08:19
yu-kinjoYes. no problem.  I think a VNF package made by vendor A will be  onboarded users "vendor A" or "all". 08:22
uehaDoes it mean that vendor B will not use the package created by vendor A in the actual operation..?08:24
uehaIn the actual operation, I'm sorry that I do not know what is the case of the "same tenant" with "different vendors"..08:26
yu-kinjoAt least not for our use case... 08:26
yu-kinjoSo I think vendor B will not use the package created by vendor A in the actual operation.08:28
yu-kinjoAnd for now, I hope this bug report only covers implementations that allow duplicate VNFD IDs in different projects.08:30
uehaIf I think about it carefully, there seems be not the same Package when vendors are different in actual operation..08:30
yu-kinjoI think so too08:31
uehaThank you, I got it and I think it's okay to care about just tenant for this bug report.08:32
yu-kinjoThank you ueha-san08:32
yu-kinjoAny other comments?08:32
yuta-kazatoThanks for confirming documents, kinjo-san.08:33
yuta-kazatoI also understood that the enhanced tacker policy and your suggestion "Do not allow duplication of VNFD IDs within the same project, but allow duplication between different projects." is independent in this bug report.08:33
yu-kinjoThank you kazato-san. Yes. I think they are independent.08:34
yuta-kazatoThanks. I agree to your proposal.08:35
yu-kinjoThanks08:36
takahashi-tscThank you everyone, so currently there are no problem and it is ok to proceed with allow-VNFD-ID-duplication-among-different-tenants. 08:36
takahashi-tscIs it correct everyone? any other comments?08:36
yu-kinjoThank you. If there are no other comments, I would like to start the implementation for this bug report.08:37
takahashi-tscThanks! Of course, if any concerns are found, let's discuss it on IRC and Gerrit.08:38
yu-kinjoThank you for your coorporation!08:38
takahashi-tscI think that's all. And there is no agenda and we can close today's meeting.08:39
takahashi-tscAny others?08:39
uehaNothing from my side08:40
takahashi-tscGood, so let's close the meeting. Thank you! bye08:40
yuta-kazatobye!08:41
uehathanks, bye!08:41
manpreetk_Thanks, Bye!08:41
yu-kinjobye!08:41
ma-ooyamabye08:41
takahashi-tsc#endmeeting08:41
opendevmeetMeeting ended Tue Apr 18 08:41:19 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:41
opendevmeetMinutes:        https://meetings.opendev.org/meetings/tacker/2023/tacker.2023-04-18-08.09.html08:41
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/tacker/2023/tacker.2023-04-18-08.09.txt08:41
opendevmeetLog:            https://meetings.opendev.org/meetings/tacker/2023/tacker.2023-04-18-08.09.log.html08:41

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