15:00:50 #startmeeting monasca 15:00:51 Meeting started Wed May 17 15:00:50 2017 UTC and is due to finish in 60 minutes. The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:53 o/ 15:00:53 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:55 The meeting name has been set to 'monasca' 15:00:58 o/ 15:01:01 o/ 15:01:09 o/ 15:01:14 o/ 15:01:15 https://etherpad.openstack.org/p/monasca-team-meeting-agenda 15:01:18 hello 15:01:23 o/ 15:01:26 hello 15:01:30 Agenda for Wednesday May 17 2017 (15:00 UTC) 15:01:30 1. Using oslo_config for detection plugins https://storyboard.openstack.org/#!/story/2000999 15:01:30 2. Feedback from OpenStack Summit 15:01:30 • complicated deployment 15:01:30 • no scalable opensource DB 15:01:30 • comparisons with Ceilometer/Gnocchi 15:01:30 3. Create a pike branch for monasca-transform 15:01:31 4. Pike release 15:01:31 5. Alarm silencing, inhibition and grouping update 15:01:32 6. Grafana update 15:01:32 7. Reviews that should be addressed? 15:01:32 o/ 15:01:33 hello 15:01:37 o/ 15:01:54 wow, good group today 15:02:16 so let's get started on the agenda 15:02:27 #topic Using oslo_config for detection plugins 15:02:34 https://storyboard.openstack.org/#!/story/2000999 15:02:58 Summit has posted it for the last week 15:03:07 I just moved it over 15:04:04 I think the proposed idea is good 15:04:05 unfortunately he's not here today 15:05:27 also we could try to coordinate it for all services in one place, as kornicameister suggested 15:05:45 sounds good to me 15:06:23 is there anything else to discuss on this topic? 15:06:44 not sure, not from me 15:06:58 #topic Feedback from OpenStack Summit 15:07:46 I have added three most frequenly asked questions we had during the Summit 15:08:31 * complicated deployment, no scalable DB and differences to Ceilometer 15:08:54 I have attended several sessions about kolla, esp. kolla-ansible 15:09:27 I think we could have a closer look at as the mean of easy Monasca deployment 15:10:48 I think the monasca-docker and monasca-helm repos help in the short-term 15:10:56 but those are outside of OpenSTack and Kolla 15:11:46 easy deployment is certainly the goal for both monasca-docker and monasca-helm 15:12:07 yes, you have done a lot of work on it, and it's the right direction 15:12:21 but it doesn't have visibility in OpenStack 15:13:03 so, how do we create some visibility, without joining Kolla 15:13:12 or how do we join Kolla 15:13:24 and get the visibility that way? 15:13:44 I would like to check how much effort would it be to join kolla, kolla-ansible 15:13:53 considering the discussions on the -dev list we may want to tread carefully there, since we intend to release binary images 15:15:03 There is also https://github.com/sapcc/helm-charts/tree/master/openstack/monasca of course :) 15:16:06 witek, if you want to follow-up with the Kolla team and PTL to get there thoughts/ideas on this, that might help 15:16:25 i'm sure timothyb89 and hoppal might be up for some discussions 15:16:34 yes, will follow this 15:16:43 please feel free to involve me too 15:16:47 sure, I'd be happy to discuss further 15:16:51 i'm not the docker/helm expert 15:16:54 great, thanks 15:17:00 thanks timothyb89 15:17:13 I think keeping a maintained devstack install helps too, for those who aren't ready for containerizing to reference. 15:17:16 dhague: kolla-ansible is without k8s 15:17:54 well, one thing that might help development is creating a development process for a Docker install 15:17:55 joadavis: yes :) 15:18:55 the dev process is one of the goals for monasca-docker, mostly that needs documentation at this point :) 15:19:40 i think DevStack has always been a bit of a obstacle/barrier to developers getting involved with Monasca 15:20:44 #topic no scalable opensource DB 15:20:59 right, nothing new, but painful 15:22:03 just wanted to note that many people asked about it 15:22:09 Is this a seperate topic, or just a feedback from openstack summit? 15:22:16 other than some of the work that is continuing on with cassandra, i don't see any other grat alternatives, beyond influxdb 15:22:34 still the same topic 15:22:39 kamil_ 15:23:21 and the last question group: will Monasa replace Ceilometer? 15:23:37 Ceilometer API has been deprecated in Ocata 15:23:49 also Gnocchi is moving out from OpenStack 15:23:58 I think the differences from Ceilometer are a positive aspect. :) 15:24:01 hmmm, the Ceilometer v2.0 api has been deprecated? 15:24:25 yes, still in for ocata and pike (so far) but marked as deprecated 15:24:41 ceilometer is more about routing events & metrics to the respective storage engines (gnocchi, panko) 15:24:51 so the API is gone, but the component is still there 15:25:10 gnocchi is moving out of openstack? 15:25:57 ceilometer serves a purpose for capturing audit events, although at SAP we are in the process of deprecating its usage anyway and just listening to oslo notifications with logstash 15:25:57 http://lists.openstack.org/pipermail/openstack-dev/2017-March/114300.html 15:26:17 so, i think ceilometer is still very useful to monasca in terms of data collection 15:26:36 (shameless plug) or we can have ceilometer push to monasca with ceilosca 15:26:38 I would agree, especially when coupled with oslo.kafka 15:26:48 +1 joadavis 15:27:00 thx witek! 15:27:22 the monasaca api can be used for metering/billing 15:27:23 main difference I see: ceilometer is for openstack admins, monasca is for openstack end-users as consumers 15:27:58 so, does this imply that metering/billing use cases in addition to monitoring would be best served by the monasca api? 15:28:27 since ceilometer api is deprecated, and gnocchi is not part of openstack 15:29:09 +1 best servered by monasca api, rhochmuth 15:29:20 rhochmuth: yes that would the case 15:29:32 i guess that seems like a reasonable position, since we were already doing this 15:29:35 I would argue that there is plenty in monasca's backlog without worrying about metering/billing, which (with auditing) is well served by ceilometer 15:29:41 I think people will still use it, but projects such as cloudkitty want to integrate with Monasca too 15:31:49 it would be nice to see monasca integrate with cloudkitty, watcher, … 15:32:17 talligent... 15:32:27 rhochmuth: yes, I think we should follow-up on this 15:33:02 so, are there any next steps/actions for folks to work on 15:33:58 I want to follow-up with CloudKitty and Watcher 15:34:13 thanks witek_ 15:34:41 ok, to end the topic 15:34:45 in addition, there is vitrage 15:35:01 added the videos to the wiki page: https://wiki.openstack.org/wiki/Monasca#Presentations 15:35:44 thanks witek_ 15:35:49 :) 15:35:51 so let's move on to next topic 15:36:15 we'll wait for updates from you on how your discussions go with watcher and cloudkitty 15:36:37 thanks rhochmuth 15:36:44 but feel free to involve others 15:36:58 sure 15:37:41 #topic Create a pike branch for monasca-transform 15:38:14 I have missed that, there is no tag in that repo at all 15:38:18 monasca-transform hasnt had a branch created yet. Since pike-milestone-3 is coming up wanted to know what steps are needed to get it included 15:39:41 so, witek_, will you create a tag, or would you like agatea to create one? 15:39:52 yes, I can label a tag for you 15:40:00 thx witek_ 15:40:01 and cut the branch 15:40:22 agatea: while you are here, i just wanted to point out this, https://github.com/monasca/monasca-aggregator 15:40:25 let's follow offline, and let me know which commit I should use 15:40:28 thanks witek_! we really appreciate it 15:41:02 also, which release type should it follow 15:41:30 rhochmuth: will take a look 15:41:40 thx 15:41:42 cycle-with-intermediary as most of the other repos? 15:41:57 witek_: i think that makes sense 15:43:02 #topic pike release 15:43:17 are there any updates in this area 15:43:31 June 8 is milestone-2 15:43:32 besides getting monasca-transform part of the release 15:43:48 so, i'm assuming that we are in good shape 15:44:06 although, i'm wondering if we'll be able to make alarm silencing, inhibition and grouping in that time 15:45:20 RC1 target week is Aug 07 - Aug 11 15:45:36 well, we should be able to make that date 15:46:34 so, sounds like we are on track, and no issues 15:46:39 thx witek_ 15:46:58 I haven't generated any issues :) 15:47:09 #topic Alarm silencing, inhibition and grouping update 15:47:27 i just wanted to mention that this is nearing completion 15:47:38 there are a bunch of reviews in flight 15:48:14 could you give here the reference to reviews again? 15:48:31 i'll need to collate them seperately and provide directions 15:48:43 ok, thanks 15:48:45 i'll follow-up with andrea and send somethign out to the openstack-dev list 15:49:43 #topic Grafana update 15:50:59 We've made some progress on gettign a SOW signed with Grafana Labs to add Keystone integration to the Grafana master/source 15:51:12 hopefully, that will get signed relatively soon 15:51:21 dhague: ^^^ 15:51:35 wow, great news 15:52:08 hopefully the contract/sow gets signed 15:52:22 #topic Reviews that should be addressed? 15:52:39 besides the reviews we've discussed so far, are there any other reviews to consider 15:53:11 https://review.openstack.org/#/c/461917/ will be good to go once the tests are passing 15:53:54 thx timothyb89 15:54:00 i'll take a look 15:54:18 is there a way to get a screen shot of the notifications? 15:54:34 I think I have one handy 15:55:03 I have used them in the workshop in Boston 15:55:05 not sure how to add that as a link to the review, but that might help show folks what this thing looks like 15:56:30 hm, apparently I don't have an image handy, but I will add it to the review :) 15:56:39 thx 15:57:00 so, i guess that is it for today, unless there is a final topic in closing 15:58:26 thanks everyone 15:58:35 thank you 15:58:51 bye 15:58:56 thanks 15:59:02 bye thanks! 15:59:17 thanks bye 15:59:32 #endmeeting