04:00:55 #startmeeting masakari 04:00:56 Meeting started Tue Aug 22 04:00:55 2017 UTC and is due to finish in 60 minutes. The chair is samP. Information about MeetBot at http://wiki.debian.org/MeetBot. 04:00:57 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 04:00:59 The meeting name has been set to 'masakari' 04:01:06 Hi all o/ 04:01:15 Hi all 04:01:19 o/ 04:01:54 #link agenda https://wiki.openstack.org/wiki/Meetings/Masakari 04:02:03 Let's start 04:02:15 First; about the release 04:02:56 Thanks to all, we were able to do the 4.0.0.0rc1 on 8/18 04:03:26 Next tag would be 4.0.0.0rc2, will be on 8/25 04:04:00 Final release 4.0.0 will be on 8/30 04:04:39 Now we have stable/pike in a separate branch, we can continue work on master for Queens 04:05:35 If you have any critical updates for stable/pike please raise them before 8/25 04:06:02 samP: Sure 04:06:19 8/29 Masakari IRC team meeting would be the last place to discuss such things 04:06:22 Thanks 04:06:43 #topic Bugs 04:07:03 any bugs to discuss? 04:08:17 Since we released last week, not much to discuss here. If you have any, please use AOB to discuss them 04:08:31 Let's goto next item 04:08:46 #topic Discussion points 04:09:02 (1) Application for become OpenStack oficial project 04:09:33 Couldn't finish it. definitely do it today 04:09:39 sorry.. 04:09:54 (2) Install guide document 04:10:28 I think patches are up for all documentations. Need to review them. 04:10:41 ok. 04:10:55 This include masakari-monitors documentations 04:11:24 I will and please review them if you have spare time 04:11:41 (3) recovery method customization 04:12:14 we need to clarify discussion points with Mistral team at PTG 04:12:32 Mistral etherpad is not open to add this item in the Queen PTG agenda 04:12:49 tpatil: Thanks. 04:12:57 IMO, For our case, there is no need to restart mistral service 04:13:31 but in future, if we add few actions which might requires you to restart mistral service, then that could be a problem. 04:13:46 tpatil: you said, some actions would need to restart it. 04:13:52 we will discuss with Mistral community to understand in what instances you need to restart mistral service 04:14:29 samP: For our POC, no need to restart mistral service 04:14:45 tpatil: great. 04:15:20 tpatil: But we dont know what will happen future, if some one add new action. 04:15:33 tpatil: as you said ^^ 04:16:07 tpatil: let's make those clear, So, we could avoid using them. 04:16:17 samP: correct, so we will discuss this point with Mistral community 04:16:25 tpatil: thanks. 04:17:16 tpatil: May I ask you to add this item to Mistarl etherpad, when it opens 04:17:33 samP: Will do 04:18:42 #action tpatil Add item to Mistral PTG etherpad for discuss when we should restart mistral service 04:18:47 tpatil: thanks 04:19:09 (4) Find hosts without specifying segments 04:19:21 rkmrHonjo: any updates on this? 04:19:24 I have thought about CLI way.(This was my homework in previous meeting.) In my idea... 04:19:50 If user run "masakari get-host-by-segment ", masakariCLI will do below processes: 04:20:14 1. Call segment list API. 04:20:14 2. Call host list API for each segments. 04:20:23 3. If there is the specified host, masakariCLI will show following columns: segment id, segment name, host id, host name 04:20:41 For example, "neutron net-list" uses multiple APIs.(Network list API & Subnet list API) 04:21:25 So, I think that CLI way is not impossible. 04:21:34 rkmrHonjo: thanks 04:22:12 Are there any need for get singe host details in masakari? 04:22:30 I mean without segments? 04:22:52 For an Ex, monitoring masakari itself 04:23:18 samP: Yes, when you process notification, we get hostname from notification request 04:23:53 samP: but we get the host details using db apis 04:24:00 Dinesh: Please confirm ^^ 04:24:09 tpatil: yes, correct 04:24:10 tpatil: yes correct 04:24:25 it is internal and not the user specific requirement 04:24:29 but my question is, do we need that on APIs? 04:24:50 I think, No 04:24:53 samP: No 04:25:05 for an ex, if we want to setup a horizon UI for masakari :) 04:25:26 probably not.. 04:25:58 OK, then can we agree to go with CLI based solution for this? 04:26:18 which is proposed by rkmrHonjo 04:26:48 samP: OK. Should I write bp? 04:27:23 Ah, I'll write bp. sorry. 04:28:07 rkmrHonjo: this is a new feature for python-masakariclient, please write a bp 04:28:10 for this 04:28:16 samP: Sure. 04:28:55 if no objection; rkmrHonjo please proceed with CLI based solution. 04:29:39 samP: adding this support in CLI is simplest way to solve this problem 04:29:43 you will have another chance to raise your objections in BP or code review. 04:29:50 tpatil: sure. 04:30:46 #action rkmrHonjo crate BP and process with CLI based solution for "Find hosts without specifying segments" 04:31:48 rkmrHonjo: I assigned this item to you, is it OK? 04:32:04 samP: No problem. 04:32:08 rkmrHonjo: thanks 04:32:24 (5) Queens Work Items 04:32:52 I created a etherpad for this/ 04:33:34 #link Queens Work Items https://etherpad.openstack.org/p/masakari-queens-workitems 04:34:02 Please add new items before 8/28 04:34:15 We could review them on 8/29 meeting 04:34:27 samP: Ok 04:34:34 samP: Sure. 04:34:46 second round would be on 9/5 meeting 04:35:05 (6) Pike work Items 04:37:01 we need to re arrange these items 04:38:18 Let's mark things done with [done] tag and not completed ones with [uncomplete] and skipped to queens ones with [skipped] 04:38:31 samP: ok. 04:38:44 I will put those tags, and let's do a review on our next IRC meeting 04:39:05 I will import skipped and uncomplete items to new Queens etherpad 04:39:46 Let's have a review on 8/29 04:40:02 #topic AOB 04:40:15 AOBs? 04:40:45 if nothing, we could finish meeting bit early... 04:41:16 I don't have AOB items. 04:41:44 samP: Nothing from my side too 04:42:14 OK then, thank you all for attending to this meeting.. 04:42:22 thank you all 04:42:26 have a good day.. 04:42:26 thank you. 04:42:29 bye.. 04:42:30 Thank you all 04:42:36 #endmeeting