15:00:17 #startmeeting monasca 15:00:18 Meeting started Wed Aug 10 15:00:17 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:19 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:22 The meeting name has been set to 'monasca' 15:00:28 o/ 15:00:29 o/ 15:00:34 Agenda is at, https://etherpad.openstack.org/p/monasca-team-meeting-agenda 15:00:40 Agenda for Wednesday August 10, 2016 (15:00 UTC) 15:00:41 1. Monasca Logstash-Output-Plugin ( https://github.com/logstash-plugins/logstash-output-monasca_log_api/pull/1 ) 15:00:41 2. Cassandra update: 15:00:41 1. https://blueprints.launchpad.net/monasca/+spec/monasca-cassandra 15:00:41 3. Dimensions API 15:00:41 1. https://blueprints.launchpad.net/monasca/+spec/dimensions-api 15:00:41 4. Last-value 15:00:42 1. https://blueprints.launchpad.net/monasca/+spec/last-value 15:00:42 5. Notification Engine plugin 15:00:43 1. https://blueprints.launchpad.net/monasca/+spec/notification-engine-plugin 15:00:43 6. Metric ID parameter 15:00:43 o/ 15:00:44 1. https://blueprints.launchpad.net/monasca/+spec/metric-id-query-parameter 15:00:48 o/ 15:00:49 hellp 15:00:53 hello 15:00:54 :) 15:01:08 o/ 15:01:18 o/ 15:01:55 Hopefully, we can get through this agenda quickly, then have open discussion 15:02:11 I'll just start with the first item in the agenda and then work through it 15:02:16 I'm officially on vacation 15:02:27 #topic Monasca Logstash-Output-Plugin ( https://github.com/logstash-plugins/logstash-output-monasca_log_api/pull/1 ) 15:02:40 That's me 15:02:49 We pushed some weeks ago a pull request to logstash 15:02:58 https://github.com/logstash-plugins/logstash-output-monasca_log_api/pull/1 15:03:05 yes, we discussed here previousely 15:03:05 To contribute the monasca output plugin. 15:03:27 Unfortunaly nothing happend since that push. So maybe folk could just add a comment to push it forward 15:03:35 OK, will do 15:03:37 +1 15:03:43 tsv: added a comment 15:04:13 maybe i need to ping logstash again 15:04:56 But that's all. We can move to the next topic 15:05:15 thx Kamil_ 15:05:22 if that does not work, we could think of new openstack repo 15:05:29 i'll add a comment after meeting is over 15:05:38 Thank you 15:05:48 is there a thumbs up button 15:06:09 for the pull requests, or it is just a comment? 15:06:29 i was wondering if there was a way to vote on the PRs 15:06:31 just +1 i reckon 15:06:34 i think there is also a thumbs up button. I created already one 15:07:08 or it was a thumbs up smiley in a comment 15:07:24 #topic Cassandra update: 15:07:25 https://blueprints.launchpad.net/monasca/+spec/monasca-cassandra 15:07:54 So, all the Cassandra code in it's current form as well as DevStack has been merged 15:08:04 thanks shinya_kwbt 15:08:19 +1 15:09:11 I believe we are still waiting to here back from me and DT on resource commitments 15:09:41 I don't have a firm commitment, but I think we'll be able to put 0.5 engineer on this 15:10:24 it would be great to have your support 15:11:13 I've seen Shinya had some problems with setting up tempest tests 15:11:19 https://review.openstack.org/#/c/352245/ 15:12:42 not too bad of a problem i hope 15:12:53 upgrading to new version of ubuntu 15:13:57 ohhh, i also want to point out that i've added all the discussion notes from some of the emails that w've exchanged to the Cassandra blueprint 15:14:10 so we don't lose track of the ideas we've been having 15:14:27 i think we should close out that bluepring though 15:14:39 good idea, thanks for that 15:14:41 and create another blueprint to cover future changes 15:15:02 it would be a good idea to mark the blueprint as implemented, which it functionally is at this point 15:15:18 and address future changes in a separate blueprint/s 15:15:31 i'll work on that 15:15:36 where is the new blueprint? 15:15:44 it isn't created yet 15:15:44 I can work on it too 15:15:48 ok 15:15:53 ok, thanks 15:16:09 i think the main part is all the tasks at the bottom should be recored in a new bp 15:16:41 so, are you going to create a new bp, or should i 15:17:08 all in one blueprint? 15:17:33 that is waht i was going to do to keep things easy right now 15:17:50 i think some of those ideas/tasks are undefined at this point 15:17:52 ok, i'll do that 15:18:00 ok, thx witek 15:18:31 i'm thinking we should have a more complete/thorough planning session on Cassandra to 15:18:39 so we can get organized some more 15:18:49 i'm on vacaton for a couple of weeks 15:19:02 denied 15:19:11 i'm in vacation starting on friday 15:19:18 also denied 15:19:19 but maybe we can do that in a few weeks 15:19:52 let's make it in the first sep week 15:19:58 I don't get vacation. 15:20:01 how about early September then 15:20:16 yes 15:20:18 slogan_: you live in San Diego 15:20:24 Isn't that always a vacation 15:20:27 Touche 15:20:50 Yeah, bash prompt looks the same in San Diego and South Dakota 15:21:29 OK, so earl September it is for a Cassandra summit 15:21:48 could you coordinate? 15:21:55 hopefully shinya will be back 15:22:10 sure, i'll coordinate 15:22:40 #topic Dimensions API 15:22:50 https://blueprints.launchpad.net/monasca/+spec/dimensions-api 15:23:17 Kaiyan from HPE is adding support for the DImensions Names resource 15:23:35 See the review at, https://review.openstack.org/#/c/350830/ 15:23:45 i've been watching that patch -- will pull in and test when it's baked 15:24:06 After this review is completed both the dimensions names and values, which bklei implemented, will be 100% complete 15:24:18 So, that will mark the completion of that blueprint 15:24:25 Thx bklei! 15:24:41 looks like kaiyan is making good progress on part 2! 15:24:53 rbak: You'll also want to watch those reviews 15:24:58 as they will impact Grafana 15:25:27 Additionally, I could see changes to the Monasca UI (Horizon) that could be made 15:25:53 The changes aren't required, but if they are, significant performance improvements will be possible 15:26:31 So, if someone from the UI side is interested in looking at the MOnasca UI changes, that would be helpful 15:26:58 one of us might pick that up -- if shinya doesn't 15:27:07 perhaps you could define work packages in the blueprint, so someone can pick it up 15:27:08 thx bklei 15:27:48 Not sure what work packages are 15:27:56 should they be separate bps 15:28:16 i was writing with bklei in parallel 15:28:51 i meant define what could be done, so someone could implement it 15:29:43 OK, i'll add bp for the Monasca UI changes for the dimensions resource API 15:29:45 or maybe create blueprints from those definitions 15:29:58 if needed 15:29:58 so somewhere in monasca-ui we do a metrics-list that could be replaced by kaiyan's new endpoint i guess 15:30:21 in addition to grafana 15:30:33 the code should be very model view (it's intrinsic with Django) 15:30:33 correct, something like that 15:30:40 sounds like slogan is volunteering 15:30:54 he's on permanent vacation 15:31:05 i thought 15:31:11 It's complicated 15:31:21 have you ever seen me checkin anything? 15:31:51 ohh, you still don't have approval? 15:32:01 not yet 15:32:10 is that in progress? 15:32:32 not sure 15:32:40 thx 15:33:07 i'll create the bp, and between shinya, charter, fujitsu and slogan, we can address 15:33:16 cool 15:33:27 let's close this out and move on 15:33:39 #topic Last-value 15:33:46 https://blueprints.launchpad.net/monasca/+spec/last-value 15:34:02 So, I believe that this review is still up 15:34:39 Actually, the code has been merged 15:34:49 So, I believe that bp should be marked as completed 15:35:04 api is not merged yet 15:35:44 Well, almost then 15:35:52 lost track these past few days 15:35:57 thanks witek 15:36:28 So, I guess that is another one to possibly get added to the Monasca UI too 15:36:38 I just realized 15:37:07 I'll create a bp for that 15:38:03 #topic Notification Engine plugin 15:38:41 I think this bp, is nearing completion 15:38:48 the initial support has been added 15:39:20 there are some bug fixes in progress, as well as updates to the HipChat formatting, and the JIRA plugin is in progress. 15:39:45 The Slack and Hipchat plugins are functional 15:40:09 #topic Metric ID parameter 15:40:16 https://blueprints.launchpad.net/monasca/+spec/metric-id-query-parameter 15:40:24 We had talked about this at the mid-cycle 15:40:36 We would like to proceed with adding this capability 15:41:07 I don't beleive that I marked it as approved 15:41:10 this one makes me sad 15:41:17 was hoping for a caching solution 15:41:19 but would like to move it to the approved state 15:41:32 we are still looking at caching 15:41:41 but in the short-term we would like to add this 15:41:50 there isn't any downside as far as I know 15:42:06 I think it would be good to have it for C* as well 15:42:21 basically, you can specifiy a metric/s in a measurements or statistics query 15:42:31 yes, it will also be applicable to C* 15:42:32 Just so you know, the blueprint mentions grafana, but after looking closer at grafana I don't believe this will be useful there. 15:42:46 thx rbak 15:42:54 i'll update bp and remove grafana 15:43:02 Grafana just isn't designed for one query to change/impact the next. 15:43:50 so, are folks ok if i move this to approved? 15:44:15 we are still looking at caching, but it is extremely difficult 15:45:16 i'm good with that -- no harm to adding it. 15:45:23 thx 15:45:53 going once, twice, … 15:46:03 metric id is metric_hash? 15:46:11 correct 15:46:29 it is really an opague ID 15:46:37 it could be the hash or somethign else 15:46:46 so it is just extending api without schema change? 15:46:53 correct 15:47:09 +1 15:47:33 actually, i beleive to handle influxdb, there is a change where we create a ID 15:47:51 and store that as a private tag 15:48:02 sorry, i spoke too soon 15:48:47 bit influxdb is schemaless 15:49:04 ok, i'll talk with my team and comment on review 15:49:14 ok, thanks witek 15:49:43 So, that concludes the agenda topics 15:49:48 #topic open discussion 15:50:05 Does anyone have any additional items to discuss 15:50:34 it looks like Claudiu Belu has been active with the windows support in the Agent 15:50:42 THat would be worth looking at 15:51:04 All his reviews are passing agina with Jenkins 15:51:19 And we made a lot of changes from when he first started to this point 15:51:35 Which I'm sure caused him a bit or rework 15:52:08 The Windows support was mainly focused on adding support for HyperV 15:52:39 yeay 15:52:52 hi claudiub 15:52:59 it looks like you are back 15:53:00 hyper-v and other metrics 15:53:22 so, is this ready for review again? 15:53:33 but the hypervisor metrics are the biggest change 15:53:50 imo, yes 15:54:11 ok, will try and get folks to look at this 15:54:15 yeah 15:54:19 we were in the process of getting hyperv running at hpe 15:54:30 that took longer than expected 15:54:43 actually, i'm still not sure we ever got everything working 15:54:59 but the main blocker was how to have agent checkers with platform-based behaviour. 15:55:21 well, the folks from hpe are regular attendees at the hyper-v meetings 15:55:47 they said everything's working on their end 15:55:57 do you have a contact? 15:56:04 for hpe? 15:56:10 yeah, sagar_nikam is the main person 15:56:16 ok, thanks 15:56:21 i'll track him down 15:56:22 and then kvinod and Sonu 15:56:38 ok, i know kvinod and Sonu 15:58:02 Are there any other topics for today? 15:58:19 negative ghostrider, pattern is full 15:58:41 bklei ? 15:58:47 top gun ref 15:59:05 thanks everyone 15:59:10 i'm going to close out the meeting then 15:59:11 thanks 15:59:15 cya 15:59:17 bye 15:59:18 bye 15:59:22 have a good time 15:59:29 #endmeeting