04:01:21 <tpatil> #startmeeting Masakari
04:01:22 <openstack> Meeting started Tue Jun 30 04:01:21 2020 UTC and is due to finish in 60 minutes.  The chair is tpatil. Information about MeetBot at http://wiki.debian.org/MeetBot.
04:01:23 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
04:01:25 <openstack> The meeting name has been set to 'masakari'
04:01:32 <tpatil> Hi Masakari Team
04:01:39 <suzhengwei> hi
04:01:58 <tpatil> Not sure if Sampath san will join this meeting
04:02:05 <tpatil> suzhengwei: Hi
04:02:16 <tpatil> #topic Critical Bugs and Patches
04:05:08 <tpatil> No critical bugs. Moving ahead
04:05:35 <tpatil> Victoria Work items
04:05:39 <tpatil> #link: https://etherpad.opendev.org/p/masakari-victoria-workitems
04:06:56 <tpatil> Enable/Disable evacuation segment wise (suzhengwei)
04:07:38 <tpatil> I have posted comments on why the functional CI job is failing
04:07:41 <tpatil> #link: https://review.opendev.org/#/c/700879
04:08:18 <suzhengwei> I will review it asap.
04:09:32 <tpatil> Promotion for large scale hosts failure(suzhengwei)
04:09:54 <tpatil> I have started reviewing the spec: https://review.opendev.org/#/c/732477
04:10:13 <suzhengwei> thx.
04:10:33 <tpatil> The spec will change the entire masakari-engine logic
04:12:02 <tpatil> suzhengwei: How will it work if masakari-engine is deployed on multiple hosts?
04:13:52 <suzhengwei_> I will give more detail later.
04:15:00 <suzhengwei_> It is a big feature, I will split it into several  pieces.
04:15:41 <tpatil> suzhengwei_: Yes, also it would need database model changes as well
04:16:02 <suzhengwei_> yes.
04:17:09 <tpatil> Continuous check to determine host failure(suzhengwei)
04:17:19 <tpatil> Are you working on writing spec for this feature?
04:18:03 <suzhengwei_> I don't think it needs a spec. I will directly give a patch about it.
04:19:57 <tpatil> Are you trying to make changes to masakari-monitor to determine host failure?
04:20:06 <suzhengwei_> yes.
04:20:53 <suzhengwei_> After I fix unit test, I will commit it to gerrit.
04:21:18 <tpatil> Ok, Thanks
04:21:43 <tpatil> Add PoweroffComputeNodeTask in host recovery workflow(suzhengwei)
04:22:26 <suzhengwei_> It's just a thought, and I haven't start the work.
04:23:16 <tpatil> What exactly you want to do here?
04:24:41 <suzhengwei_> Make sure to fence the failure host before instance evacuating.
04:26:07 <tpatil> OK, so most likely changes to the masakari-monitor side, Pacemaker and corosync can take care of fencing as well.
04:26:50 <tpatil> New host monitor driver by consul(suzhengwei)
04:27:19 <tpatil> #link : https://review.opendev.org/#/c/734017/1
04:27:25 <tpatil> I will review the updated PS
04:27:34 <suzhengwei_> thanks
04:27:59 <tpatil> Cooperaton with Blazer project(suzhengwei)
04:28:59 <tpatil> So here you want to automate and set the compute host as reserved from masakari directly using blazer APIs, Is it correct?
04:32:07 <suzhengwei__> we can use both. Blazar reserved hosts is useful on special env.
04:33:40 <suzhengwei__> ping
04:33:45 <tpatil> Multiple masakari-api/engine test
04:34:51 <tpatil> At my end, I don't have setup to try out this test. Will check with Sampath san how we can confirm this point.
04:35:26 <suzhengwei__> ok
04:36:40 <tpatil> Support new roles
04:37:39 <tpatil> Can you please elaborate what precisely you want here. As an operator, you can configure RBAC as per role in policy.json.
04:37:51 <suzhengwei__> It is a common issue lead by Keystone project. Forget about it for a while.
04:38:31 <tpatil> Ok
04:39:00 <tpatil> Is there any other work item that you would like to discuss?
04:39:12 <suzhengwei__> no
04:39:41 <suzhengwei__> Can we give some review to recently commits?
04:40:48 <tpatil> Sure, I will try to do as much as possible from my end
04:41:29 <tpatil> I don't have any other topic for discussion. So let's end this meeting early
04:41:42 <suzhengwei__> ok
04:41:49 <suzhengwei__> bye
04:41:54 <tpatil> suzhengwei__: Bye
04:41:59 <tpatil> #endmeeting