08:05:46 #startmeeting tacker 08:05:47 Meeting started Tue Feb 2 08:05:46 2021 UTC and is due to finish in 60 minutes. The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:05:48 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:05:50 The meeting name has been set to 'tacker' 08:07:14 There is no topic today on our etherpad 08:07:49 Do you have anything to discuss? 08:08:37 I have 1 topic to discuss, would like to hear opinions from you, could I go on? 08:09:30 please go ahead 08:09:44 https://etherpad.opendev.org/p/tacker-meeting#286 08:10:28 sorry for write on Etherpad late.. This is a topic about Backward compatibility for patch https://review.opendev.org/c/openstack/tacker/+/768091 08:11:51 in this patch we are trying to refactoring legacy action-driver code, to support SOL-001 based VNFLCM interfaces 08:12:39 also we are trying to make sure user are using tacker's mgmt-driver(like kubernetes.py) in their package, by checking hash value. 08:14:00 however, this patch will also make legacy action types like ACTION_SCALE_IN_VNF not run anymore since wo changed mgmt calling method in vnflcm_driver 08:15:57 this makes incompletely backward compatibility.. And here what I want to discuss is, should this change keep legacy actions support? 08:19:45 my opinions are: 1. we should or we are excepted to support SOL-001 based interfaces, 2. It is not a long time since legacy code released(in Victoria), so maybe it is a good timing to do a complete refactoring now. 08:20:09 that's all 08:22:18 I understand the point is; The scale operation in SOL-implementation calls legacy-MgmtDriver. This will be refactored to call your new MgmtDriver for SOL. 08:23:16 I remember we discussed the design of new MgmtDriver for SOL-implementation in the previous PTG, and my opinion was to create completely new one. 08:23:42 Because the methods for new MgmtDriver are different from legacy. 08:23:59 So I agree. 08:24:20 https://etherpad.opendev.org/p/Tacker-PTG-Wallaby 08:24:32 L183 08:25:45 takahashi-tsc is not here today? 08:26:39 thanks for opinion! 08:28:03 takahashi-tsc is attending another meeting. 08:30:22 I am not opposite to your proposal 08:30:47 Hi, sorry for very late... 08:30:49 but you should revise your patch 08:30:52 hi 08:31:05 hi takahashi-san 08:31:43 please find https://etherpad.opendev.org/p/tacker-meeting#286 08:32:53 Thanks, I read meeting log and understand that we are talking about Mgmt Driver. 08:35:43 do you have any comments? 08:39:18 I remember that our conclusion in PTG is to create new one for SOL. In my opinion, it is better to divide. 08:43:22 LiangLu: What do you think? 08:46:04 thanks for opinion, I think we don't need to fix patch to support legacy interfaces(is already modified in current patch) 08:46:35 and also may I ask what else should we revise for patch? 08:47:24 You are proposing this topic because Itsuro suggested to discuss here, right? 08:47:53 If so, you should add an explanation in docs or so as he advised at least. 08:48:36 In addition, you do not make clear about backward compatibility 08:49:03 keep the legacy one, or discard, or so... 08:49:32 I do not understand your point discussed from your current patch actually 08:50:29 Itsuro also suggested to make a decision at this IRC meeting. I agree with him. 08:54:13 thanks for suggestion, my opinion is to discard legacy codes, I will add this part to docs/commit message 08:56:07 takahashi-tsc: I am not sure about your comment, “it is better to divide”. It means the same as LiangLu? 08:58:16 Sorry for ambiguous, I said just to create new MgmtDriver feature for SOL. And "Discard legacy or not" seems another discussion 09:00:47 thanks 09:01:50 In my opinion, we should not discard legacy suddenly(e.g. W-release), so we should make some docs to explain. 09:02:07 And separately, we discuss and decide the strategy about legacy code. 09:02:17 Let me correct the point of discussion 09:03:21 LiangLu doesn't propose discarding of Legacy Mgmt-Driver 09:03:56 He is just trying to drop the unintentional logic of calling legacy-MgmtDriver in the SOL scale operation. 09:05:32 As we discussed in PTG, we agreed to have different MgmtDrivers for legacy and SOL. But we found that the scale operation supported in V-release has a logic calling legacy MgmtDriver. 09:05:36 thanks for explanation! 09:06:13 I'm not sure why that is there, but the point is that I think we can drop the unintentional logic related to legacy MgmtDriver in SOL scale operation. 09:07:08 Understood... I agree with LiangLu SOL operation should not call legacy-MgmtDriver. 09:09:21 sorry for make things ambiguous, the conflict part(sol/legacy) is in vnflcm, calling scale operation, in the patch we are modifying to call SOL operation 09:10:41 I am still not sure about “3rd-party drivers” discussed while reviewing. 09:11:14 Is it not included in your scope of the change actually? 09:17:11 anyway, we don’t have time today. 09:17:48 should we continue discuss on patch reviews? 09:17:55 LiangLu: please continue on gerrit if you have no comment now 09:18:16 or make it clear shortly if possible 09:19:39 I think it is better to continue in reviews 09:19:59 OK, thanks 09:20:01 sorry for taking long time.. 09:20:27 I would like to ask you to update your patch first. 09:20:37 Thanks everyone 09:20:49 I would like to close this meeting 09:20:52 bye 09:20:55 bye 09:21:01 bye 09:21:04 thanks 09:21:08 #endmeeting