04:00:43 #startmeeting masakari 04:00:44 Meeting started Tue Jul 25 04:00:43 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:45 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 04:00:47 The meeting name has been set to 'masakari' 04:00:55 lets start Masakari meeting.. 04:01:05 Hi 04:01:17 sagara: abhishek_k: hi 04:01:31 hi samP 04:01:35 Lets start with Bugs 04:01:42 Tushar san will be 10 minutes late 04:01:45 #topic Critical Bugs 04:01:55 any bugs to discuss? 04:02:46 let me check quickly 04:03:14 If not let's jump in to Discussion. if any, you may address them in AOB later.. 04:03:16 abhishek_k: thanks 04:03:35 nothing sampath san 04:03:38 #link https://bugs.launchpad.net/masakari/+bug/1697629 This is not critical but improtant to fix. I have fix uploaded for it. 04:03:38 Launchpad bug 1697629 in masakari "Should not delete host of another segment" [Undecided,In progress] - Assigned to Dinesh Bhor (dinesh-bhor) 04:04:21 Dinesh_Bhor_: thanks.. 04:04:46 Dinesh_Bhor_: I will review this. thanks 04:04:56 samP: thanks 04:05:15 #topic Discussion points 04:05:37 (1) Application for become OpenStack official project 04:06:08 I would like to propose masakari to become official OpenStack project 04:06:40 I discussed this with Terry in OpenStack Days Tokyo in 7/20-21 04:07:19 great news 04:07:20 Thierry? 04:07:38 I will send a mail to openstack-dev ML and propose this to community. And send submit the patch to openstack governance repo 04:08:11 rkmrHonjo: sorry, mistake s/Terry/Thierry 04:08:40 if anyone have any objections or comments, please raise now.. 04:09:28 No objection. 04:09:48 I will share the patch before I submit it to governance, you will have another chance to put your comments. 04:09:50 no objections, I agree to propose that 04:09:52 Great news, no objections 04:10:33 OK then, I will proceed. feel free to raise your comments any time on this.. 04:10:35 Thanks 04:10:50 (2) Install guide document 04:11:00 I participated in OpenStackDays Tokyo in 7/20-21. 04:11:11 In the event, some people said that they didn't know how to install masakari. 04:11:24 So I thought that current install procedure in README.rst is not kind enough. I'd like to improve it. 04:11:32 Does anyone do the same now? 04:11:37 rkmrHonjo: thanks for the great presentation...\o/ 04:11:46 samP: thanks. 04:12:32 rkmrHonjo: README.rst was a quick work done by abhishek_k (if Im remember correctly..) 04:12:40 abhishek is writing a doc 04:13:02 samP:right 04:13:04 sagara: is that the API ref? 04:13:09 abhishek_k: ^^ 04:13:18 abhishek_k: Are you writing install document now? 04:13:23 samP: yes 04:13:32 rkmrHonjo: yes 04:13:57 OK then, if abhishek_k is not working on install docs, then we can split the work with rkmrHonjo 04:14:13 We should start writing installation guide for Ubuntu in the beginning 04:14:29 tpatil: agree 04:14:46 samP: I am working on the same, and have some work done 04:15:37 Quick question: should we also add information of how masakari-monitor will detect node failures? 04:15:38 abhishek_k: ok. Will you write about monitor? 04:15:47 abhishek_k: Thanks. Is there are any part you wants to split? or is it almost done? 04:15:58 abhishek_k: could you write gerrit address here? 04:16:13 rkmrHonjo: you can procced with monitors 04:16:29 sagara: its not on community gerrit yet 04:16:49 samP: I have covered related to masakari only 04:17:03 abhishek_k: great..thanks 04:17:26 abhishek_k: OK. I'll write about masakari-monitors installation. 04:17:45 rkmrHonjo: thanks 04:17:53 OK, then, rkmrHonjo can proceed with discriminators 04:18:10 rkmrHonjo: abhishek_k: Thank you.. 04:18:39 (3) Make nova "on_shared_storage" option configurable for evacuate API 04:19:22 Patches are on gerrit for masakari side solution. 04:20:12 We discussed about Jay's proposal last week. Any progress on that? 04:21:14 I have verified the solution Jay has suggested but it looks like it will not solve our problem: http://lists.openstack.org/pipermail/openstack-operators/2017-July/013967.html 04:22:06 the main issue is resize revert won't work if the destination compute node is down 04:22:29 destination compute node is the node on which the instance is resized 04:22:52 and when this node is down, masakari will get notification to rescue the instances 04:24:07 Dinesh has already replied to his proposal on the mailing list 04:24:23 Dinesh: is there any update post your reply? 04:24:30 not yet 04:24:34 No not yet 04:24:36 Dinesh_Bhor_: tpatil: Thank you.. 04:24:58 Let's watch the progress on ML 04:26:12 and let's proceed with our temporary solution in masakari side for this.. 04:26:52 samP: Dinesh has already proposed that patch 04:27:11 tpatil: Dinesh_Bhor_: thanks 04:27:17 #link: https://review.openstack.org/#/c/469029/ 04:27:42 Let's review that and merge. 04:27:58 samP: Sure 04:28:15 samP: ok. 04:28:24 (4) Evacuates partially resized VMs 04:29:01 Is this related to previous topic or new one? 04:29:38 samP: Its related to above topic 04:29:59 ah.. my mistake.. 04:30:04 abhishek_k: you are correct 04:30:10 let's move to next topic 04:30:22 (5) Remove ERROR instances from recovery targets when host failure happen 04:30:45 I sent my opinion about this topic to ML. 04:30:55 rkmrHonjo: I forget to replay that... sorry.. 04:31:10 samP: No problem. Please send your opinions to ML or this meeting. 04:31:31 rkmrHonjo: sure. 04:31:36 thanks. 04:31:49 (6) Recovery method customization 04:32:25 I think we need to discuss with Mistral team with this.. 04:33:04 Mistral already support Restful api to register new actions, but it requires operator to restart mistral services to get these newly action into effect 04:33:16 samP: we are working on a POC to register mistral actions on the fly 04:33:35 abhishek_k: great.. 04:34:02 Dinesh_Bhor has more update about it 04:34:10 is better to discuss this with Mistral team before propose those changes? 04:34:19 s/is/is it/ 04:34:41 Dinesh: Is it possible to check if a particular action is already registered in Mistral? 04:35:09 tpatil: Yes it is possible 04:35:57 Dinesh: Ok, great 04:36:03 There was a similar requirement in triple-O like masakari to add custom actions 04:36:04 Do we need to unregister 04:36:13 Do we need to unregister or delete actions? 04:36:15 samP: the idea is masakari will register these new actions, based on the yams file configured by the operator, if the action is not registered, register it. Then execute the workflow based on the notification type. 04:36:15 They have adopted below approach: https://review.openstack.org/#/c/282366/30 04:36:25 for each notification type, there will be a workflow 04:37:08 we can unregister those custom actions 04:38:12 tpatil: got it. 04:38:14 Dinesh_Bhor: so we can add the action in masakari code itself 04:38:28 tpatil: yes 04:39:28 Dinesh_Bhor : Let's finish this POC and then Abhishek can update specs accordingly 04:39:38 sure.. 04:39:43 tpatil: ok 04:40:03 so there is no dependency on the mistral community ro add recovery action customization 04:40:17 s/ro/to 04:40:55 yes I think so 04:41:32 OK then. Please share the PoC and update the spec. I would like to process the spec 04:42:09 samP: Yes, we will take the POC forward and update you once it is done 04:42:20 Thanks. 04:42:53 If you wants to talk to Mistral team, please let me know. I will be there. 04:43:09 samP: sure, thanks 04:43:41 (7) Masakari Pike work items 04:44:09 Not much progress in other work items. 04:44:57 Ah, Notifying API, need to review this.. 04:45:42 samP: Notifying is not API, that is RPC, log, etc. I replied to you on gerrit. Please check it. 04:46:02 rkmrHonjo: sure.. I will recheck that 04:46:09 samP: thanks. 04:46:19 (8) masakari-manage db purge 04:46:59 specs to be reviewed 04:47:11 #link https://review.openstack.org/#/c/473379/ 04:47:14 # link : https://review.openstack.org/#/c/473379/ 04:47:29 I will recheck this and approve it.. sorry for the delay. 04:48:10 #topic AOB 04:48:24 Any other topics to discuss? 04:49:14 no. 04:49:37 I will be attending to Ops meetup in Mexico on 8/9-10 04:49:42 #link https://etherpad.openstack.org/p/MEX-ops-meetup 04:50:19 In L62, OpenStack Resiliency is proposed 04:50:57 This session is about HA in openstack. please put your comments or questions on this. 04:51:26 And OpenStackExtreme Testing in L-77 04:52:01 Main purpose of the sessions are, get the feedback from ops and share new features 04:52:13 samP:Could I put comments even if I don't participate in the meetup? 04:52:26 rkmrHonjo: sure. 04:52:34 samP: I see. 04:52:56 I just submitted one patch to deprecate the masakari_topic conf option. Please add your comments on the patch if you have any concerns on this: https://review.openstack.org/#/c/485119/ 04:53:29 Dinesh_Bhor: Sure. 04:53:35 Dinesh_Bhor: I will review this patch tpday 04:53:49 thanks 04:54:09 s/tpday/today 04:54:57 samP: one thing to ask to sampath san, should I proceed with adding python-masakariclient to global-requirements? 04:55:39 Dinesh_Bhor_: yes. I fixed the versions and you may proceed now. 04:55:48 samP: ok thanks 04:56:45 Dinesh_Bhor_: How about other projects? Are they not allowed to config RPC topics? 04:57:14 samP: yes, they have removed all such config options 04:57:27 Dinesh_Bhor_: got it. 04:57:43 I will review this. Thanks for the fix. 04:57:54 samP: thanks 04:58:11 If nothing else to discuss, lets finish the meeting. 04:58:42 Please use #openstack-masakari or openstack-dev ML with [masakari] for further discussions.. 04:58:51 Thank you all.. 04:58:56 thanks 04:59:02 thanks. 04:59:17 thanks all 04:59:30 #endmeeting