15:00:49 #startmeeting monasca 15:00:50 Meeting started Wed Nov 28 15:00:49 2018 UTC and is due to finish in 60 minutes. The chair is witek. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:51 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:53 The meeting name has been set to 'monasca' 15:01:07 Hello everyone 15:01:11 \o/ 15:01:18 Stefano! :) 15:01:20 hey all 15:01:25 welcome sc! 15:01:29 I got released from AWS 15:01:35 haha 15:01:56 nice to see you again 15:02:30 let's start 15:02:43 agenda is as usual here: 15:02:48 https://etherpad.openstack.org/p/monasca-team-meeting-agenda 15:02:59 Hi 15:03:08 hi Fdaisuke_ 15:03:17 #topic CI updates 15:03:30 two updates 15:03:57 Adrian has finished the work migrating the CI configuration to native Zuul3 15:04:10 for tempest tests jobs 15:04:19 both in monasca-api and monasca-log-api 15:05:01 it's now more flexible to use with the new Zuul version 15:05:20 and also `compatible` with the rest of OpenStack CI 15:05:37 nice work 15:06:06 we're using now `devstack-tempest` parent job which is defined openstack infra 15:06:48 the second update is about upgrading devstack to Ubuntu Bionic 15:07:28 infra plans on migrating all the tempest tests to run on Bionic in December 15:08:18 I have tested devstack locally and after fixing some minor problems everything seems to work fine 15:08:25 the devstack readme page still indicates 16.04 as the most supported version. Hopefully that will update as well 15:08:54 I need to rebuild my devstack anyway, I'll give it a try also 15:08:56 you mean devstack or our devstack plugin? 15:09:08 the main devstack repo 15:09:15 I see 15:09:23 witek: why openjdk-8-jre-headless? what's missing in openjdk-8-jdk? 15:10:08 for some reason it installed openjdk-11-jre-headless next to 8 in my local env 15:10:24 11 being default 15:10:47 11 is default for bionic release, I think 15:11:21 yes, but I haven't installed it myself, must have been pulled in by some dependency, I guess 15:11:52 so when I added `openjdk-8-jre-headless` the dependency problem was gone 15:12:32 witek: I see but still looks strange, did you try openjdk-11-jdk? 15:13:17 no, I think upgrading to Java 11 is a bigger thing 15:14:09 Yes, and you don't what to patch java code, aren't you? 15:14:49 well, no if there's no direct reason 15:15:21 OK, we'll survive with one more package :-) 15:16:38 well, I think `openjdk-8-jre-headless` was installed anyway in Xenial already, just not explicitly 15:17:11 I'll check it once again 15:17:41 FWIW, kolla provides bionic and we're using openjdk-8-jre-headless there: https://github.com/openstack/kolla/blob/master/docker/storm/Dockerfile.j2#L16 15:18:52 thanks, feel free to comment in review 15:19:17 #topic notification plugins 15:19:41 dougsz: that's yours, right? 15:20:10 yeah - so there are a lot of patches sitting around for notification 15:20:25 these ones I think are the highest in the chain 15:21:01 yes, they're up for quite some while now already 15:21:36 There are some bug fixes which depend on these getting merged. 15:21:56 Around configuration of plugins. 15:22:23 the only missing puzzle is using Alembic commandline tool in devstack plugin 15:22:45 https://storyboard.openstack.org/#!/story/2001654 15:22:51 yes, you're right - saw your comment. 15:23:02 we still use the SQL script there 15:23:12 Unfortunately I'm not a devstack user - but I suppose I could try and take a look sometime. 15:24:41 So I guess we just need reviews on these patches. 15:25:19 thanks for adding unit tests on fingerprinting 15:25:43 looks good 15:25:46 np - it was worth it - I found a python 3 bug 15:26:00 Just looking, I think I need to update the commit ID - I can do that later. 15:26:23 But if anyone can see anything else which needs doing please let me know,. 15:27:04 if you need help with alembic in devstack, please ping in #openstack-monasca 15:27:32 ok, thanks. Do you see that as something blocking the existing patches? 15:29:00 it's not really tested in tempest tests, so I guess we can add alembic later 15:29:13 but we should definitely do this 15:29:29 yeah - I've switched over in Kolla and it's a really nice feature 15:30:16 any other comments? 15:30:53 #topic specs 15:31:07 https://review.openstack.org/583803 15:31:44 dougsz has posted some questions in review 15:31:53 and I added my comments 15:32:00 yes, thanks for the comments. I haven't tried to incorporate them yet 15:32:17 The point about validation is a good one 15:32:48 but I think the efficiency of going straight to kafka is why we wanted to shortcut the events api 15:32:51 agree, it would be easier if all the requests go through the single API 15:33:05 But we can use the same validation code in the Events Listener when it is implemented 15:34:00 dougsz: what do you think? 15:34:47 Just wondering how this fits in with merging APIs 15:35:04 The validation code would live in monasca-common? 15:35:11 already does 15:35:17 no, monasca-api 15:35:28 I mean, after merge in monasca-api 15:35:45 and event-listener also 15:36:13 Ah I see. 15:36:35 yes, sorry, I was starting to merge things in my head already 15:37:00 So the event listener would run as a separate service the the Monasca API? 15:37:08 *to the 15:37:24 yes, but reusing the code 15:39:42 Just wondering if it should have it's own repo but import the validation code from the Monasca API 15:41:23 won't we end up with the same issues we have with monasca-common? 15:42:24 Yeah - that is a disadvantage. 15:43:03 OK, let's make another round on that spec this week 15:43:28 is that OK 15:43:29 ? 15:43:33 I'll take some time this afternoon and incorporate revisions 15:43:33 Sounds good to me 15:43:49 thanks joadavis and dougsz ! 15:44:11 thanks to you both, it'll be a very nice feature 15:44:35 I think so too 15:44:45 https://review.openstack.org/609055 15:45:34 I have moved the spec to a different dictionary and made small updates 15:45:52 I think it's in a good shape already 15:46:49 thanks for tweaking it 15:47:26 that's all from my side 15:47:36 do you have anything else? 15:47:51 Not from me 15:47:57 nor from me 15:48:43 Fdaisuke_: how is the progress on monasca-analytics? 15:49:44 dougsz: Feeling sorry for Fdaisuke_ that it's gone midnight 15:50:10 yes, not a good meeting time for Japan 15:50:45 anyway, please keep us updated if you have any news or problems 15:50:59 thanks everyone for today 15:51:04 and see you next week 15:51:05 thanks all 15:51:48 #endmeeting