15:01:24 #startmeeting monasca 15:01:25 Meeting started Wed Feb 6 15:01:24 2019 UTC and is due to finish in 60 minutes. The chair is witek. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:26 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:28 The meeting name has been set to 'monasca' 15:01:33 hello everyone 15:01:45 good morning 15:01:49 hello 15:01:53 I'm in another meeting in parallel, so I might be little slow :) 15:02:22 #topic summit + ptg reminder 15:03:05 we want to hold again Monasca sessions during the next PTG 15:03:17 it will be directly after the Summit 15:05:45 I am hoping to attend. Are there scheduling options available yet? 15:06:12 no, I'll set up the etherpad next days 15:06:27 I'm guessing many teams will try to grab the earlier days closer to the summit 15:06:54 please ping your managers if you can attend 15:07:10 it's important to have your input during the PTG 15:07:37 we'll also try to set up remote conference call 15:08:28 #topic reviews 15:08:46 we have some backlog with reviews 15:09:20 https://review.openstack.org/622361 15:09:30 I have updated this one again 15:09:49 it failed on the gate during the last test again 15:10:10 and then I hopefully have found the solution 15:10:56 being the mismatch between id type in both referenced tables 15:11:27 then we have two more changes in notification engine 15:11:33 https://review.openstack.org/603157 15:11:38 https://review.openstack.org/633163 15:12:00 these are cleaning up the usage of oslo.config 15:13:05 nice to see so much work from toabctl :) 15:13:16 similar clean-up work in persister: 15:13:22 https://review.openstack.org/633381 15:13:26 hey 15:13:28 https://review.openstack.org/633229 15:14:10 and log-api: 15:14:11 https://review.openstack.org/632245 15:14:53 I see also a new change with tempest test for events-api: 15:14:54 https://review.openstack.org/599575 15:15:58 two more I wanted to mention are changes updating policy names: 15:16:16 https://review.openstack.org/#/q/status:open++branch:master+topic:policy-names 15:17:25 do you have some other needing review? 15:19:11 #topic open stage 15:19:28 one question about naming 15:19:48 I saw that there is now a monasca-status command from the monasca-api git repo 15:20:02 shouldn't that be monasca-api-status? Or what happens if we get the same for monasca-log-api? 15:20:10 or are there plans to merge both projects? 15:20:21 It is part of the upgrade check community goal 15:20:44 yes. I know. I'm asking about the name of the "binary" 15:20:46 The convention defined by the community goal was to have an overall -status name 15:21:01 and yes, there is a plan to merge the APIs into one 15:21:27 ok. thanks! 15:21:29 so monasca-status isn't limited to just the api or log-api 15:22:10 if you think of other things the monasca-status could/should do besides upgrade-check, feel free to suggest them. :) 15:22:49 yes, the idea is to add useful checks to that command 15:23:22 to make upgrades smoothier :) 15:24:27 other questions? 15:24:45 one minor commit we can review - https://review.openstack.org/#/c/628272/ 15:25:28 thanks, added myself 15:26:03 if there's nothing else, I'll wrap up now 15:26:21 thanks for joining 15:26:26 see you next time 15:26:31 see you 15:26:36 #endmeeting