04:01:24 #startmeeting masakari 04:01:25 Meeting started Tue May 16 04:01:24 2017 UTC and is due to finish in 60 minutes. The chair is samP. Information about MeetBot at http://wiki.debian.org/MeetBot. 04:01:26 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 04:01:28 The meeting name has been set to 'masakari' 04:01:33 sagara: hi.. 04:01:40 Hi 04:01:47 abhishekk: hi 04:02:28 samP: hi, how are you, how was the journey 04:02:37 right after the summit, mightn not have updates...anyway..lets start with bugs 04:03:03 abhishekk: still jetlag... too sleepy in daytime :) 04:03:14 samP: same here :) 04:04:04 abhishekk: I hate to travel with time diffs... next time would be better..its AUS 04:04:19 #topic critical bugs 04:04:41 samP: yes, but PTG will be in US again 04:04:48 #link https://bugs.launchpad.net/masakari/+bug/1690768 04:04:50 Launchpad bug 1690768 in masakari "Notification status will be "error" if recovered instance was "resized"." [High,New] 04:04:57 abhishekk: Right... 04:05:47 samP: Can I split the report to two reports? 04:05:51 abhishekk: Im not gonna attend full PTG...:) 04:06:03 rkmrHonjo: why? 04:07:02 rkmrHonjo: why would you think so? I can only see one issue here. 04:07:30 samP: I wrote two expected behaviour. but , IMO, I think that these are difference problems after that. 04:08:18 rkmrHonjo: have you checked sheve case with shelved_offload_time -1 i.e. never offload? 04:08:55 i.e. instance is in shelved state and recovery happens? 04:09:05 notification status will be going to error, this is severe issue. But, IMO, recovering "stopped->resized" instance as "active" is not severe. 04:09:45 abhishekk: why would some one do that, shelved with -1? 04:09:45 abhishekk: shelved_offload? This report tell about resize. Would you like to say that resize auto confirm? 04:10:24 rkmrHonjo: no this is different, we will test this scenario 04:11:59 abhishekk: Did you say that you tested recovering "resized" instance? And, notification status was "finished" when you tested? 04:12:00 shelved with offload_time -1 is diffent scenario but sill could related to same situation, if node goes down. 04:12:32 samP: right, we will check this scenario 04:12:50 abhishekk: thanks... let us know the result.. 04:13:04 samP: sure 04:13:42 samP: will let you know on irc or will comment on same bug once done 04:13:55 abhishekk: great.. thanks 04:14:19 abhishekk: ah, sorry, I misunderstood that you already tested. 04:14:54 rkmrHonjo: no problem 04:15:30 rkmrHonjo: you wants to split the report because, 1) Fix the notification status 2)Fix the recovery flow for resized state VMs 04:15:42 rkmrHonjo: ^^ Am I right? 04:15:51 samP: yes. 04:16:54 1 is issue about notification status. But 2 is issue about instance status. 04:17:32 rkmrHonjo: correct, but those 2 are still related to same issue, right? 04:18:04 rkmrHonjo: If you think its better to split this, then please go ahead. 04:18:20 samP: thanks. I'll split after that. 04:18:31 rkmrHonjo: sure, thanks. 04:18:55 OK then, any other bugs..? 04:19:20 ok, nothing 04:19:26 sagara: thanks. 04:19:46 let's move to discussion 04:19:57 #topic Discussion points 04:20:41 #link Recovery method customization https://review.openstack.org/#/c/458023/ 04:22:00 I think it doses make sense to add Mistral to alternative.. 04:22:19 abhishekk: what would you think about adam's comment? 04:23:19 samP: ok, I will discuss with Tushar San and modify the specs 04:23:35 abhishekk: sure... 04:23:50 #action samP Review https://review.openstack.org/#/c/458023/ 04:24:02 I will review this^^ 04:24:19 Other Pike work items 04:24:41 Notifying API progress: BP submitted 04:24:47 rkmrHonjo: thanks ^^ 04:24:55 samP: thanks, also review api documentation 04:25:10 abhishekk: sure... I will do that 04:25:35 samP: could you please share blueprint link for notifying API? 04:25:47 #action samP Review https://review.openstack.org/#/c/459516/ 04:26:05 #link https://blueprints.launchpad.net/masakari/+spec/notifications-in-masakari 04:26:08 samP: thanks 04:26:26 rkmrHonjo: thanks... 04:26:43 abhishekk: rkmrHonjo put the link 04:27:01 rkmrHonjo: thanks :) 04:27:39 I and Takahara describe specs and implement from now on. 04:27:49 rkmrHonjo: thank you... 04:28:11 rkmrHonjo: great 04:28:32 rkmrHonjo: let me know if any help needed 04:28:48 Dinesh_Bhor: Thanks! 04:29:06 Force Stonith: had some discussion with Adam about this. 04:29:24 I will add spec for this one soo. Really sorry for the delay.. 04:29:55 Improve the masakari-hostmonitor's implementation about detecting split-brain 04:30:17 samP: Sorry, no update. I'll update next week. 04:30:34 rkmrHonjo: sure...NP 04:30:57 Other are Just BPs with no specs. 04:31:10 (1) Prevent from flapping feature 04:31:31 (2) Recoverable libvirt events customization 04:31:32 I'll add 'Prevent from flapping' BP 04:31:37 sagara: sure 04:32:14 sagara: We can discuss how to do this in separate session or IRC 04:32:54 for (2) Recoverable libvirt events customization, this would be a BP for masakari-monitors. 04:33:23 Please add them when you have time.. 04:34:15 samP: thanks 04:35:00 Let's move to AOB 04:35:05 #topic AOB 04:35:26 About rpm packaging 2/3 done. 1 wating 04:35:57 Once, it is done, I will fix the tags for all masakari packages. 04:37:41 Maxwell Li asked about ansible support for Masakari 04:38:10 #link Request Ansible support for Masakari http://lists.openstack.org/pipermail/openstack-dev/2017-April/115944.html 04:38:47 I will discuss with him about how to proceed with this 04:40:34 samP: By the way, you fixed masakariclient package in pypi. thanks. I'll try to add it to global-requirements. 04:40:38 samP: ok, we will keep watch on ML 04:41:38 rkmrHonjo: yes. But I have push 3.0.0 tag and need to add pip packging jobs to gate 04:42:07 abhishekk: thanks... 04:42:28 <> 04:42:36 samP: Ok. Should I add it after you done? 04:42:51 sorry for interrupting... 04:43:38 Sice we have done presentaions, HA session, in summit, now pepole may ask question about masakari in ML or IRC 04:44:05 Please answer them if you can... or let me know if Im not there.. 04:44:13 samP: sure 04:44:20 OK, Sure 04:44:46 samP: Sure. 04:46:36 I will also work with openstack HA community for add resorce-agents, and you all are welcome to openstack HA meetings 04:46:53 #link http://eavesdrop.openstack.org/#High_Availability_Meeting 04:47:08 Any other topics to discuss? 04:48:12 samP: nothing from our side 04:48:21 nothing 04:48:23 nothing 04:48:25 nothing 04:48:50 OK then, lets finish bit early... 04:49:02 Thank you all 04:49:09 thanks to all 04:49:23 OH. Dinesh_Bhor, I will replay to your mail about pacemaker 04:49:31 thank you all... 04:49:34 bye 04:49:35 #endmeeting