15:00:33 <chaconpiza> #startmeeting monasca
15:00:33 <openstack> Meeting started Wed Aug 21 15:00:33 2019 UTC and is due to finish in 60 minutes.  The chair is chaconpiza. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:34 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:37 <openstack> The meeting name has been set to 'monasca'
15:00:57 <joadavis> good morning
15:01:00 <Dobroslaw> Hi
15:01:08 <dougsz> hey all
15:01:30 <sum12> Hello
15:01:31 <Wasaac> o/
15:01:32 <chaconpiza> Hi, good morning/afternoon
15:02:13 <chaconpiza> The agenda for today
15:02:17 <chaconpiza> https://etherpad.openstack.org/p/monasca-team-meeting-agenda
15:03:17 <chaconpiza> #topic Faus as core for Monasca-Thresh
15:03:22 <chaconpiza> *Faust
15:03:51 <chaconpiza> Welcome sum12, would you like to share your results about your investigation on Faust?
15:04:12 <sum12> sure
15:04:55 <sum12> There is a limitation which is no where mentioned in the documentation
15:05:38 <sum12> And also if this is really a limitation or bug is not known
15:06:15 <sum12> it is around table creation. Faust tables cannot be created dyncamically
15:06:48 <sum12> I have created a PR to get around it
15:07:12 <dougsz> tables are used for alarm definitions?
15:07:52 <sum12> to be precise: to  store metrics corresponding to every sub-expression
15:08:10 <chaconpiza> As table you mean a Kafka-topic ?
15:08:59 <sum12> table a faust datastore, but yes it is backed up a kafka-topic and rocksdb storage
15:10:44 <sum12> I will need to rethink the implementation around this limitation and am waiting for witek to be back.
15:11:56 <dougsz> Do they have a mailing list or chat where you can get some feedback from the Faust devs?
15:11:59 <chaconpiza> I tried with two consumers, each starts and faust's application
15:12:32 <chaconpiza> the first with a hopping window 10,5 and second with hopping windows 4,2
15:13:01 <sum12> they do have slack channel, but its mostly populated with long time faust users
15:13:27 <chaconpiza> for that I used the --without-web to avoid that each app will start a webserver in an specific port
15:15:11 <chaconpiza> sum12, are you using kafka 2.3 or an older one?
15:15:33 <sum12> chaconpiza, its older version
15:17:18 <dougsz> sum12: Just thinking they could shed some light on whether it's a limitation or bug
15:18:02 <sum12> oops, I am on 2.3 version
15:19:14 <sum12> I am pretty sure that this has to do with faust and not with kafka
15:19:14 <chaconpiza> I see, I'm able to start the faust's example of Witek in 2.3, but not in an older one like in monasca-devstack
15:19:37 <chaconpiza> yes, it should be other issue.
15:20:47 <chaconpiza> All right, I will contact you this week or next week to share my findings in detail.
15:21:17 <sum12> the other problem is : even if tables could be created dynamically, to support the table correctly a kafka rebalance will be required and that is pretty expensive in time
15:21:45 <sum12> Thanks chaconpiza
15:23:09 <chaconpiza> Ok, is there other point to mention about your investigation?
15:23:47 <sum12> I thk
15:24:09 <sum12> I think thats it
15:24:23 <chaconpiza> #topic Q&A
15:24:46 <chaconpiza> From mbindlish
15:24:51 <chaconpiza> "Do we have CLI commands for monasca logging...if yes can anybody please share that?"
15:25:18 <chaconpiza> As far as I know, Monasca-CLI handles only the metrics part.
15:25:41 <chaconpiza> Am I right?
15:26:57 <chaconpiza> But in other hand, it is possible to send http requests to elasticsearch using curl to get some info about monasca-log part.
15:27:25 <Dobroslaw> I think so
15:30:41 <dougsz> chaconpiza, that's correct, log API is basically write only
15:31:14 <dougsz> we have a patch to add query support for logs, which could work with the CLI, but not merged yet
15:31:32 <chaconpiza> it sounds good
15:32:48 <chaconpiza> #topic monasca.io
15:33:46 <joadavis> yes, quite a story there. I don't have an update over the last couple days
15:33:47 <chaconpiza> monasca.io still not available,
15:34:21 <chaconpiza> could it be because of this commit?
15:34:24 <chaconpiza> https://github.com/monasca/monasca.github.io/commit/cce1fca108f26d09e595a92d7f4038e4da6d9806
15:34:29 <chaconpiza> I am not sure
15:34:50 <joadavis> It appears to be because the domain registration expired
15:35:09 <joadavis> SUSE and HPE have talked a little through email about trying to get it renewed
15:35:59 <joadavis> There is some question of copyright notices on the HPE side - Tim is asking about that through channels but doesnt expect an answer until the 25th or so
15:37:05 <joadavis> Witek and I have asked if SUSE could pay the $30 and change to renew the domain, but the billing for that requires jumping through some hoops
15:37:48 <chaconpiza> All right, thanks for the info joadavis
15:37:50 <joadavis> chaconpiza: I think the commit is an attempt to work around the expiration
15:38:16 <joadavis> wish I had a complete answer, as I know this has broken a few people's helm chart use
15:38:41 <joadavis> the monasca.github.io hosting of the same files does work, but some urls are encoded in the helm charts
15:40:21 <chaconpiza> Ok, is there other topic you would like to discuss today?
15:44:06 <chaconpiza> Then I wish you a good morning/afternoon. See you next week.
15:44:28 <dougsz> thanks all, bye
15:44:55 <joadavis> thanks
15:45:15 <chaconpiza> #endmeeting