14:00:25 #startmeeting monasca 14:00:25 Meeting started Wed Sep 13 14:00:25 2017 UTC and is due to finish in 60 minutes. The chair is witek. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:27 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:30 The meeting name has been set to 'monasca' 14:00:55 hello everyone 14:01:01 o/ 14:01:05 o/ 14:01:09 o/ 14:01:32 small group today 14:01:43 hi! 14:01:56 hi all 14:02:01 the agenda is as usual here: https://etherpad.openstack.org/p/monasca_queens_midcycle 14:02:04 oops 14:02:07 wrong one :) 14:02:08 hi 14:02:19 https://etherpad.openstack.org/p/monasca-team-meeting-agenda 14:02:45 #topic mid-cycle planning 14:03:02 https://etherpad.openstack.org/p/monasca_queens_midcycle 14:03:32 The agenda is filling in 14:04:08 at the end of our mid-cycle meeting I would like to be able to create a list of priorities for the Queens cycle 14:04:18 I think we have too many things on Wednesday, we need to rebalance 14:04:53 might be true 14:05:31 I'll move OpenStack wide goals then 14:06:24 it sounds better now 14:06:32 rhochmuth: can someone from your team speak about Helm installer and docker-compose? 14:07:26 i think so 14:07:28 will have to check 14:07:59 but, tim buckley or michael hoppal would be good to cover that topic 14:08:10 yes, they are the experts 14:08:38 someone has added tripleO 14:08:54 any details about it? 14:09:19 i don't know who added that 14:09:27 I did as I think we need to sort out how to install in RDO/TripleO, at least for RDO, IIRC, there is an open bug 14:10:28 rhochmuth: RDO/TripleO is far different from our old distro 14:10:44 sc: are you driving this? 14:10:52 ok, thanks, that will be an interesting update 14:11:18 witek: yes, at least with the process I'm doing 14:11:32 ok, nice 14:11:37 witek: using ansible could result in a non upogradable cloud 14:13:23 jamesgu and Nicolas have worked on TSDB requirement spec 14:13:49 I've read your document but did't leave comments yet 14:14:31 last week there was request to invite Telemetry team to discuss potential integration with Gnocchi 14:14:58 are you interested in inviting them? 14:15:08 witek: we need more inputs from the community from their perspective of requirements 14:16:32 should we share the etherpad and ask for feedback or is some other form better? 14:17:13 we can share etherpad .. we are using it as a place for data dump at the moment 14:17:16 https://etherpad.openstack.org/p/monasca-db-perf 14:17:41 do you have other form that you'd suggest? 14:18:05 please take a look and we'll further discuss during mid-cycle 14:19:14 we could think of using specification for this and discuss in review, but I'm not sure if it's better 14:19:21 I check in our lab and I have 3 servers free for testing, I need instructions about how to run comparisons 14:19:52 sc: great, thanks 14:20:11 from tsdb perspective, would be interesting to include Gnocchi if someone is interested in driving its integration. but last week, jdavis recommended to invite telemetry for metering discussion 14:20:41 did someone write to them? 14:21:06 I haven't, wanted to ask you here again 14:21:21 I believe last week the "people" voted to leave that to PTL :-) 14:21:27 :) 14:21:54 sc: that's great. I likely need to take up your offer. 14:22:15 jamesgu: the decision if we should invite or invitation itself? 14:22:37 who should contact the telemetry team 14:23:21 cool, so I'll contact them 14:24:09 witek: please do, we need to try to integrate or at least understand where they are going 14:24:47 what exactly are you interested in talking of 'metering discussion'? 14:26:03 jdavis added the topic to the midcycle etherpad if I remember it correctly 14:26:42 Ceilometer API deprecation? 14:27:17 I think so, consistency and service roadmap etc. 14:28:01 for Thursday I have invited Luka Peschke from CloudKitty project 14:28:08 i think that topic in mid cycle was to discuss options we have with monasca-ceilometer e.g. if ceilometer collection components are still valuable, their roadmap..since ceilometer api is getting removed 14:29:17 aagate: as far as I understand they have moved the parts of API to panko, aodh and gnocchi 14:30:26 for CloudKitty, Luka has offered to shortly present the project and make a demo of their integration with Monasca 14:31:51 in the Ceilosca part I could shortly report about monasca-events-api 14:32:54 there was a discussion last week about the possiblity of gnocchi for time series storage 14:33:13 yes that will be good re: monasca-events-api. BTW Panko is for events (but is not actively being worked upon), gnocchi api is replacement for ceilometer api. With monasca-ceilometer we do support ceilometer api, but ideally want monasca api to be used for getting metering data to 14:33:28 the idea was to add gnocchi as a metrics repo in monasca 14:34:05 there was a possiblity of getting an update from gnocchi on performance 14:34:18 metrics injest rates and query performance 14:35:10 rhochmuth: I will contact them and ask if they would like to discuss about it 14:37:01 I hope it's not too short-term 14:37:20 rhochmuth: I would like even to understand if monasca uses gnocchi and telemetry is running how do we manage dupplication of information 14:38:47 is there anything else we want to add or clarify in agenda? 14:39:16 GridDB progress? 14:39:20 can i add the audit log discussion? 14:39:34 you first 14:39:52 GridDB is already on the list 14:40:16 koji: yes, I think we can add it 14:40:35 thanks, i'll do it in tomorrow 14:41:13 might be good to schedule it early as koji is based in Japan 14:41:50 thanks, but i'd like to join all discussion :) 14:42:01 ok :) 14:42:29 anything else? 14:43:10 #topic jira library in g-r 14:43:56 prometheanfire from requirements team has requested adding jira to global-requirements 14:44:18 we use it in monasca-notification jira plugin 14:45:11 the plugin is optional, so the lib is not listed in requirements.txt, but in [extras] 14:45:42 we have two options: 14:45:54 1. add the lib to global-requirements 14:46:29 2. remove from setup.cfg as it's optional 14:46:48 I think there should be no problem to go with 1) 14:47:36 the check-list for adding the lib to g-r is here: 14:47:46 https://github.com/openstack/requirements/#for-new-requirements 14:48:22 I don't know about packaging, but the rest should be good 14:49:08 so, it seems to be a low-hanging fruit, so if anyone wants to take it, just propose a change to openstack/requirements 14:50:07 Is there a story or ticket to reference for the request? 14:50:49 requirements is not in storyboard I guess 14:51:28 I think we don't have to track it 14:53:17 I'll be closing the meeting soon 14:53:25 do we have anything else for today? 14:54:29 nothing 14:54:39 OK, thank you 14:55:02 see you next week in gotomeeting session 14:55:16 See you 14:55:18 thanks 14:55:20 thank you 14:55:22 bye 14:55:22 cheers 14:55:26 thanks! 14:55:32 #endmeeting