04:00:13 #startmeeting Masakari 04:00:14 Meeting started Tue Mar 24 04:00:13 2020 UTC and is due to finish in 60 minutes. The chair is tpatil. Information about MeetBot at http://wiki.debian.org/MeetBot. 04:00:15 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 04:00:18 The meeting name has been set to 'masakari' 04:00:26 Roll Call 04:01:24 #topic: Roll Call 04:07:30 Note to everyone: If you want your patches to get merge in U release, please add the list of patches in etherpad below: 04:07:39 #link : https://etherpad.openstack.org/p/masakari-u-workitems 04:10:30 GM Tushar san, sorry for delay 04:10:42 shilpasd: Hi 04:11:20 shilpasd: Do you have any patches for review? 04:12:03 if yes, please add them in https://etherpad.openstack.org/p/masakari-u-workitems 04:13:55 sorry some connection issue at my end 04:14:06 okay will list into etherpad 04:14:12 shilpasd47: No problem. 04:15:21 I will prioritize the patches that should be merged in U release and spend some time reviewing those accordingly 04:15:56 tpatil: okay, thank you 04:16:16 shilpasd47: Do you have any points for discussion? If no, let's end this meeting early as no one else has joined this time. 04:16:32 just one query, https://review.opendev.org/#/c/704811/, here we are waiting for the approach to finalize 04:16:41 patch is related to 'Add new filter `host_name` to segment list' 04:17:12 I have discussed this point in the last meeting and awaiting Sampath san to reply back. 04:17:28 okay my miss, thank you 04:17:28 there are two choices 04:17:37 1. Go ahead with the changes you have proposed 04:18:00 2. introduce a new Rest API ``GET /hosts`` 04:18:10 sorry for late. 04:18:20 suzhengwei__: Hi 04:18:29 hi 04:19:14 suzhengwei__: Hi 04:19:17 #topic: Critical Bugs 04:19:57 #link : https://bugs.launchpad.net/masakari/+bug/1858762 04:19:58 Launchpad bug 1858762 in masakari "“UNKNOWN” host_status notification may cause unsafe evacuation" [Critical,Confirmed] - Assigned to Shilpa Devharakar (shilpasd) 04:20:20 shilpasd47: Do you have any update about this bug? 04:20:21 will push changes today to community for this 04:20:29 shilpasd47: Ok 04:20:57 Any other bugs you want to discuss here? 04:21:06 tpatil: no 04:21:29 https://review.opendev.org/#/c/702328/ 04:22:11 tpatil: woud you like to give a review o this simple patch? 04:22:48 suzhengwei__: Sure, I will review it 04:22:59 thanks 04:23:18 In the beginning of this meeting, I have added a note asking people to add patches that they want to see in U release. 04:23:52 suzhengwei__: Could you please add the patches to want to see land in U release in below etherpad: 04:24:06 ok 04:24:09 #link : https://etherpad.openstack.org/p/masakari-u-workitems 04:25:10 suzhengwei__: The above patch looks simple but it's missing unit tests. Can you please add unit tests for your changes? 04:26:19 I will. My own CI workflow is broken, I need to fix it first. 04:27:40 suzhengwei__: Ok, No problem 04:27:58 Moving to the next topic 04:28:11 #topic Work Items for Ussuri 04:28:53 suzhengwei__: I forgot to mention about patch : https://review.opendev.org/#/c/708325/ 04:29:23 suzhengwei__: Changes looks good. Need unit tests so that we can merge it patch soon 04:30:06 ok, i will add unit tests later. 04:31:34 suzhengwei__: Ok, Thanks 04:32:02 Enable/Disable evacuation segment wise 04:32:24 specs: https://review.opendev.org/#/c/705893/ 04:33:08 tpatil: there are few review comments by Toshikazu Kazu Ichikawa, will address and push the updated path, further please review 04:33:16 Still I need to review the updated specs, sorry the delay 04:34:02 tpatil: i know your are super busy, so pl no sorry 04:34:28 shilpasd47: This is different spec I'm talking about 04:34:39 proposed by suzhengwei__ 04:34:57 tpatil: okay, we switched... 04:35:34 sorry, i got confused 04:36:00 suzhengwei__: I will this specs soon 04:36:10 thx 04:36:21 I have update code for this spec, but because my own ci workflow, it still failed. 04:37:10 suzhengwei__: Ok, Got it. I will see that this spec and implementation gets merged in U release. 04:37:26 function test is rely on openstackSDK, so function test will be add in next V branch. 04:38:39 suzhengwei__: Only rest API will go in this cycle and you plan to work on OpenStackSDK in next cycle, is it correct? 04:38:54 yes. 04:39:34 not enough time left for U release. 04:40:28 suzhengwei__: Ok 04:41:56 Next work item: Evacuate non-recovery (`HA_enabled = False`) instances 04:42:04 Specs: https://review.opendev.org/#/c/702427/ 04:42:50 shilpasd47: Any update? 04:42:57 tpatil: i want your review on this 04:43:12 there are few comments, will address by today 04:43:41 shilpasd47: Ok, Thanks 04:44:18 shilpasd47: I will review this specs as well. But are you ready with the implementation? 04:44:38 tpatil: yes 04:45:14 shilpasd47: Have you already uploaded the patch? 04:45:57 tpatil: on CG, not yet, should i push? 04:46:13 since pec is under review i haven't pushed to CG yet 04:46:20 spec* 04:46:45 shilpasd47: Yes, you can push the implementation patch on the CG 04:47:07 tpatil: okay will push today 04:47:18 shilpasd47: Thanks 04:47:35 Modify masakari-hostmonitor in order to run it inside container 04:47:53 shilpasd47: Any update? 04:48:20 tpatil: here using 'crm' commands to check status for corosync/pacemaker 04:48:39 but 'crm' itself uses systemctl internally to verify the same 04:48:52 so my query, will crm commands will work inside docker? 04:49:10 Where did you find out this information? 04:49:30 that crm-> uses systemctl? 04:49:56 tpatil: https://github.com/ClusterLabs/crmsh/blob/master/crmsh/utils.py#L1796 04:51:37 That's important finding. If that's the case, there is no point of making this change. Let me discuss this issue with Sampath san and get back to you 04:51:38 i have gone through this repository and observed that crm uses systemctl, correct me if i am wrong 04:51:50 tpatil: thank you 04:52:08 Command parameter support to segment list command to filter out segments based on host input parameter 04:52:25 shilpasd47: We have already discussed about this work item. 04:52:38 tpatil: yes 04:53:07 tpatil: since approach 2 is not yet finalized, should i focus on implementation for this option? 04:54:09 shilpasd: Your call. I will discuss this point with Sampath san and get back to you. 04:54:22 tpatil: okay 04:54:29 tpatil: one more finding regarding 'Modify masakari-hostmonitor in order to run it inside container' 04:55:05 here 'crm status list', this command i was looking for finding status of corosync and pacemaker 04:55:35 but if we want status of 'pacemaker-remote', as of now 'crm' doesn't have support for this 04:56:26 https://github.com/ClusterLabs/crmsh/blob/master/crmsh/ui_cluster.py#L602 04:56:55 if check here, 'crm status list' only list status for corosync and pacemaker services. 04:56:58 shilpasd: I will need time to look into this. 04:57:40 tpatil: yup, just findings i have shared here 04:58:14 shilpasd47: Understood, thanks. If it's a blocker and cannot be done in U release, you can implement it in the next cycle 04:58:20 running out of time. 04:58:36 We have finished discussion on work items planned for U release 04:58:49 Any other points left for discussion? 04:59:36 tpatil: ok, thanks 04:59:43 Let's end this meeting here 04:59:48 Thank you, All 04:59:50 thats all from my side, will add list of patches that needs to be review 04:59:54 thank you 05:00:05 shilpasd47: Thanks 05:00:09 #endmeeting