08:03:04 #startmeeting tacker 08:03:04 Meeting started Tue Nov 24 08:03:04 2020 UTC and is due to finish in 60 minutes. The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:03:05 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:03:07 The meeting name has been set to 'tacker' 08:03:57 hi 08:04:38 do you have any topic today? 08:04:57 I have 1 topic about heat-tranlator and tosca-parser. 08:05:03 I have checking our ether pad. 08:05:12 10th item? 08:05:30 #link https://etherpad.opendev.org/p/tacker-meeting 08:05:33 Yes, sorry i forget to write item in section 0. 08:05:48 no problem! 08:06:28 Is there no update in 9th item, right? 08:07:18 no update... POST_FAILURE occurred again but there is no progress now. 08:09:19 OK. I and VA linux have been working for fixing the issue, reducing log messages and so on. 08:09:39 I will share my update in the next meeting, or later possibly. 08:10:24 I have no topic for today, so please go ahead your topic, takahashi-san. 08:10:57 Sure 08:11:45 Please see etherpad L522- 08:11:45 #topic heat-translator-and-tosca-parser 08:12:55 I think tacker development need to update heat-translator and tosca-parser, but recent patches is not merged. 08:14:13 So i'd like to propose something to proceed with such community activities. I want to send email to openstack-discuss. 08:15:41 Discussion point is... 1. Is such propose needed? 2. If needed, is it OK that I say that tacker member becomes heat-translator/tosca-parser's reviewers? 08:16:54 In addtion, I want to propose that Tacker core team becomes heat-translator/tosca-parser core team, if possible. 08:17:34 L529 is another option(Move heat-translator/tosca-parser repository under Tacker if only Tacker use them.) But I think it is difficult... 08:18:51 Yes, I have already joined for reviewing and positive to become a core. 08:19:02 Thank you, takahashi-san. I agree with your two proposals. I really appreciate if heat-translator/tosca-parser become more active because they are always the bottleneck of the patches related to my specs. 08:21:31 If OK, I send email to openstack-discuss. I think this is discussion across projects, so [tc] tag is needed. [tc][heat][tacker] 08:21:51 +1 08:26:05 are there any objections? If no, I'd like to show 1 more discussion point(L530-) 08:26:35 seems nothing 08:27:47 OK, I think we need to discuss how to develop with heat-translator/tosca-parser. I think we cannot conclude because it depends on above discussion. But I want to start discussion. 08:28:57 Issue is current tacker's FT use pip package of heat-translator/tosca-parser. i.e. even if the patch is merged to master them, Tacker FT does not use updated code. 08:30:09 I want team's opinions. Do we need to make script to install master for FT? 08:30:25 install master of heat-translator/tosca-parser. 08:31:24 We can install pip packages localy from source, and I think it is doable on zuul env as a remedy. 08:32:04 Until required updates are merged in the pip package 08:33:59 Your ‘make a script’ means that you add installation script in our devstack script, right? 08:34:35 devstack or zuul setup playbook. 08:35:24 Of course, this is just example. Is there any other way? I'm not sure... 08:35:46 Before that, we should decide that FT should use pip package or master code. 08:37:59 I wrote pros/cons of using master code in etherpad L534. 08:38:20 IMO, it's better to use master code because our patches often depend on the new patch in heat-translator/tosca-parser. I don't want to wait till the new codes are introduced to pip repo. 08:39:24 I'm not sure how much risky to use master codes other than pip. 08:40:01 For me, it seems enough to simply change the Zuul or devstack to use master codes without any new FTs. 08:41:12 I think it is not so different between using master or pip repo. 08:42:14 My biggest concern is L538, "We may release the code which is not available due to not updating heat-translator/tosca-parser pip package." 08:43:27 I think it will happen very rarely, but it may happen. 08:45:46 We can customize the installation to use master repo while running pip installation. 08:47:25 So, I think it might not so serious issue actually. 08:49:52 Yes, I think there are not so serious issues. But I think we should decide our strategy and show to developers and users both 08:50:47 It should not be so long term issue, right? 08:51:09 I think so. 08:51:32 So, we do not need to care users, but only developers. 08:51:56 In my opinion, it just enough to update devstack installation. 08:52:54 for testing on devstack by developers, and passing CI on zuul. 08:53:46 OK, understood. 08:54:30 We also need to have a discussion with teams, tosca-parser and heat-translator, for getting control for merging our patches in parallel. 08:54:52 Thanks takahashi-san for leading the discussion. 08:55:06 Agree, thanks. 08:56:36 That's all from me. 08:58:07 Thanks. Please continue to discussion for details, especially for plans how to make agreement with them. 08:59:16 It is almost the end of time, but do yo have other topic, everyone? 08:59:25 Let me ask you to review my updated specs: 08:59:36 #link https://review.opendev.org/c/openstack/tacker-specs/+/759601 08:59:45 #link https://review.opendev.org/c/openstack/tacker-specs/+/759642 09:00:00 Also, my other specs are ready to review. Thanks. 09:01:00 That's all from me. 09:01:04 Thank you for your mention. 09:03:18 We have some more specs ready to be reviewed which proposed while vPTG. 09:03:41 Please join for the review. Thanks 09:04:18 I would like to close this meeting. Thank you for joining. 09:04:23 bye 09:04:27 Thanks. bye. 09:04:31 bye 09:04:48 #endmeeting tacker