15:00:28 <rhochmuth> #startmeeting monasca
15:00:29 <openstack> Meeting started Wed Sep 14 15:00:28 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:30 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:33 <openstack> The meeting name has been set to 'monasca'
15:00:33 <rhochmuth> o/
15:00:39 <igorn> o/
15:00:42 <koji> o/
15:00:49 <rhochmuth> https://etherpad.openstack.org/p/monasca-team-meeting-agenda
15:01:05 <tomasztrebski> o/
15:01:10 <shinya_kwbt> o/
15:01:11 <rhochmuth> Agenda for Wednesday September 14, 2016 (15:00 UTC)
15:01:12 <rhochmuth> 1.	MT for logging with Kibana plugin
15:01:12 <rhochmuth> 1.	blueprint => https://blueprints.launchpad.net/monasca/+spec/mt-in-kibana
15:01:12 <rhochmuth> 2.	Reviews
15:01:12 <rhochmuth> 1.	https://review.openstack.org/#/c/350470/
15:01:12 <kamil_> o/
15:01:12 <rhochmuth> 2.	https://review.openstack.org/#/c/286782/ - bug fix ?
15:01:24 <tomasztrebski> Fujitsu's agenda...
15:01:30 <tomasztrebski> :P
15:01:35 <rhochmuth> After last weeks killer agenda, this week is looking rather light
15:01:37 <witek> hello
15:01:49 <rhochmuth> hello everyone
15:02:05 <rhochmuth> so, does anyone have any open commentary
15:02:09 <rbak> o/
15:02:16 <rhochmuth> logistical issues
15:02:21 <rhochmuth> …
15:02:23 <hosanai> o/
15:02:26 <bklei> o/
15:02:46 <tomasztrebski> road next to my apartment ceased to exist if that account for logistical issue...
15:02:54 <rhochmuth> One thing I should mention is that the PTL candidacy/elections are coming up
15:03:24 <rhochmuth> tomasztrebski: hopefully it will be put back
15:03:33 <witek> rhochmuth: do you candidate? ;)
15:03:41 <tomasztrebski> noob question - who's PTL ?
15:03:55 <larissabraz> o/
15:03:58 <rhochmuth> witek: i'll put my name in again
15:04:06 <tomasztrebski> someone important ? very important ? or just representative like queen of England ?
15:04:16 <witek> project technical lead
15:04:25 <rhochmuth> tomasztrebski: queen of England
15:04:30 <rhochmuth> :-)
15:05:05 <witek> what's the procedure?
15:05:40 <rhochmuth> in the openstack/elections repo add your candidacy
15:05:48 <rhochmuth> if there is more than one, there is a vote
15:06:08 <rhochmuth> there is an official doc in the openstack wiki somewhere
15:06:14 <rhochmuth> but i dont' have it right now
15:06:35 <rhochmuth> i can send to you later
15:06:57 <rhochmuth> shall we start then?
15:07:05 <witek> yes, please
15:07:20 <rhochmuth> #topic MT for logging with Kibana plugin
15:07:35 <tomasztrebski> ok, so it's on us
15:07:38 <rhochmuth> blueprint => https://blueprints.launchpad.net/monasca/+spec/mt-in-kibana
15:07:46 <witek> we would like to propose multi-tenancy solution for logging
15:08:14 <witek> we save tenant-id in elasticsearch index already
15:08:17 <rhochmuth> so, what is involved?
15:08:25 <rhochmuth> correct, tenant-id is saved
15:08:34 <rhochmuth> along with dimensions and the log message
15:08:47 <witek> well
15:08:57 <witek> index name has the tennant-id
15:09:09 <tomasztrebski> that's part of the data of single project - so it's implicitly involved here
15:09:20 <witek> so you even don't have to read the fields
15:09:56 <witek> the proposal is to make it with kibana plugin
15:10:12 <witek> we already have authorisation plugin for kibana
15:10:43 <witek> now we extend the plugin to filter indices and save project specific data
15:11:31 <witek> some questions to that?
15:11:33 <rhochmuth> so, this goes back to the original arch diagrams showing the kibana plugin, correct?
15:12:11 <witek> yes, kibana sends query requests to ES
15:12:47 <rhochmuth> so, scoping the queries to return only the relevant data for a tenant
15:13:17 <witek> I think it allows quering only specific indices, am I right tomasztrebski ?
15:13:26 <rhochmuth> as well as being able to login to Kibana via Keystone authentication, similar to maybe what was done with Grafana
15:13:40 <tomasztrebski> queries are scoped to the single project retrieved from token
15:13:45 <witek> similar to Grafana1
15:14:52 <tomasztrebski> that scope goes to entities like actual data, dashboards and visualizations
15:14:59 <rhochmuth> would this plugin be hosted as part of the monasca repos in openstack
15:15:10 <tomasztrebski> because kibana stores those too in elasticsearch
15:15:12 <rhochmuth> or part of the Kibana repos
15:15:20 <witek> rhochmuth: that is one question we wanted to ask
15:15:23 <tomasztrebski> we would like to have this as openstack project
15:15:39 <rhochmuth> is that how the other kibana plugins are done
15:15:47 <witek> there are no official Kibana plugin repos
15:15:52 <tomasztrebski> we cannot have this as kibana plugin because officially kibana does not support plugins as it is beatufilly presented in one of the readme files
15:15:55 <witek> AFAIK
15:15:56 <rhochmuth> we've already done this for the monasca-grafana-plugin repo
15:16:21 <rhochmuth> so basically a monasca-kibana-plugin repo
15:16:29 <rhochmuth> i thoguht kibana was adding the plugin capability
15:16:38 <rhochmuth> is that still in progress?
15:16:39 <witek> it would be great to have it @openstack
15:17:06 <witek> rhochmuth: yes, kibana has plugin capability, but does not support any plugins officially
15:17:13 <tomasztrebski> they have framework to do this, but do not recommend writing custom plugins because framework is likely to changef from version to version
15:17:27 <tomasztrebski> I mean, that's their statement I read somewhere
15:17:34 <rhochmuth> so, if the kibana way is similar to the grafana way, where a plugin lives outside of the project, then i think hosting it in openstack makes sense
15:17:59 <rhochmuth> so, in that case we would have to keep up with Kibana's changes
15:18:12 <rhochmuth> i'm assuming they would lock down on the plugin interface/api at some point
15:18:29 <tomasztrebski> check this => https://github.com/elastic/kibana/blob/v4.5.1/src/plugins/README.txt :P
15:19:15 <rhochmuth> well, i don't see any alternative, other than re-writing plugins as they change
15:19:23 <rhochmuth> hopefully, they don't do something too drastic
15:20:08 <rhochmuth> even though it isn't official from Kibana, it still seems like a monasca-kibana-plugin repo, would be the correct approach
15:20:20 <rhochmuth> Kibana isn't going to allow us to merge the plugin in their repo
15:20:29 <rhochmuth> and we have to host it somewhere
15:20:32 <witek> tomasztrebski: do you have other opinion on that?
15:21:15 <tomasztrebski> well even timelion, a plugin from ELK itself, is not part of kibana repo
15:21:20 <rhochmuth> i think the hpe team that works on centralized logging would be interested in developing too
15:21:39 <rhochmuth> so timelion is in a separate github repo?
15:22:04 <tomasztrebski> https://github.com/elastic/timelion
15:22:22 <tomasztrebski> heh, it was apparently Kibana while movign forward had timelion merged
15:22:29 <rhochmuth> It says, HEADS UP: This repo is deprecated. Timelion has been merged into Kibana. File issues over at https://www.github.com/elastic/kibana
15:22:33 <tomasztrebski> maybe they've done this for Kibana 5.x
15:22:41 <tomasztrebski> it was external, installable plugin for Kibana 4.x
15:23:00 <tomasztrebski> that way I've been playing around with that
15:23:04 <rhochmuth> Are you interested in Kibana 4.X or 5.X?
15:23:09 <witek> tomasztrebski: I meant, is plugin the right aproach or would you prefer to fork kibana?
15:24:32 <witek> rhochmuth: tomasztrebski started with initial implementation as plugin
15:24:36 <tomasztrebski> no opinion on that, though Kibana 5.x comes with several UI improvements, improved builtin applications (old elasticsearch site plugins would be now kibana apps)
15:25:03 <rhochmuth> does 5.X still support plugins?
15:25:12 <tomasztrebski> but it is still in alpha stage, so we did not look into this
15:25:41 <tomasztrebski> but it should support this because of the kibana apps and plugins are mainly designed to support kibana apps AFAIK
15:26:37 <rhochmuth> maybe we should discuss with ES?
15:26:47 <rhochmuth> just to make sure that plugins will be OK
15:27:07 <rhochmuth> my guess is that they would be interested in what we are doing
15:27:19 <witek> tomasztrebski: could it be an action item for you?
15:27:32 <rhochmuth> and if we let them know, they might provide us additional info
15:28:17 <rhochmuth> and help to not make the wrong decision
15:28:22 <tomasztrebski> we can try that, I could write an issue (question) @ github informing about our intention and asking about some feedback
15:28:50 <rhochmuth> sure, that is one way, they might have an email list or irc channel that would be better
15:29:11 <rhochmuth> i can check here to see if we've every contacted them
15:29:13 <witek> or do they want to keep that functionality proprietary in Shield?
15:29:47 <rhochmuth> i don't know, but i still think it is worth a discussion with them
15:29:51 <tomasztrebski> Shield is bound to basic http + maybe some plugins, but I don't recall keystone as one of them
15:30:03 <tomasztrebski> if there are any plugins I mean
15:30:38 <rhochmuth> should we wrap-up then
15:30:56 <rhochmuth> action itmes are to learn a little more about plugins, hopefully get some feedback from ES
15:31:15 <rhochmuth> if all is OK, then we would create a monasca-kibana-plugin repo
15:31:24 <rhochmuth> step 3, write code
15:31:28 <rhochmuth> step 4 drink beer
15:31:31 <witek> sounds fine
15:31:46 <witek> rhochmuth: you forgot barbecue
15:31:55 <rhochmuth> lol
15:32:03 <tomasztrebski> ok, I will write this issue @ github asking about some stuff + add your guys (roland, witek) to this
15:32:08 <tomasztrebski> cool with that ?
15:32:12 <rhochmuth> sure
15:32:19 <rhochmuth> please send email, so i can follow
15:32:43 <rhochmuth> i can't beleive we are discussion yet another monasca repo
15:32:47 <tomasztrebski> I think you will receive notification from github ( monasca-notification plugin -> lol ) but I will wrap this up in email as well
15:32:48 <rhochmuth> you guys are killing me
15:32:52 <witek> :)
15:33:24 <tomasztrebski> I think you can take 5 additional repos ;-)
15:33:30 <tomasztrebski> before collapsing or sth :)
15:33:37 <rhochmuth> Instead of project PTL, we need Monasca Chief of Repos
15:34:15 <witek> shield: " Login and Session Management in Kibana  Shield contains a Kibana plugin that provides user authentication and session support, making it easier than ever to fully protect Kibana."
15:34:15 <rhochmuth> #topic reviews
15:34:16 <rhochmuth> https://review.openstack.org/#/c/350470/
15:34:41 <rhochmuth> so, i see craig's been working on this with you
15:35:04 <rhochmuth> but, he hasnt' commented recently
15:35:12 <rhochmuth> should i ping him
15:35:28 <tomasztrebski> mhm, we already have newer kafka, looks great btw, and that agent's stuff from this review would help us a bit
15:35:42 <tomasztrebski> if you'd be so kind, that'd be great
15:35:47 <rhochmuth> ok, i'll do that
15:35:52 <rhochmuth> we have a planning session today
15:35:54 <rhochmuth> in hpe
15:36:00 <rhochmuth> i'll mention that review too
15:36:28 <rhochmuth> perhaps Joe Keen too
15:36:30 <tomasztrebski> + think about upgrading kafka in devstack, there's one feature in newer kafka that might be interesting from MT POV, or limiting access to kafka in general
15:36:46 <rhochmuth> upgrade to 10.X
15:36:48 <rhochmuth> ?
15:37:03 <tomasztrebski> right now to 0.9, kafka-python won't work with kafka 0.10
15:37:27 <tomasztrebski> at least it says that client currently available in global requirements works only with kafka 0.9.x AFAIR
15:37:51 <tomasztrebski> if openstack goes up with this I suspect we will need to upgrade kafka + monasca-common
15:37:56 <tomasztrebski> up to kafka 0.10.x
15:38:28 <rhochmuth> well, unfortuatley, we are the one's blocking the upgrade becayse so far the latest python kafka client has got some problems
15:39:05 <rhochmuth> assuming that upgrade occurs, then we can move to kafka 10
15:39:13 <tomasztrebski> if there are issues, I don't think nobody wants to break stuff up, me in the first place
15:39:30 <rhochmuth> right
15:39:57 <rhochmuth> i don't think we've looked at the latest python kafka client
15:40:07 <tomasztrebski> as I said upgrading kafka/zookeeper in devstack is optional item I could do if you all agree to that, but not something that needs to be done
15:40:09 <rhochmuth> but joe has been following pretty closely all the developments
15:40:32 <rhochmuth> i think we should ping joe
15:40:40 <rhochmuth> and get this thoughts on that
15:40:48 <tomasztrebski> Joe is in this review as well
15:41:05 <tomasztrebski> I'd appreciate their (Joe, Craig) insight on this matter
15:41:22 <rhochmuth> ok, i'l; bring it up with them
15:42:01 <tomasztrebski> that's all from my side btw
15:42:07 <rhochmuth> https://review.openstack.org/#/c/286782/
15:42:26 <tomasztrebski> ok, this one is old (I know) but recently we reported/fixed bug about logging in log-api here => https://review.openstack.org/#/c/365932/
15:42:31 <tomasztrebski> and noticed that review in the process
15:43:14 <tomasztrebski> basically that would fix issue where files are not rolled after reaching certain size/age + enable granular control over logging different pieces of information at different severities
15:43:41 <rhochmuth> So, you want to get this change merged too
15:43:42 <tomasztrebski> however I couldn't receive any feedback from creator of this change, so I am posting this here to ask if we could take it over and finish this review
15:44:02 <tomasztrebski> + match up to other OS projects
15:44:09 <tomasztrebski> in terms of handling the logging
15:44:32 <rhochmuth> sure, i don't see any problems taking it over
15:45:01 <witek> tomasztrebski: well, you've sent email today :)
15:45:33 <rhochmuth> i don't think he'll mind
15:45:45 <rhochmuth> checking with him via email is a good step
15:46:00 <tomasztrebski> I did send an email, you were in CC ;-)
15:46:04 <rhochmuth> i'm assuming he'll be thrilled to see it progressed after 6 months
15:46:15 <witek> :)
15:46:28 <tomasztrebski> but last monascan (I think that was the phrase) got bunch of emails :D so it might be overlooked :P
15:47:56 <tomasztrebski> ok, so I will wait two extra days and if there's no progress me or someone else from Fujitsu will match this code to the log-api and it will be ready for final review/merge
15:47:57 <tomasztrebski> ok ?
15:48:07 <rhochmuth> yes
15:48:17 <witek> sounds good
15:48:25 <tomasztrebski> yupi :D
15:48:45 <rhochmuth> #topic summit
15:49:09 <rhochmuth> i thought we could spend a few minutes discussing the summit
15:49:19 <rhochmuth> right now we have 6 design summit slots
15:49:30 <rhochmuth> one more than austin
15:49:35 <witek> on which day?
15:49:54 <rhochmuth> i don't know
15:50:01 <rhochmuth> i beleive thursday and friday
15:50:04 <rhochmuth> spance multiple days
15:50:07 <rhochmuth> spans
15:50:32 <rhochmuth> i was hoping that several slots would be to discuss monasca analytics, like 3
15:50:55 <rhochmuth> i expecting several folks to show up
15:51:12 <rhochmuth> that leaves 3 slots or possibly 4 for more general monasca disucssions
15:51:13 <witek> from hp labs?
15:51:29 <rhochmuth> correct, as well as fujitsu
15:52:01 <rhochmuth> hosanai and his team
15:52:27 <hosanai> rhochmuth: yeah, i and daisuke will go there
15:52:43 <rhochmuth> hi hosanai
15:53:11 <hosanai> rhochmuth: hello
15:53:11 <rhochmuth> on friday, i would like to spend all my time on monasca-analytics if possible
15:53:33 <rhochmuth> and possibly part of thursday too
15:53:52 <tomasztrebski> is there quick way to install analytics (like devstack plugin for monasca-transform) we could use to set this up quickly and play around ?
15:53:54 <rhochmuth> anyway, i think we have lot's of opportunities to do more monasca planning
15:54:07 <witek> cassandra would need 1 session or 2
15:54:10 <rhochmuth> there is a devstack plugin, but it isn't fast to setup
15:54:22 <rhochmuth> yes, i think cassandra would be 1 or 2 sessions
15:54:48 <rhochmuth> what other topics would be valuable to discuss in barcelona, with the restricted set of folks we have available
15:54:56 <rhochmuth> possibly the kibana discussion we were just having
15:55:03 <witek> yes, could be
15:55:15 <rhochmuth> and logging in general
15:55:40 <rhochmuth> tomasztrebski: i'm assuming you are going as well a kamil
15:56:07 <kamil_> yes... i will join
15:56:17 <rhochmuth> great!
15:56:26 <witek> tomasztrebski is sleeping... :)
15:56:53 <rhochmuth> one the bootcamp, what i did for austin is at, https://github.com/roland-hochmuth/monasca-bootcamp
15:56:59 <tomasztrebski> no I am not, just responded privately...a little bit of intimacy please ;-)
15:57:00 <rhochmuth> that is an ipython notebook
15:57:23 <kamil_> great. i will take a look into
15:57:37 <rhochmuth> i don't know if you want to keep that format
15:57:44 <rhochmuth> i think the material shoudl be different though
15:57:58 <rhochmuth> covering different areas of monasca, including logging
15:58:24 <rhochmuth> if you have any questions about the ipython, please let me know
15:58:35 <rhochmuth> well, i guess that is a wrap for today
15:58:50 <rhochmuth> sounds like we've got some ideas on good topics for barcelona too
15:59:02 <bklei> wish i was gonna be there
15:59:05 <rhochmuth> i'll follow up on those reviews that were mentioned with my team
15:59:12 <rhochmuth> me to
15:59:23 <rhochmuth> it is very difficult to so design summits without everyone there
15:59:31 <witek> bklei: yes, it's pitty
15:59:37 <bklei> sad panda
15:59:42 <rhochmuth> the follow-on summit in february in boston, is the one i'm, hoping everyone can attend
15:59:51 <rhochmuth> panda wanna cry
16:00:10 <tomasztrebski> kung-fu panda don't cry o.o
16:00:17 <rhochmuth> bklei, the dimensions names/values and names reivews are ready
16:00:20 <bklei> there's no crying in monasca
16:00:26 <bklei> ok -- will pull in and test
16:00:30 <rhochmuth> ooops got to go and close the meeting
16:00:34 <rhochmuth> thanks everyone
16:00:35 <witek> thanks
16:00:36 <witek> bye
16:00:37 <kamil_> bye
16:00:39 <rhochmuth> bye
16:00:52 <rhochmuth> #endmeeting