04:00:07 <samNTT> #startmeeting masakari
04:00:08 <openstack> Meeting started Tue Feb 13 04:00:07 2018 UTC and is due to finish in 60 minutes.  The chair is samNTT. Information about MeetBot at http://wiki.debian.org/MeetBot.
04:00:09 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
04:00:11 <openstack> The meeting name has been set to 'masakari'
04:00:18 <samNTT> Hi all for masakari
04:00:25 <sagara> hi
04:00:26 <nsingh> hi all
04:00:32 <Dinesh_Bhor> Hi all
04:00:36 <samNTT> Hi all
04:00:41 <samNTT> let's start
04:00:56 <samNTT> #topic Queens Release
04:01:52 <tpatil> Hi All
04:01:57 <samNTT> As we discussed last week, I will create stable/queens for masakari-monitors and python-masakariclient today
04:02:00 <samNTT> tpatil: Hi
04:02:51 <samNTT> Though, we have to resolve one issue, #link https://review.openstack.org/#/c/542683/
04:03:44 <tpatil> The above issue should be fixed in queens or rocky release?
04:04:54 <samNTT> tpatil: For queens, openstacksdk>=0.9.19 and upper  openstacksdk===0.11.3
04:05:26 <samNTT> tpatil: as you all pointed out in the review
04:06:17 <samNTT> with current code, UT should fail if openstacksdk>=0.10.0
04:06:57 <tpatil> But then we will need to wait until global requirements bumps openstacksdk>=0.10.0
04:07:09 <samNTT> tpatil: correct
04:07:26 <sagara> samNTT: I think we can support both version openstacksdk>=0.9.19 and >=0.10.0 with modifying masakarimonitors/ha/masakari.py.
04:07:46 <samNTT> sagara: That can be done
04:07:54 <tpatil> Does OpenStack community is in favor of bumping openstacksdk to 0.10.0 in queens?
04:08:12 <samNTT> tpatil: I think not for queens
04:08:53 <samNTT> tpatil: as you mentioned in the review, #link https://review.openstack.org/#/c/540343/1
04:09:17 <samNTT> Monty proposed it, but it seems not gonna happen
04:10:05 <tpatil> ok, so basically we need to add exception handling code (AttributeError) to support both versions
04:10:11 <Dinesh_Bhor> I agree with sagara san.
04:10:43 <samNTT> tpatil: sure, agree.
04:11:11 <samNTT> support both versions is the best possible solution at this time.
04:11:15 <tpatil> the same problem must be existing in other projects too, does anyone know how the other projects are addressing this issue?
04:12:46 <samNTT> seems that swift using http_status, but I think they are not using requirement updates
04:15:21 <Dinesh_Bhor> #link https://review.openstack.org/#/c/540315/3
04:16:29 <samNTT> and trove, ironic, zaqur
04:17:34 <tpatil> Dinesh_Bhor: Even though the above patch is merged , it will fail if openstacksdk installed version is 0.9.19
04:17:42 <Dinesh_Bhor> exactly
04:17:50 <Dinesh_Bhor> I think they haven't noticed the openstacksdk>=0.9.19 issue
04:19:38 <samNTT> you will not hit http_status error, if you are not deliberately test against <=0.9.19
04:21:33 <samNTT> Any way, I will check with other projects and update the patch work for both versions
04:21:45 <Dinesh_Bhor> samNTT: okay
04:21:58 <samNTT> If you find anything, please share.
04:22:07 <Dinesh_Bhor> sure
04:22:13 <tpatil> samNTT: Ok
04:22:28 <samNTT> Once we done with this, I will cut off stable/queens.
04:24:39 <samNTT> For openstack/masakari, initial proposal was to create stable/queens on 2/23.
04:25:18 <samNTT> However, thinking about the release schedule of other projects, 2/23 seems bit late.
04:26:58 <tpatil> #link https://bugs.launchpad.net/masakari/+bug/1746229
04:26:59 <openstack> Launchpad bug 1746229 in masakari "masakari-engine recovery looking for URL endpoint for service_name='Compute Service' instead of 'nova'" [Undecided,New] - Assigned to Louie Kwan (lkwan)
04:27:08 <tpatil> Do you think this bug is critical?
04:27:28 <tpatil> I think masakari engine doesn't handle reload of config files correctly
04:27:38 <tpatil> I haven't yet reproduced this bug though
04:30:24 <tpatil> This issue was discussed in this ML thread http://lists.openstack.org/pipermail/openstack-dev/2018-January/126552.html
04:30:27 <samNTT> tpatil: I think we must fix it. my impression was need more survey on this
04:31:05 <tpatil> Ok, We will reproduce this bug
04:31:50 <Dinesh_Bhor> If operator sets 'nova_catalog_admin_info' correctly then there will be no issue.
04:32:40 <tpatil> Dinesh_Bhor: so I think it's not critical. Maybe some issue with handling reloading of config files
04:33:26 <Dinesh_Bhor> tpatil: yes, agree. I will check this. But definitely the default value of this config option needs to be changed.
04:34:03 <samNTT> Dinesh_Bhor: tpatil: understood.
04:34:13 <tpatil> is there any common place where we can see the default service_name of all projects similar to service_type
04:34:38 <samNTT> tpatil: Why would you say "problem with config reload"?
04:35:31 <Dinesh_Bhor> samNTT: Greg said in his email that after also he changed the config option value he was not able to resolve the issue.
04:35:40 <tpatil> samNTT: Becoz if you change the nova_catalog_admin_info config option in masakari.conf and restart the masakari-engine, it doesn't refer to the latest service name
04:36:00 <samNTT> tpatil: Dinesh_Bhor: gotit..
04:40:49 <samNTT> tpatil: Dinesh_Bhor: Could you please find more about this bug and let me know what can be done in queens to fix this issue?
04:41:02 <tpatil> samNTT: Sure
04:41:05 <Dinesh_Bhor> yes
04:42:15 <samNTT> Adding the correct default would fix this temporary and I would like to know how critical is the "config reload" issue
04:43:00 <samNTT> tpatil: Dinesh_Bhor; thank you..
04:43:21 <samNTT> I think I'm still in release topic
04:43:25 <tpatil> samNTT: how critical this bug is: it depends on how often you change the config file and want to reload instead of stop/start
04:44:06 <tpatil> samNTT: Will reproduce this bug and let you know if this is a easy fix or not
04:45:15 <samNTT> tpatil: exactly :).. I meant to say is this effect all config options or part of it.
04:45:44 <samNTT> #topic Critical Bugs/Patches
04:45:46 <tpatil> samNTT: Will find out the required info
04:46:06 <samNTT> Any critical issues apart from discussed above
04:46:08 <samNTT> tpatil: thanks
04:46:59 <Dinesh_Bhor> I think this needs attention: https://review.openstack.org/#/c/531310/3
04:48:30 <tpatil> Dinesh_Bhor: I will review this patch today
04:48:39 <Dinesh_Bhor> okay
04:49:02 <samNTT> Dinesh_Bhor: thanks for the info, I will review this too
04:50:22 <nsingh> ui-cookiecutter patch is pending for review.
04:50:28 <nsingh> https://review.openstack.org/#/c/528647/
04:51:14 <tpatil> samNTT: In queens cycle, you have no plan to include masakari-dashboard, correct?
04:51:38 <samNTT> tpatil: correct
04:52:33 <samNTT> The reason is, we only have cookiecutter code in there.
04:53:10 <tpatil> samNTT: Ok, Niraj is ready with the patches for adding failover segment and hosts in masakari-dashboard. he will propose these patches soon for the community review. Let's review this patch and merge it for Rocky relese
04:53:33 <samNTT> tpatil: sure, sounds good.
04:53:39 <nsingh> yes
04:54:01 <samNTT> Let's review and merge #528647
04:54:22 <samNTT> nsingh: Thanks for the great work..!
04:54:42 <nsingh> samNTT: thank you :)
04:55:00 <samNTT> Any other issues to discuss?
04:55:02 <samNTT> nsingh: NP
04:55:21 <samNTT> Last 5 mins of the meeting
04:55:56 <samNTT> #topic AOB
04:56:19 <samNTT> I will cut the stable/queens for projects as we discussed above.
04:56:54 <samNTT> Please let me know if you would like to backport any patches after we create queens branch
04:57:12 <tpatil> samNTT: Sure
04:57:58 <samNTT> For further discussion, please use IRC #openstack-masakari or openstack-dev ML with [masakari]
04:58:15 <samNTT> Let's finish today's meeting.
04:58:23 <samNTT> Thank you all
04:58:28 <sagara> thanks all, bye
04:58:37 <samNTT> BYE
04:58:40 <samNTT> #endmeeting