14:01:01 <rhochmuth> #startmeeting monasca
14:01:02 <openstack> Meeting started Wed Sep  6 14:01:01 2017 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:03 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:01:06 <openstack> The meeting name has been set to 'monasca'
14:01:09 <rhochmuth> o/
14:01:12 <Dobroslaw_> hello
14:01:14 <cbellucci> o/
14:01:16 <koji> o/
14:01:31 <rhochmuth> hi everyone
14:01:38 <joadavis> o/
14:01:45 <rhochmuth> witek is out today
14:01:58 <rhochmuth> so, it guess it is back to me this week
14:02:13 <rhochmuth> no agenda items have been posted
14:03:02 <rhochmuth> do we have some items to add to the agenda
14:03:11 <rhochmuth> possibly some updates from last week
14:04:00 <tobiajo> hi
14:04:05 <BeHavee> hi
14:04:09 <joadavis> I've just got a thought about the mid-cycle meeting.  I think those of us involved in Ceilosca would like to join if it isn't going to derail things
14:04:20 <rhochmuth> hi tomiago and BeHavee
14:04:29 <nseyvet> hello
14:04:43 <rhochmuth> joadavis: sounds like a good topic to discuss
14:04:43 <joe_w> hello
14:04:51 <rhochmuth> i've been out of the loop on that for a while
14:05:23 <nseyvet> I would like to discuss updating the kafka-> persister python library
14:05:34 <joadavis> Yeah, we definitely could use some discussion around architecture going forward, especially as Ceilometer project is pivoting to be very Gnocchi directed
14:06:40 <joadavis> I hope we can continue to improve metering related functions for Monasca users
14:06:48 <sc> hi
14:06:56 <rhochmuth> ok, so let's start with the kafka library first
14:07:06 <rhochmuth> #topic afka-> persister python library
14:07:28 <rhochmuth> nseyvet: you have the floor
14:07:55 <nseyvet> First, I would liek to know how to go forward and submit updating the python kafka library to a later version?
14:08:17 <nseyvet> It seems to be using an old version, with offset manipulations in ZK atm
14:08:36 <nseyvet> we would like to move it forward to kafka 0.10+
14:08:41 <rhochmuth> there were problems with the newer versions with stability and performance
14:08:52 <rhochmuth> i don't know if those have been resolved
14:08:58 <rhochmuth> have you tests
14:09:22 <nseyvet> someone in our team made a quick benchmark and performance was about 20% higher
14:09:37 <nseyvet> but we have not tested for stability
14:09:52 <Dobroslaw_> with pure Python implementation or using librdkafka?
14:09:58 <rhochmuth> we basically forked the library in monasca-common
14:11:01 <rhochmuth> because upstream openstack wanted to use the newever version and it wouldn't work for us
14:11:29 <Dobroslaw_> also one person in our team was looking shortly on upgrading it and he said that going 0.9 to 2.6 is like using completely new library...
14:11:44 <nseyvet> yes, that is also our finding
14:12:15 <nseyvet> so, how to move forward?  Create a "specifications"?
14:12:42 <nseyvet> I dont have the exact info as to which lib was looked at.. sorry
14:12:53 <rhochmuth> creating a specification would be a good start
14:13:38 <Dobroslaw_> if newer Pykafka is so different then maybe https://github.com/confluentinc/confluent-kafka-python also would be good to look at
14:13:56 <rhochmuth> i think the confluent library is a good one to use
14:14:07 <nseyvet> Ok. I take note. And I agree on the confluent one.
14:14:14 <rhochmuth> however, the problem is that is requires C code to be built as well
14:14:29 <nseyvet> so we will submit a specification.
14:14:33 <rhochmuth> so install/deployment is more complicated
14:14:47 <Dobroslaw_> hmmm, true
14:15:01 <rhochmuth> there was another library that joe keen was looking at
14:15:44 <rhochmuth> forgot the name of it
14:15:47 <Dobroslaw_> newer PyKafka have two backends: pure Python and faster librdkafka
14:15:53 <rhochmuth> that is the one
14:16:01 <rhochmuth> thx Dobroslaw_
14:16:03 <Dobroslaw_> (same as in confluent-kafka-python)
14:16:51 <nseyvet> are there any C dependencies in the python persister today?  Because when I look at the docker images, it lists some
14:17:58 <nseyvet> like "linux-headers libxml2-dev libxslt-dev" etc
14:19:19 <akiraY> hi, all
14:21:00 <nseyvet> We will submit a specification.  Then we see.
14:21:06 <nseyvet> thanks for info.
14:21:15 <rhochmuth> ok
14:21:27 <rhochmuth> thanks nseyvet
14:22:23 <rhochmuth> what should the next topic be
14:22:30 <tobiajo> maybe go over to pykafka in monasca-common? we could set pure python as default, and make it possible to use librdkafka if one want
14:23:24 <rhochmuth> tobiajo: good idea, i think that is similar to what joe proposed
14:23:26 <rhochmuth> too
14:25:04 <nseyvet> Ceilosca?
14:25:12 <rhochmuth> #topic ceilosca
14:25:40 <joadavis> Sure. :)  Do we want to put a slice of time on the midcycle agenda for Ceilosca?
14:26:53 <rhochmuth> i lost my link to the etherpad for the mid cycle
14:27:04 <joadavis> some topics could include changes in Ceilometer project (like deprecation of Ceilometer API), other sources of metrics (like Prometheus) that could be funneled in to Monasca...
14:27:13 <rhochmuth> but, yes, someone should add that as a agenda item and propose a date
14:27:16 <joadavis> Try https://etherpad.openstack.org/p/monasca_queens_midcycle
14:27:24 <rhochmuth> thx
14:27:49 <joadavis> ... and other things like events and alarms that could be run through Monasca to match any feature set from the Telemetry project.
14:28:40 <efoley> Are there any attendees from the telemetry project?
14:29:16 <joadavis> I doubt any telemetry project folks are planning to attend the virtual mid-cycle for Monasca
14:30:12 <efoley> If you're proposing changes to align/match their metrics/events, wouldn't it make sense to invite them?
14:31:07 <joadavis> Ceilosca already matches the metrics (by matches I mean funnels ceilometer metrics into Monasca).  Monasca already has some work around events.
14:31:46 <joadavis> We can invite them, I just doubt they have much interest
14:32:25 <efoley> They might be interested in the discussion around TSDB support, as gnocchi fits the bill.
14:32:47 <joadavis> <biting my tongue>
14:33:16 <rhochmuth> sure, i would be interested in a gnocchi discussion
14:33:45 <rhochmuth> there were some questions around metrics injest rates and query performance
14:36:02 <joadavis> Is there a right way to invite them?  Open post to #openstack-telemetry?
14:40:28 <nseyvet> how different are the telemetry vs monasca objectives?
14:41:20 <rhochmuth> is anyone here that can help to answer/clarify
14:42:17 <efoley> I can't anyway.
14:42:33 <efoley> Try a post to the mailing list to invite the telemetry team
14:43:30 <rhochmuth> thx efoley
14:43:31 <joadavis> I don't think I'm qualified to articulate it. :)  I have opinions but I'd just get myself in trouble
14:43:46 <rhochmuth> i'll leave that to witek to handle i guess
14:44:12 <joadavis> I'll take an action item to come up with a focused item or two re: Ceilometer for the mid cycle meetings
14:44:22 <sc> witek is off this week IIRC
14:44:29 <rhochmuth> thx joadavis
14:47:05 <rhochmuth> so are there more topics to address for today
14:47:13 <rhochmuth> tsdb updates
14:47:14 <rhochmuth> ?
14:47:25 <akiraYo> griddb
14:48:51 <rhochmuth> akiraYo: sure
14:49:05 <rhochmuth> #topic griddb
14:49:11 <akiraYo> I'm working to improve DB healthcheck.
14:49:39 <rhochmuth> thx, is that the refactoring that i requested
14:50:00 <akiraYo> yes.
14:50:18 <rhochmuth> great, i'll take a look
14:51:26 <akiraYo> thx
14:51:53 <rhochmuth> akiraYo: did you poast a new patch set?
14:51:59 <rhochmuth> i don't see one listed
14:52:12 <akiraYo> not yet
14:52:26 <rhochmuth> are you planning too?
14:52:31 <akiraYo> improving unittests
14:52:37 <rhochmuth> thx
14:52:50 <rhochmuth> i thought you had posted already, just clarifying
14:53:37 <akiraYo> ok.
14:55:12 <akiraYo> and I got mails about requirements of TSDB
14:56:16 <rhochmuth> so, i'm going to have to close the meeting down shortly
14:56:41 <rhochmuth> any final comments or requests?
14:57:13 <nseyvet> all good. ty
14:57:19 <joadavis> have a nice day
14:57:38 <rhochmuth> thanks everyone
14:57:39 <Dobroslaw_> thank you
14:57:47 <rhochmuth> #endmeeting