15:00:04 <rhochmuth> #startmeeting monasca
15:00:06 <openstack> Meeting started Wed Dec 14 15:00:04 2016 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:07 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:08 <rhochmuth> o/
15:00:10 <openstack> The meeting name has been set to 'monasca'
15:00:14 <rhochmuth> https://etherpad.openstack.org/p/monasca-team-meeting-agenda
15:00:16 <rbak> o/
15:00:20 <dirk> o/
15:00:22 <rhochmuth> Agenda for Wednesday December 14 2016 (15:00 UTC)
15:00:22 <rhochmuth> 1.	Grafana - meeting with Raintank
15:00:22 <rhochmuth> 2.	Reviews:
15:00:22 <rhochmuth> 1.	https://review.openstack.org/#/c/408813/
15:00:22 <rhochmuth> 3.	Log API future for reads
15:00:22 <rhochmuth> 4.	Can we uncap python-kafka ? http://lists.openstack.org/pipermail/openstack-dev/2016-December/108436.html
15:00:23 <rhochmuth> 5.	New version numbers for Java components https://review.openstack.org/#/q/projects:openstack/monasca+topic:version
15:00:23 <rhochmuth> 6.	Ocata 2 Milestone: 15 Dec
15:00:24 <rhochmuth> 7.	Adding Promethues features to Monasca
15:00:24 <rhochmuth> 1.	PromQL
15:00:25 <rhochmuth> 2.	Alarms and notifications
15:00:25 <rhochmuth> 1.	https://prometheus.io/docs/alerting/alertmanager/
15:00:26 <dhague> o/
15:00:26 <rhochmuth> 2.	Grouping Alerts
15:00:26 <rhochmuth> 3.	Alarm inhibition
15:00:28 <kamil> o/
15:00:31 <koji> o/
15:00:33 <hosanai> o/
15:00:35 <cbellucci> o/
15:00:39 <rhochmuth> hi everyone
15:00:57 <rhochmuth> looks like a good agenda today
15:00:59 <stevejims> hi all
15:01:07 <rhochmuth> and we have a number of people here which is great
15:01:17 <rhochmuth> i'll probably be out the next two weeks though
15:01:42 <rhochmuth> so, for next week, unless i'm at home at 8:00 AM doing nothing, i probably won't attend
15:01:55 <rhochmuth> but, you can never rule me out
15:02:05 <rhochmuth> so, someone else should start the meeting next week
15:02:25 <rhochmuth> so, let's go through the agenda
15:02:33 <rhochmuth> #topic Grafana - meeting with Raintank
15:02:41 <rbak> That's me
15:02:42 <rhochmuth> rbak: is that u
15:03:06 <rbak> Anyone who asked to be on last weeks email to Raintank may have already seen this
15:03:19 <rbak> But we've setup a meeting with them for anyone who wants to attend.
15:03:35 <rbak> It's at 1630 UTC, so half an hour after this meeting ends
15:03:56 <witek> where?
15:04:01 <rbak> I don't have the link for the the meeting yet but it should be in the email and I'll post it here once I have it.
15:04:24 <rbak> They said they would send one out to us.
15:04:30 <rhochmuth> https://plus.google.com/hangouts/_/raintank.io/openstack?hceid=ZHV0dEByYWludGFuay5pbw.pt93p3n8dpqq55i410e81c3aks
15:04:31 <dhague> Here's the link for the meeting: https://plus.google.com/hangouts/_/raintank.io/openstack?hceid=ZHV0dEByYWludGFuay5pbw.pt93p3n8dpqq55i410e81c3aks
15:04:37 <rbak> Great, thanks
15:05:35 <rbak> That's all I had.  Anyone is welcome to attend who wants to talk with them about Grafana.
15:05:49 <dhague> One thing to mention up front:
15:06:15 <rhochmuth> dhague: are we going to try and keep the kubernetes meeting after this meeting
15:06:32 <dhague> They seem to be of the mindset that openstack support will be a support burden for which they are looking for subscriptions from users (i.e. us), instead of seeing it as a contribution from us which will help their product
15:06:57 <dhague> So we may have some perusading to do, or at least compromising.
15:07:05 <rbak> Good point.
15:07:41 <rbak> I'll add that they've started talking to Charter again, so I wouldn't get hopes up but we might be able to offer some leverage there.
15:07:58 <rhochmuth> yes, they are a business
15:08:21 <bklei> o\
15:08:28 <rhochmuth> so, let's see what they say later today
15:09:06 <rhochmuth> dhague: are we still trying to meet after this meeting?
15:09:19 <dhague> rhochmuth: about the k8s meeting, jobrs rescheduled it for next week to avoid conflicts, but we could also move it to the new year if that's more convenient
15:09:32 <stevejims> If there is still resistance, would it be worth suggesting a plugin-style approach, and maintain a plugin outside grafana?
15:09:48 <rhochmuth> thanks dhague
15:09:57 <rbak> stevejims: I think they're thinking pluggable auth would be a good idea.
15:10:09 <dhague> stevejims: that would be great, except that Go doesn't really do plugins nicely
15:10:16 <stevejims> Ok, that's good
15:10:19 <rhochmuth> not sure i wanted hoppal to have to wait that long, as he is in the midst of developign his plugin
15:10:34 <rbak> Right, so I don't know how they're planning on doing the pluggable auth.
15:10:41 <rbak> We'll see what they say in the meeting.
15:11:01 <hoppalm> I can do whenever works for everyone else
15:11:10 <rhochmuth> but as far as i'm concerned to the new year is fine with me
15:11:11 <stevejims> Sounds good
15:11:18 <rhochmuth> split brain
15:11:46 <dhague> rhochmuth hoppalm: ok, I'll get jobrs to push it to the new year
15:12:12 <rhochmuth> ok, sorry for the change in plans, was hoping to resolve this
15:12:17 <dhague> summary: prometheus mtg in new year, grafana meeting in 1:15 from now
15:12:39 <rhochmuth> hoppal's promethues and kubernetes plugins are up for review if you have some comments
15:12:44 <rhochmuth> correct
15:12:48 <rhochmuth> dhague
15:13:12 <rhochmuth> #topic review https://review.openstack.org/#/c/408813/
15:13:24 <rbak> Also mine.
15:13:35 <rbak> Just wanted to get some eyes on.
15:13:46 <rbak> It's been up for a week and only one comment.
15:14:11 <rhochmuth> looks like craig has +1'd
15:14:21 <rhochmuth> and bklei
15:14:29 <rhochmuth> so, i'm assuming ready to go
15:14:30 <rbak> It's a pretty simple patch
15:14:52 <rhochmuth> if anyone else want to take a quick look and merge that would be great
15:15:02 <rhochmuth> or add comments as appropriate
15:15:26 <rhochmuth> #topic Log API future for reads
15:15:55 <stevejims> This was my addition
15:16:10 <stevejims> I was hoping to raise the topic of the future of the log API
15:16:38 <rhochmuth> hi stevejms, welcome to the monasca meeting
15:16:49 <rhochmuth> does anyone want to take a crack at this one?
15:16:51 <stevejims> Hi, thanks
15:16:52 <witek> we thought of doing this, but for now decided to implement multi-tenancy in Kibana plugin
15:16:53 <rhochmuth> if not, i can
15:17:31 <stevejims> We have looked at the Kibana plugin but it looks like the MT was reverted?
15:17:32 <rhochmuth> so, obviousely we would like to see this added
15:17:36 <rhochmuth> it isn't trivial
15:17:59 <rhochmuth> do to the prioritues and resources we don't have any immediate plans to add support for reading logs from the log api
15:18:15 <witek> we are in the process of adding this to devstack plugin
15:18:47 <witek> https://github.com/FujitsuEnablingSoftwareTechnologyGmbH/fts-keystone/tree/multitenancy
15:19:02 <witek> the plan is:
15:19:21 <witek> * update tempest tests for logs
15:19:34 <witek> * create new repo for plugin
15:19:42 <witek> * include in devstack-plugin
15:20:25 <stevejims> Sounds promising - Would be there be interest in proposals for an API, if we (I) could put some time into it?
15:21:00 <stevejims> The use case would be allowing logs to be displayed in Grafana, so quite focused
15:21:08 <rhochmuth> i think the answer is yes, we are always interested in developers becoming involved with the project
15:21:31 <rhochmuth> but, we also need to coordinate
15:21:35 <rhochmuth> witek?
15:22:00 <witek> sure
15:22:14 <rhochmuth> Also, I want to mention, if we ever get to adding reads to the log api, we would want to look at the Searchlight for code reuse/inspiration…
15:22:15 <witek> we can work together on API proposal
15:23:09 <rhochmuth> Searchlight has an api for quierying ES, that handle multi-tenancy, filtering of in/out bound queries, and making sure that queries are secure
15:23:29 <stevejims> Sounds good - happy to coordinate on a proposal
15:23:42 <rhochmuth> stevejims: so my suggestion would be to submit a blueprint first
15:23:50 <rhochmuth> along with some API proposals
15:24:06 <rhochmuth> i'm wondering if we want to try and use storyboard for something like this, rather than launchpad
15:24:37 <witek> good idea
15:24:42 <rhochmuth> then we can review either in weekly meetings or in a separate time/place
15:24:49 <rhochmuth> witek: storyboard?
15:24:51 <stevejims> Sure
15:24:53 <witek> yes
15:25:13 <rhochmuth> stevejims: are you familiar with storyboard?
15:25:29 <stevejims> Afraid not but can get familiar
15:25:43 <rhochmuth> https://storyboard.openstack.org/#!/page/about
15:26:15 <rhochmuth> we need to add a monasca project to it i think
15:26:18 <rhochmuth> hopefully that isn't hard
15:26:46 <rhochmuth> so let's close on this for now
15:26:54 <rhochmuth> i'll assume we'll give storyboard a try
15:27:39 <rhochmuth> stevejims, looks like you have approval to get started on a proposal and review with the team
15:27:40 <stevejims> OK grand - thanks all
15:27:56 <rhochmuth> where do you work, btw?
15:28:36 <rhochmuth> #topic Can we uncap python-kafka
15:28:51 <rhochmuth> http://lists.openstack.org/pipermail/openstack-dev/2016-December/108436.html
15:28:51 <witek> I have put that one
15:29:00 <stevejims> Company is called StackHPC, we primarily do consulting work for Cambridge University on OpenStack
15:29:17 <rhochmuth> cool, thanks
15:29:57 <witek> there is some pressure from requirements team and oslo.messaging to uncap python-kafka
15:30:25 <rhochmuth> my understanding after talking to joe about this is that it isn't a great situation
15:30:41 <rhochmuth> they want to bump the kafka library to the latest one
15:30:50 <rhochmuth> however, it only supports async
15:31:08 <rhochmuth> there is a SimpleConsumer, that is depreated in the library, that they want us to move to
15:31:24 <rhochmuth> but, there are a number of issues outstanding in SimpleConsumer too
15:31:41 <rhochmuth> i guess there is a SimpleProducer too
15:31:55 <rhochmuth> i would like to free the openstack oslo folks up too
15:32:17 <rhochmuth> but, this change puts us in a potentially bad situation
15:32:45 <rhochmuth> as an alternative, we were thinking about moving to the confluent library
15:33:05 <rhochmuth> then we could get out of everyone's way
15:33:34 <rhochmuth> thoughts?
15:33:45 <witek> confluent is not in global-requirements though, right?
15:33:57 <rhochmuth> right
15:34:08 <rhochmuth> we would have to get that added first
15:34:17 <rhochmuth> then we could move
15:34:32 <witek> do they support sync?
15:34:53 <rhochmuth> i don't think so, but i'm not positive
15:35:16 <rhochmuth> so, it isn't exactly a trivial change
15:35:57 <rhochmuth> joe is out for the rest of the year i believe
15:36:06 <rhochmuth> so, i can't check with him
15:37:16 <rhochmuth> is there anything else to discuss on this right now
15:37:31 <witek> ok, thanks for explaining, it seems complicated at that point
15:37:38 <rhochmuth> yes, it is
15:38:13 <rhochmuth> so, let's get back to this issue in the new year
15:38:21 <rhochmuth> #topic New version numbers for Java components
15:38:31 <rhochmuth> https://review.openstack.org/#/q/projects:openstack/monasca+topic:version
15:38:44 <witek> could we bump the version numbers of Java components?
15:39:03 <rhochmuth> sure
15:39:15 <bklei> ok by us at charter
15:39:34 <witek> the tests should be passing if we merge in a right sequence
15:39:53 <rhochmuth> so, if you want to shepherd it through that would be great
15:40:21 <rhochmuth> monasca-common needs to go first i guess
15:40:27 <witek> yes
15:41:09 <rhochmuth> ok, i guess feel free to +2
15:41:12 <witek> then thresh and persister
15:41:26 <rhochmuth> right
15:42:28 <rhochmuth> #topic Ocata 2 Milestone: 15 Dec
15:42:39 <witek> just a reminder
15:42:41 <rhochmuth> omg
15:42:44 <witek> :)
15:42:46 <rhochmuth> already
15:43:03 <witek> I'll create tags
15:43:16 <rhochmuth> sounds great
15:44:12 <rhochmuth> #topic Adding Promethues features to Monasca
15:44:21 <rhochmuth> this is my topic
15:44:41 <rhochmuth> just wondering if anyone else had any thoughts or ideas on this
15:45:04 <rhochmuth> i have a little prometheus envy lately
15:45:47 <rhochmuth> but, at the same time, i think we have some compelling features, functionality and architecture with monasca
15:46:21 <rhochmuth> the prometheus community is starting to look at areas like scale, clustering, monitoring-as-a-service
15:46:22 <dhague> it seems like everybody is getting in on the alerting act: prometheus, ceilometer, grafana, ...
15:46:48 <rhochmuth> yes, there is a huge amount of overlap
15:48:00 <rhochmuth> anyway, i'm looking at this area a bit, and trying to understand what could be or should be done
15:48:07 <rhochmuth> just wanted to mention that
15:48:40 <jamesgu> leverage ro replacement?
15:48:43 <jamesgu> or
15:49:00 <rhochmuth> i think understand first
15:49:15 <dhague> we have a working student who is doing his thesis on monitoring our "converged cloud" openstack-on-kubernetes setup. His report should be available early in the new year, and hopefully we can share it here. It covers prometheus and monasca, among other things
15:49:30 <rhochmuth> my first thought is to try and add features to monasca to remain parity
15:49:37 <rhochmuth> thanks dhague
15:49:54 <rhochmuth> i also did a comparison, but unfortunatly on the internal wiki
15:49:58 <notq> a diff of the features would be useful.
15:50:10 <rhochmuth> so, i'll try and get that published on the monasca public wiki
15:50:44 <stevejims> When I have talked to people about Prometheus the thing they like the most is the simple nature of it, but that is also it's biggest issue (scalability)
15:50:45 <jamesgu> thanks rhochmuth
15:51:06 <rhochmuth> i was going to mention that there are two companies, weaveworks and digitalocean that have leverage promethues
15:51:12 <rhochmuth> https://github.com/digitalocean/vulcan
15:51:34 <rhochmuth> https://github.com/weaveworks/cortex
15:52:37 <rhochmuth> ok, enough on that topic
15:52:48 <rhochmuth> #topic open floor
15:54:52 <rhochmuth> i guess no other topics
15:54:57 <rhochmuth> so, i'll end the meeting
15:55:03 <rhochmuth> thanks everyone
15:55:10 <dhague> thanks
15:55:12 <rhochmuth> see some of you in a few minutes
15:55:25 <witek> thanks
15:55:28 <rhochmuth> #endmeeting