04:01:12 #startmeeting masakari 04:01:13 Meeting started Tue Feb 6 04:01:12 2018 UTC and is due to finish in 60 minutes. The chair is samP. Information about MeetBot at http://wiki.debian.org/MeetBot. 04:01:14 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 04:01:17 The meeting name has been set to 'masakari' 04:01:24 Hi all 04:01:38 Hi all 04:01:44 let's start 04:02:11 #topic High Priority Items 04:02:19 About Release 04:02:57 I had a discussion with release team and agree to follow independent release model for Queens 04:03:28 Form next cycle, we will follow the cycle-with-milestones 04:03:29 Ok 04:03:38 #link https://releases.openstack.org/reference/release_models.html 04:03:55 samP: Sure 04:04:02 samP: Service type patches are up for review, do you want this change in Queens cycle? 04:04:20 tpatil: that's one thing I would like to discuss 04:05:18 since requirements are freezed, if we merged them then we have to propose FFE to requirements 04:06:23 on the other hand, instance-ha has alias `ha` 04:06:24 samP: IMO, it's not a blocker.it can be done early Rocky release.What do you think? 04:07:57 tpatil: are you proposing to update requirement manually, till Rocky start? 04:10:32 samP: If we don't want to depend on requirements, then that's one way to merge service type change in queens cycle. But I don't think we should go in that way 04:11:07 my main question is, do you want to change service_type in Queens cycle? 04:12:01 tpatil: I would like to postpone it to Rocky, if no objections 04:14:25 If service type change is not a blocker for other OpenStack projects, then I think it's ok to merge it in early Rocky release 04:15:40 for my understanding it would not be a blocker for other projects. 04:16:10 OK, then let's land it on early Rocky. 04:16:36 samP: Sure 04:16:56 Since we are following the independent release model, I would like to propose closing dates for Queens. 04:17:05 Is there any existing openstack service sharing the same "HA" service_type? 04:17:26 for Masakari, stable/queens will be created on 2/23 04:18:07 Dinesh_Bhor: none that i known of 04:18:41 samP: okay, then there is no issue. We can update the service_type in next release. 04:19:05 Please do not merge patches for openstack/masakari after 2/20 04:19:44 if you would like to merge something after 2/20, please discuss with me. 04:20:29 For masakari-monitors, python-masakariclient stable/queens will be created on 2/13 04:20:29 samP: When will stable/queen branch be cut for masakari projects? 04:20:40 samP: Ok 04:20:47 tpatil: it will be 2/23 04:21:27 Please do not merge any patches for masakari-monitors and python-masakariclient after 2/9 04:21:30 samP: One question related to service type 04:21:37 tpatil: sure, 04:21:53 if someone is using masakari for the first time, then they would need to add service as 'ha' and not 'instance-ha', correct? 04:22:12 tpatil: yes 04:23:43 samP: Does operator refers service-types-authority project for creating services for OpenStack deployment? 04:24:49 If yes, then we need to confirm masakari will work using alias 'ha'. 04:24:50 tpatil: in that case we have `ha` alias to `instance-ha` 04:25:20 I will confirm this point from my end 04:25:37 tpatil: thank you. that will be great. 04:27:16 tpatil: if there are any issues, could you please share. So, we could merge them to Queens and fix the related problems manually. 04:27:34 In Keystone Service db table, I can see only type column to store service type 04:27:57 Need to check how to specify alias when you add a service 04:28:21 samP: I will update my findings 04:29:46 "API consumer cannot find a given service-type in the service-catalog, they are directed to try the list of aliases" need to find out more about it. 04:30:56 tpatil: thanks. I will take a look on this. 04:30:59 since consumers of masakari service are python-masakariclient and masakari-monitors, there shouldn't be any issues 04:32:29 tpatil: currently, yes. if someone would like to call masakari API from their custom monitors, then that would be the situation 04:33:34 samP: in that case, they would need to follow service type authority guidelines to try using alias 04:34:20 tpatil: correct 04:35:29 samP: So it's ok to merge service type changes in early Rocky, correct? 04:36:48 tpatil: Correct. I do not see any problem with that. 04:36:55 samP: Ok 04:38:17 All the details about release is in today's meeting wiki 04:38:28 #link https://wiki.openstack.org/wiki/Meetings/Masakari#High priority items 04:39:15 which is not a good place to hold those info. I will put those info in masakari wiki page and send them to ML 04:39:33 if you have any questions or requests please let me know. 04:39:43 samP :Sure 04:40:51 I would like to merge operators guide documentation in Queens. 04:40:57 #link https://review.openstack.org/#/c/489095/ 04:40:58 patch 489095 - masakari-monitors - Masakari-monitors operator's documentation 04:42:12 I have already read the doc, only have few comments. I will put my review comments asap. 04:42:50 #topic Bugs and patches 04:43:01 Any bugs or patches to discuss? 04:44:26 Horizon Plugin, what is happening to this patch? 04:44:32 #link https://review.openstack.org/#/c/528647/ 04:44:33 patch 528647 - masakari-dashboard - Initial UI-Cookiecutter commit 04:45:11 I thought I have merged it :) 04:45:50 Zuul requirements jobs are failing after workflow +1 04:45:56 need to merge it again 04:46:39 In Queens release, are you planning to release masakari-dashboard? 04:47:26 tpatil: no. I think there is nothing to release yet. right? 04:47:39 samP: Correct 04:48:19 tpatil: it's first release will be in Rocky 04:49:11 samP: Ok, I will review cookie cutter patch and vote +2 if no comments from my end 04:49:29 tpatil: sure, I will review it again 04:49:30 #link : https://bugs.launchpad.net/masakari/+bug/1746229 04:49:31 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:49:44 Need to reproduce this bug 04:51:57 samP: I will confirm this LP bug 04:53:09 tpatil: thanks. 04:56:22 seems "nova" is correct. but, tpatil: please update 04:56:35 we only have 4 mins left 04:56:44 samP: ok 04:56:56 Any updates to share? 04:58:26 Please use #openstack-masakari @freenode or openstack-dev ML with [masakari] for discuss any issues related to masakari 04:58:58 Let's finish today's meeting 04:59:04 Thank you all 04:59:16 Thanks 04:59:26 #endmeeting