04:00:01 #startmeeting masakari 04:00:02 Meeting started Tue Oct 10 04:00:01 2017 UTC and is due to finish in 60 minutes. The chair is samP. Information about MeetBot at http://wiki.debian.org/MeetBot. 04:00:03 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 04:00:05 The meeting name has been set to 'masakari' 04:00:06 tpatil: hi 04:00:22 o/ 04:00:25 sorry, didn't have time to update the agenda in wiki 04:00:34 abhishekk: hi 04:00:43 #topic bugs 04:00:43 hi 04:00:45 samP: hi 04:00:49 rkmrHonjo: hi 04:00:59 Any bugs to discuss? 04:01:16 #link https://bugs.launchpad.net/masakari/+bug/1721742 04:01:18 Launchpad bug 1721742 in masakari "Masakari will fail to recovery instances on failure host if instance's task_state is not none" [Undecided,New] - Assigned to takahara.kengo (takahara.kengo) 04:02:09 rkmrHonjo: thanks 04:02:13 Takahara reported that bug. And, he plan to reset task_state by reset state API. 04:02:41 rkmrHonjo: can you reset the task_state? 04:03:10 i guess no 04:03:18 abhishekk: same here 04:03:29 Hi 04:03:35 I think you only can reset the vm_state to active or error 04:03:39 sagara: Hi 04:03:40 you can only reset vm_state 04:03:47 samP: right 04:04:13 samp: Will reset state API change task_state to None? 04:04:46 it reset task state to None 04:04:55 rkmrHonjo: does it? Im not sure. could you please try that out and post your findings in LP bug report? 04:05:27 tpatil: OK, then it would be possible 04:05:39 I have checked the code, it reset vm_state to whatever is passed to the API and task_state to None 04:05:52 tpatil: thanks. Just in case, I re-confirm reset-state API spec and write it on LP. 04:06:05 tpatil: rkmrHonjo: thanks 04:07:59 let's wait for the patch. Please make sure that you will not break the other logic 04:08:15 samP: Sure. 04:08:18 any other bugs to discuss? 04:09:16 if any, please bring them in AOB at the end 04:09:24 #topic Discussion points 04:09:40 (1) Application for become OpenStack official project 04:10:30 TC will approve the application today or tomorrow. Congratulations team... 04:11:04 Cheers! 04:11:10 Thierry's comment "Majority reached, to be approved on Oct 10 unless new objections are posted" 04:11:14 Congratulations 04:11:19 Great! 04:11:34 (2) Install guide document 04:12:03 Need to review this..I will find some time to review those in this week. Really sorry for the delay 04:12:28 (3) Recovery method customization 04:12:29 I guess, you can review it once openstack doc theme is applied 04:13:26 abhishekk: Earlier, you had uploaded guide docs using openstack doc theme, correct? 04:13:41 tpatil: yes 04:14:21 after that I have added few things as a review comments given by rkmrHonjo san 04:14:21 abhishekk: ok, so it's easy to revert them back, right? 04:14:36 so Once we revert it I need to add those changes again 04:14:46 abhishekk: ok, I got it. 04:16:36 abhishekk: Hopefully, from tomorrow, we can use the theme. If you have time, please revert it and fix the theme 04:17:25 samP: yes 04:17:29 abhishekk: thanks 04:17:45 (3) Recovery method customization 04:17:54 Any update on this? 04:18:04 samP: Need to update specs 04:18:58 samP: we have plan to add action python package in masakari repo and in setup.py, we will create a separate lib which operator will need to install it on mistral executor nodes 04:18:59 tpatil: Understand. I will review again once update done 04:19:17 samP: Ok, Thanks 04:20:35 tpatil: Understand about the new package, please details of your plan in spec. let's discuss where is the best place for this package 04:20:55 samP: Sure 04:21:01 tpatil: thanks 04:21:17 (4) Find hosts without specifying segments 04:21:45 I guess, we have to review this, right? 04:21:49 Dinesh_Bhor: Thank you for reviewing. 04:21:55 samP: yes. Please. 04:22:14 rkmrHonjo: np 04:22:26 rkmrHonjo: I will do it, and again sorry for the delay 04:22:34 samP: No problem. 04:22:46 (5) Queens Work Items 04:23:30 We already currently active items. Any other items need to discuss? 04:24:12 Yes, we are planning to add masakari horizon plugin 04:24:25 samP: Should we run masakari in python3? 04:24:38 tpatil: great. have you start it? 04:25:06 We have understood horizon code and implemented POC for certain screens 04:25:30 Who will create masakari horizon plugin repo in GitHub? 04:25:58 rkmrHonjo: please wait 04:26:03 sorry 04:26:13 I will ask Niraj to add a new BP masakari horizon plugin 04:26:37 tpatil: Any one can propose it. However, now we are official, we need to add it to TC project list under masakari 04:27:30 samP: ok, I will check the documentation and will do the needful 04:28:02 tpatil: thanks, please let me know if anything unclear 04:28:25 rkmrHonjo: sorry to keep you on hold 04:28:26 samP: sure 04:28:34 rkmrHonjo: about python 3 04:28:56 samP: yes. 04:29:16 rkmrHonjo: Masakari already supports python 3 04:29:22 samP, rkmrHonjo: All masakari projects are python 3.5 compatible 04:29:29 I think we dont have any known problem with python 3, and we have py3 jobs running in gate 04:29:53 Dinesh_Bhor: thanks 04:30:03 tpatil: Dinesh_Bhor: Ok. 04:31:19 sorry, I haven't grasped about python3 compatibility. 04:31:41 rkmrHonjo: above that answered to your question? 04:31:49 samP: yes. 04:31:56 rkmrHonjo: ok then. 04:32:14 (6) BM HA (ironic + nova) 04:32:24 No progress.. 04:32:44 (7) OpenStack Proposal Bot updates 04:33:12 We have long queue of updates from BOT. 04:34:03 I would like to decide a policy for this.. 04:34:54 By the way, UT codes should be fixed according to new oslo.context.(Please see Patch set 89) 04:34:54 Do you think its better to review and merge each patch as it comes, or do it once on time to time 04:34:59 So I'll submit other patch to fix it after that. 04:35:15 oh, sorry 04:35:20 rkmrHonjo: thanks, I have seen that 04:35:20 rkmrHonjo: its ok 04:36:20 samP: And, I agree to your opinion "I would like to decide a policy for this" 04:37:53 I think bot options are OK, I will check and merge proposal bot updates currently pending. 04:38:38 samP: No objections. 04:38:45 Presently, Jenkins jobs are failing 04:39:03 For bot updates in future, we could do it single handedly, any objections? 04:39:11 tpatil: Yes. So I submit a patch to fix UT code after that. 04:39:12 tpatil: thaz zuul3 right? 04:40:01 samP: no 04:40:09 no objection 04:40:31 samP: At the bottom, it giving error for Zulu 04:40:31 samP: No, jenkins failures are caused by UT codes. 04:40:34 [Zuul] Job complete, result: FAILURE 04:41:00 tpatil: I think zuul -1 means zuul 3 fail, which is OK. I think Monty send a mail about this in ML 04:41:12 s/Zulu/zuul 04:41:12 samP: yes 04:41:15 tpatil: zuul or jenkins is zuul2 04:42:07 sorry, zuul and jenkins are run with zuul2 04:42:08 In Jenkins job, I see above error 04:43:22 tpatil: In this patch? https://review.openstack.org/#/c/452503/ 04:44:10 tpatil: I will check that.. 04:44:13 No, this one, https://review.openstack.org/#/c/477955/ 04:44:58 tpatil: This one failing because of UT 04:45:17 tpatil: Ah, yes.. someting wrong with this one. I will check that later 04:45:37 Dinesh_Bhor: got it. 04:45:41 Dinesh_Bhor: thanks.. 04:47:05 samP: I'm preparing to submit a patch to fix it. 04:47:13 rkmrHonjo: thanks 04:48:23 Anyway, for future bot updates, all core members feel free to approve and merge bot updates single handedly 04:48:50 If you are not sure, then please discuss with other.. 04:49:04 #topic AOB 04:49:12 samP: OK, after Jenkin job passes, I will approve and merge these patches 04:49:25 tpatil: thanks 04:49:37 I have already approved this patch, https://review.openstack.org/#/c/508419/, can you please review it? 04:50:10 tpatil: Ah, yes. thanks. I will look 04:51:19 tpatil: sorry, I was late for reviewing... 04:51:48 rkmrHonjo: np 04:52:02 Any other thins to discuss?, if not we could end today's meeting bit early 04:52:15 s/thins/things 04:52:53 no. 04:53:00 no 04:53:03 Nothing from my end for now 04:53:46 no 04:54:19 OK then, thanks you all. If you have any points to discuss, please use ML with [masakari], or use our IRC channel #openstack-masakari 04:54:30 bye 04:54:39 bye 04:54:43 let's end for today 04:54:49 #endmeeting