04:00:03 <samP> #startmeeting masakari 04:00:04 <openstack> Meeting started Tue Mar 6 04:00:03 2018 UTC and is due to finish in 60 minutes. The chair is samP. Information about MeetBot at http://wiki.debian.org/MeetBot. 04:00:05 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 04:00:08 <openstack> The meeting name has been set to 'masakari' 04:00:16 <samP> Hi all for masakari 04:00:20 <tpatil> Hi 04:00:20 <sagara> Hi 04:01:12 <samP> Glad you all came back safely 04:01:20 <samP> from PTG 04:01:41 <samP> #topic High priority items 04:01:53 <samP> About Release 04:02:10 <samP> all 3 projects has been released 04:02:38 <sagara> Great 04:02:46 <samP> currently, python masakari client does not have stable/queens branch 04:03:40 <tpatil> Once the masakari-monitors patch is merged, you will need to release it's new version, correct? 04:03:42 <samP> The reason is in comment of following patch 04:03:53 <samP> #link https://review.openstack.org/#/c/547502/ 04:04:05 <samP> tpatil: correct 04:04:06 <tpatil> #link : https://review.openstack.org/#/c/546492/10 04:04:49 <tpatil> samP: Ok, Is there any problem in cutting stable/queens branch for python-masakariclient? 04:06:27 <samP> tpatil: waited for release. Currently no blockers. I will create it today 04:06:41 <tpatil> samP: OK 04:08:20 <tpatil> So only masakari-monitors patch is pending for review against Queens release 04:09:31 <samP> And fix masakari command for python-masakariclient 04:09:41 <samP> rkmrHonjo: ^^ correct? 04:10:14 <tpatil> samP: yes, I remember, that create_connection method issue 04:10:37 <samP> tpatil: yes. 04:10:38 <rkmrHonjo> samP: Correct. 04:11:41 <rkmrHonjo> This patch fixes masakari command. #link https://review.openstack.org/#/c/547879/ 04:11:43 <samP> I think we need to fix those 2 problems and release a new version for both pyclient and monitors 04:11:52 <samP> rkmrHonjo: correct 04:13:17 <samP> Please do not merge this patch before create stable/queens for python-masakariclient 04:13:57 <tpatil> samP: point noted 04:14:23 <samP> I will submit required patches for create stable/queens today. 04:14:44 <rkmrHonjo> samP: I got it. 04:15:34 <samP> For openstack/masakari and masakari-monitors, now we can work master for R 04:16:01 <samP> For openstack/python-masakariclient, please wait for stable/queens branch 04:16:57 <samP> #topic Rocky work items 04:17:28 <samP> I would like to take some time to discuss about Rocky work items. 04:18:34 <samP> First, I will create a etherpad for Rocky, and fill it with existing items 04:19:13 <samP> Please propose any new items to etherpad before next IRC meeting on 11/3/2018 04:19:26 <tpatil> samP: Sure 04:21:13 <rkmrHonjo> samP: OK. 04:21:43 <tpatil> In PTG, I met Greg, Abhishek and Adam along with NTT folks 04:21:45 <samP> #link https://etherpad.openstack.org/p/masakari-rocky-work-items 04:21:54 <samP> ^^ here is the etherpad 04:22:07 <samP> tpatil: thanks 04:22:27 <tpatil> Greg is looking forward to get his team's patch merged in Rocky about Intrusive monitoring 04:22:31 <samP> tpatil: any update from them. Really sorry that I wan not able to be there 04:22:45 <tpatil> samP: Not yet 04:22:51 <samP> tpatil: got it. 04:23:25 <tpatil> Also, if someone is available we can start work on nova-host-alerter 04:24:27 <samP> rkmrHonjo: Any progress on your side of this work? 04:24:34 <samP> rkmrHonjo: nova-host-alerter 04:24:40 <tpatil> I think you are familiar with this openstack resource agents and this new agent will be part of it 04:25:56 <samP> tpatil: yes. if I remember correctly, rkmrHonjo was stared to work on this. 04:26:03 <tpatil> #link : https://aspiers.github.io/openstack-day-israel-2017-compute-ha/#/no-fence_evacuate 04:26:19 <rkmrHonjo> Please wait.. 04:27:54 <samP> rkmrHonjo's team was creating a PoC for this. OCF-RA and masakari plugin 04:28:07 <rkmrHonjo> Excuse me, does nova-host-alerter means monitor implemented as RA? 04:28:35 <tpatil> rkmrHonjo: That's correct 04:28:37 <samP> rkmrHonjo: monitor implement as RA 04:29:36 <rkmrHonjo> Ah, OK. I'm preparing to submit PoC. Sorry for late. I'll submit it in next week. 04:30:17 <samP> rkmrHonjo: thanks. 04:30:29 <samP> I will put this item to Rocky work items. 04:31:19 <samP> This is bit heavy task. rkmrHonjo: might better to split the tasks. 04:31:33 <samP> Let's discuss this on Rocky work item discussion. 04:32:09 <rkmrHonjo> ok. 04:32:25 <samP> For Rocky work item discussion, which method you prefer, IRC or VoIP? 04:32:57 <samP> VoIP also have chat, VoIP=Zoom 04:33:12 <tpatil> samP: Once nova-host-alerter is available, what is the plan for masakari-monitor? 04:34:08 <samP> tpatil: we have 2 options, 04:34:50 <samP> (1) retire hostmonitor part from masakari-monitors in favour of nova-host-alerter 04:35:20 <samP> (2) keep both, since current masakari-monitors doing it different manner 04:36:34 <samP> In future, process monitor could also implement as same architecture with nova-host-alerter 04:36:48 <samP> However, not the instance monitor. 04:37:58 <tpatil> samP: Ok, process monitor is doing nothing as of now. Do we really want it? 04:38:00 <samP> since we have new requirements coming in for instance monitor, we do have to maintain it 04:38:25 <tpatil> samP: Ok I got it. 04:39:26 <samP> tpatil: about process monitor, agree with current situation. However, it is still valid as a reference driver for process monitoring 04:39:50 <samP> In VMHA 04:40:22 <samP> In VMHA usecase, process monitoring is one of the requirement, along with host and instance monitoring. 04:41:37 <tpatil> samP: Let's come up with some use case and take some recovery action against process notifcations other than simply logging it 04:41:43 <samP> Our, current process monitor do not do much at the time. But in future, if we can cutormize the recovery action, then we might able to use it in much efficient way 04:42:00 <samP> tpatil: totally agree. 04:42:55 <tpatil> samP: Recovery customization is next big item for Rocky, we have completed the POC. We can talk about it in next meeting 04:43:14 <samP> tpatil: great work. thanks 04:43:29 <rkmrHonjo> tpatil: great. 04:43:34 <samP> tpatil: let's look into details in next meeting 04:44:28 <tpatil> samP: Sure 04:44:47 <rkmrHonjo> Sorry, I leave this meeting at 13:55. 04:44:59 <rkmrHonjo> 13:55 JST 04:45:10 <samP> About, "Rocky work items" I will send a mail for details about the discussion. 04:45:12 <samP> rkmrHonjo: NP 04:46:18 <samP> #topic Masakari Project mascot 04:46:25 <samP> Any new ideas? 04:47:47 <samP> Please propose if you have any ideas. I would like to decide some thing in next meeting..:) 04:48:22 <rkmrHonjo> OK. When is the time limit_ 04:48:26 <rkmrHonjo> s/_/?\ 04:48:33 <sagara> samP: OK, I'm also still considering 04:48:52 <samP> rkmrHonjo: before 3/11 04:48:58 <samP> rkmrHonjo: next meeting 04:49:07 <rkmrHonjo> oh. I got it. 04:49:41 <samP> #topic AOB 04:50:16 <rkmrHonjo> py35 of masakari was failed by date time format error. #link 04:50:19 <rkmrHonjo> #link https://review.openstack.org/#/c/545545/ 04:50:44 <samP> Skipped the Bug/Patch part, cause we have already discussed above about important issues. 04:50:58 <samP> Please share, other than that.. 04:51:27 <rkmrHonjo> Oh, sorry. 04:51:55 <samP> rkmrHonjo: sorry, not about one posted 04:52:08 <samP> rkmrHonjo: your issue is valid 04:53:22 <rkmrHonjo> samP: ok. Does anyone analyze this py35 error? If "no", I analyze it. 04:53:32 <tpatil> rkmrHonjo: Please report it as a bug and someone will take up this issue 04:53:40 <rkmrHonjo> tpatil: ok. 04:54:16 <samP> tpatil: rkmrHonjo: thanks/ 04:55:08 <samP> seems like datetime format error, 04:55:25 <samP> Anyway, will follow the Bug report. 04:56:05 <samP> Last 5 mins, any other issues to discuss? 04:56:23 <tpatil> maybe some Oslo_utils related changes is causing this problem 04:57:10 <samP> BTW, NTT system-fault-ci masakari-integration-ci is down for maintenance 04:57:52 <samP> I will be at OpenStack Ops meetup on 3/7-8 04:58:18 <samP> #link https://wiki.openstack.org/wiki/Operations/Meetups/TYO-ops-meetup 04:58:33 <samP> almost time.. 04:58:41 <samP> Thank you all... 04:59:15 <samP> Please use #openstack-masakari @freenode IRC or openstack-dev ML with [masakari] for further discussion 04:59:19 <sagara> Thank you, bye 04:59:33 <samP> Thanks you again... bye 04:59:39 <samP> #endmeeting