08:02:55 #startmeeting tacker 08:02:56 Meeting started Tue Feb 18 08:02:55 2020 UTC and is due to finish in 60 minutes. The chair is joxyuki. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:02:57 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:03:00 The meeting name has been set to 'tacker' 08:03:08 #topic Roll call 08:04:54 hello 08:05:03 hi keiko-k 08:07:27 Hi 08:07:45 keiko-k 08:07:48 and Jo 08:07:53 hello 08:07:58 hi 08:09:29 let's start. 08:09:48 #topic spec 08:10:17 https://review.opendev.org/#/c/591866/ 08:10:38 it almost looks good. I can put +2. 08:11:10 I can put +2 soon after this meeting. 08:11:44 and series of implementation patches are being uploaded. 08:12:54 Thanks 08:13:11 I will start to review them except WIP patches. 08:13:49 next,,, 08:14:21 hyunsikyang, do you have anything to talk about your patches? 08:14:35 hi, takahashi-tsc 08:14:35 https://review.opendev.org/#/c/674761/ 08:14:45 I replied your comment. 08:14:46 Hello, sorry for late. 08:14:55 Please see check it again. 08:15:12 IMO, now tacker doesn't have testing for C-VNf. 08:15:31 ANYWAY, Please see my comment. 08:15:48 I hope this pathck will merge at this stage. 08:17:48 ok, I will check it. 08:18:08 thanks 08:18:27 I think we can remain tests for kubernetes driver for future work. 08:18:59 YES. It also good Idea 08:19:53 next, 08:19:58 In this round, I want to merge two patches.. and staring another one:) 08:20:48 noted. 08:20:59 https://review.opendev.org/#/c/700167/ 08:21:15 takahashi-tsc, do you have anythink to talk about your spec? 08:23:03 I think remaining topic is "constraint", I'm checking my spec and existing code of "Alarming". 08:25:10 yeah, parameters under "condition" are not clear for me also. 08:25:21 I reply the comment later. In my understanding, "constraint" in Alarming definition is just description, and actual constraint should defined as other attributes. 08:25:24 https://github.com/openstack/heat-translator/blob/2ceec3b348bb034935284033bde3c3be51f54651/translator/hot/tosca/tosca_policies_monitoring.py#L67 08:26:07 I will consider the definition of event alarm based on the above. 08:27:23 umm..., it looks bit strange. 08:28:30 But if you think that code is feasible, I don't care about it anymore. 08:28:31 I agree... I think we should also change current metric alarming definition... 08:28:58 ok 08:30:27 next https://review.opendev.org/#/c/696819/ 08:31:11 PTL already put +2. If you have a time, please review it. Any comments and queries are welcome. 08:31:56 next... 08:32:02 #topic python3 08:32:09 https://review.opendev.org/#/c/703579/ 08:32:40 Tomi reported a trouble on installing tacker-horizon on python3. 08:32:52 Yes. I got same error. 08:33:20 As you can see discussions on the patch, work around for this problems is changing /usr/bin/python simlink to python3. 08:33:47 please be aware of this work around. 08:33:50 yes. It also one of the solution. 08:35:31 hyunsikyang, do you think we should merge this patch instead of changing the simlink? 08:36:39 umm... I think this patch can solve this problem temporary... 08:38:04 Now in master 08:38:21 version, 08:38:30 python3 is default. 08:39:05 So, It make a pytone3 env when it install... but only this manage.py make a error. 08:39:34 Yes, we only support python3 so we can merge it. 08:39:35 IMO, There is another bug. 08:41:53 What bug? 08:42:22 Just Guess 08:42:38 Bucause only mange.py make a error. 08:43:00 If you are ok, I think it needs for current error.:) 08:44:19 Actually I got the same error caused by script in neutron during devstack installation. 08:45:36 is it also python3 problem? 08:45:53 Yes. Regarding these errors, it depends on your python2 environment whether errors occur of not. 08:46:10 s/of/or/ 08:47:09 If your python2 environemnt satisfies requirements of an script, you won't get a error. 08:48:47 So, what I am saying is that we may get these errors dpending on python2 environemnt even if we merge the patch. 08:49:47 To solve this, all shebang, including other project, need to be changed to python3 from python. 08:50:36 This is why I recommend the work around for now. 08:51:54 I don't know what project use pythone2 until now... , but if we think that pythone3 is default, it is now problem even we change shebang of the manage.py. 08:52:09 Can we test it again with this patch? 08:52:53 and it doesn't make a error, we can use it workaround solution. What do u think? 08:54:09 or just abandon it and change the link.. now chaos of version of python.kkk 08:55:37 what do you mean "we can use it workaroud solution"? 08:56:10 this patch if it doesn't make a error. 08:58:06 I think we should abondone this patch for now. But if the all community starts to change shebang, I will re-open it. 08:58:18 Okie:) 08:58:28 thank your for your concern! 08:58:38 not at all. 08:59:05 time is running out. close the meeting. thanks team! 08:59:10 Thanks 08:59:13 see you:) 08:59:22 #endmeeting