04:01:33 #startmeeting Masakari 04:01:34 tpatil: thanks 04:01:35 Meeting started Tue Apr 3 04:01:33 2018 UTC and is due to finish in 60 minutes. The chair is tpatil. Information about MeetBot at http://wiki.debian.org/MeetBot. 04:01:36 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 04:01:38 The meeting name has been set to 'masakari' 04:02:23 #topic Bugs 04:03:22 Any new bugs reported in the last week? 04:04:47 #link https://review.openstack.org/#/c/546492/13 04:05:30 rkmrHonjo: does above patch works for all supported versions? 04:06:16 I mean openstacksdk versions 04:06:28 Ah, please wait... 04:08:43 Recently this patch https://review.openstack.org/#/c/555710/ is merged which adds instance_ha service support in openstacksdk 04:09:11 So we will need to remove the sdk code from masakariclient 04:09:26 Who will submit patch to remove that code? 04:09:54 tpatil: We can submit that patch. 04:10:01 s/We/I/ 04:10:24 rkmrHonjo: Thanks 04:10:35 #link https://review.openstack.org/#/c/557634/ 04:10:41 And, this patch: https://review.openstack.org/#/c/546492/13 works with openstack-sdk containing instance-ha code. 04:11:09 So we should wait to merge until releasing new version of openstack-sdk and bumping lower version of openstakc-sdk. 04:12:13 can you please add the required info in the commit message? 04:12:46 ok. I or Takahara will add it. 04:12:54 Thanks 04:14:03 rkmrHonjo: Going forward, masakari-dashboard should use openstacksdk to call masakari API instead of masakariclient, correct? 04:15:09 Probably right. But, sorry, I don't know about the detail of masakari-dashboard. 04:16:56 niraj_singh: have you tried applying this openstack instance_ha patch to test masakari-dashobard? 04:17:00 #link :https://review.openstack.org/#/c/555710/ 04:17:58 yes. but test cases still not wroking in my env. 04:18:31 should i need to create connection through openstacksdk now? 04:18:53 niraj_singh: Yes, of course 04:19:14 ok, i will try and let you know. 04:20:27 ok 04:21:05 #topic Discussion points 04:21:25 recovery method customization 04:21:30 No progress yet 04:21:54 Ansible support for Masakari 04:22:02 niraj_singh: Any updates? 04:22:05 masakari-api and masakari-engine are installed successfully. 04:22:36 Also uploaded patch specs patch for community review. https://review.openstack.org/#/c/556756/ 04:23:27 there is -1 on the specs, anything you need from our end to address their concerns 04:23:38 yes 04:24:40 My first concern about the role. can we create 2 roles for masakari and masakari-monitors? 04:25:14 niraj_singh: why do you need two roles? 04:26:33 beacause masakari and masakari-monitors are two different project. 04:27:03 And as per my reference understanding there is no role which implemented two role. 04:27:14 means two project 04:27:41 do you need to provide reference of the repo to download the code or release? can't it be done for two project in one role 04:28:28 yes i need to provide reference of the repo to download the code. 04:28:34 Are you facing any problems if you want to include both these projects in one role? 04:29:02 There is a significance of having two different roles I think. It depends on the "dependency" between those two projects. Need to check documentation. 04:29:21 yes.. i still dont know how it works with two project in single role. 04:31:10 niraj_singh: if it's possible to add everything in one role, I think it's great. but if there are any constraints design-wise then adding it in two roles should also work 04:31:26 but I request you to figure out if it can be done with any problems in a single role 04:31:34 without 04:31:45 ok. i will do it today. 04:31:58 Do you have any other concerns? 04:32:04 or questions? 04:32:11 yes about the test cases. 04:32:49 There is no tempest test case in masakari. 04:32:49 So ansible member suggested me to start by testing the API responses codes. 04:33:30 I gone through tacker role. They just checked is tacker api is rechable or not by checking the response code return after hitting the htts://localhost:{port} 04:33:53 ok, you can call versioning api to confirm this point 04:34:19 but how to confirm masakari-engine and masakari-monitors are installed properly? 04:35:26 i am working on it. 04:35:44 masakari-engine comes into picture only for processing notifications 04:35:56 Is there any suggession about it. 04:36:06 yes 04:36:39 niraj_singh: To test masakari-engine is process notification successfully, we need some mechanisms to shutdown nova-compute host 04:37:03 ok. 04:37:42 this way, you can confirm masakari-monitor and masakari-engine are installed properly and it's functioning as expected 04:37:56 ok 04:38:27 Moving ahead 04:38:41 Call Force down API when host-failure will be notified 04:38:50 rkmrHonjo: Any update? 04:39:38 Sorry, nothing. 04:39:53 ok 04:40:14 #topic Masakari Project mascot 04:40:37 I haven't heard anything from Sampath yet about the decision on mascot 04:41:58 Let's wait for Sampath reply 04:42:21 #topic Masakari Rocky Work Items 04:42:28 Run masakari api service using uwsgi 04:43:04 Most of the projects uses uwsgi, so we should also do the same 04:43:21 Can this be done without specs? 04:45:47 I don't think it requires specs. If no one has any objection, then I will propose code changes directly 04:46:19 Is any of the items in the Rocky etherpad not discussed here? 04:47:01 #link https://etherpad.openstack.org/p/masakari-rocky-work-items 04:47:35 Many of the items were discussed two weeks back 04:49:43 Ok, if you want to discuss any new features you are planning for Rocky, please bring it on in the next week meeting 04:50:20 we have 10 more mins remaining 04:50:35 Any questions? 04:51:10 tpatil:no 04:51:37 Nothing from my side. 04:52:09 Let's end this meeting. Thank all for participation 04:52:11 #endmeeting