08:04:15 #startmeeting tacker 08:04:15 Meeting started Tue Dec 22 08:04:15 2020 UTC and is due to finish in 60 minutes. The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:04:16 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:04:19 The meeting name has been set to 'tacker' 08:05:32 I have no topics today 08:06:32 I have 2 topics, not so big. 08:08:17 OK, go ahead please 08:09:11 First is about adding separated FT. Sorry for the late.. But I found 1 issue. 08:09:22 See Etherpad https://etherpad.opendev.org/p/tacker-meeting 08:09:30 L595 08:09:49 We cannot change tacker config in current Tacker FT, because gawk is not installed in controler-tacker node. 08:10:24 So I'll make some workaround, but I think we should report to devstack team. 08:11:33 This is just infromation... But I think it is important information because other member is also considering add new FT set. 08:12:46 understand 08:13:17 Any comments or questions? 08:14:30 seems good, please go to next 08:14:53 OK, next is about DB refactoring. ehterpad L603- 08:15:28 NEC already post patch and someone added comments. very thanks! 08:16:07 But DB changing is big decision. So I want Tacker members comment about big direction. 08:17:49 I already added 1 discussion in NEC L617-. Not use DB and get information using API. As a result, we think it is difficult. 08:19:41 I want such discussion points or other suggestions. 08:20:57 It's also OK after this meeting. 08:21:15 Can you share the url of the patch? 08:21:39 on etherpad one? 08:21:44 https://review.opendev.org/c/openstack/tacker/+/763955 08:21:55 Etherpad L603 08:22:00 thx 08:24:16 Takahashi-san, I have one question. This `class VnfInfo` on etherpad seems to specialize for Openstack data. Does not use this DB in kubernetes infra driver? 08:27:49 I see... it is good point. We should consider design of whole VNF data... 08:32:46 Having OpenStack-specific data may be fine, but in the end it's necessary to consider other VIM types as well. 08:33:30 Yes.. I think we should know how use this DB and to think commonization for other vims. It is difficult.. 08:35:46 OK, I write your comment on etherpad... I'll discuss it. 08:37:49 OK. thanks. I'll check patch for knowing details of DB refactoring! 08:42:42 Sorry, I'm late. I've checked the log. 08:45:36 sorry for leaving for disconnection 08:45:36 For DB refactoring, I'm concerning that we cannot follow what attributes are stored in DB in the existing implementation. 08:46:48 Especially for VNFAttribute table, I believe no one can understand what is stored in there. That's why it's also difficult to review the patch. 08:51:35 Do you mean... e.g. we need information about whole data structure in Tacker. and its before & after? 08:55:00 I mean reviewers need to understand the mapping between the existing implementation and the refactor patch, but it's difficult for us to understand the existing implementaion because they has a big dict variable. It takes long time to review the patch. 08:56:24 And as you mentioned, the data structure help us to understand what this patch tries to refactor. 08:57:47 We are running out the time today, so I'll try to put my concern on the etherpad. 08:58:08 I see... at least we need mapping between before and after. And data structure seems needed too. 08:58:09 Thanks! 09:02:25 takahashi-tsc: do we need to have more discussion in the next meeting? 09:03:55 Seems needed... but is it 3 weeks later? 09:06:53 Or we can have a meeting anytime on our channel 09:08:00 OK... anyway, we'll update etherpad or the patch if necessary. If you write comments on etherpad or tacker channel, I'll reply. 09:09:10 OK, please join the discussion who are interested 09:09:33 I would like to close this meeting if no more comments 09:11:02 OK, thanks. 09:11:17 Thanks, bye 09:11:23 The next meeting is at 12 Jan, 2020. 09:11:32 bye 09:11:44 #endmeeting