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