15:00:13 <witek> #startmeeting monasca
15:00:14 <openstack> Meeting started Wed Jul 31 15:00:13 2019 UTC and is due to finish in 60 minutes.  The chair is witek. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:15 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:18 <openstack> The meeting name has been set to 'monasca'
15:00:30 <Dobroslaw> hi
15:00:39 <witek> hi Dobroslaw and joadavis
15:01:10 <witek> agenda for today:
15:01:16 <witek> https://etherpad.openstack.org/p/monasca-team-meeting-agenda
15:01:41 <witek> just few items, please add if you have anything
15:02:09 <witek> #topic IPv6
15:02:40 <joadavis> I noticed two commits from Ghanshyam for IPv6
15:02:49 <joadavis> Looks like they may need a little help
15:03:50 <witek> that's a complete list https://review.opendev.org/#/q/topic:ipv6-only-deployment-and-testing++monasca
15:04:14 <witek> IPv6 support is the community wide goal
15:04:21 <joadavis> It may be that the test_missing_port test in monasca-api isn't a test that is compatible with IPv6 parsing, so we may need to change the code to avoid the need for the test
15:04:46 <joadavis> But I haven't dug in to it to be sure :)
15:05:23 <witek> it would be best if we could assign a person for this goal
15:05:45 <witek> gmann is championing this but he definitely will need support
15:05:55 <witek> at very least for reviews
15:06:53 <Dobroslaw> sorry, I don't have much time now
15:08:01 <witek> I think I'll add it to our board and priorities list for the first
15:08:16 <witek> and try to keep an eye on reviews
15:09:53 <witek> any other comments?
15:10:57 <witek> #topic Kafka consumer (persister)
15:10:59 <joadavis> no,
15:11:46 <witek> I'd like to ask for critical and constructive reviews on my Kafka consumer change
15:11:52 <witek> https://review.opendev.org/644844
15:12:32 <witek> there are also 2 small related changes in monasca-common and monasca-api
15:12:51 <witek> and Apache Kafka upgrade https://review.opendev.org/670914
15:13:13 <dougsz> Hopefully should have some time early next week to look.
15:13:25 <witek> that'd be great!
15:14:07 <witek> currently I work on implementation in monasca-notification
15:14:17 <witek> I hope to push the code soon
15:15:08 <witek> just updated the task
15:15:43 <witek> I guess that's all for this topic, any questions?
15:15:51 <joadavis> looks great so far
15:16:26 <witek> thanks joadavis :)
15:16:35 <witek> #topic Mid-cycle recap
15:16:59 <witek> I've updated our Board with AIs from the mid-cycle meeting
15:17:06 <witek> https://storyboard.openstack.org/#!/board/141
15:17:44 <witek> please check if the status is up-to-date and update yourself or ping me to do it
15:18:31 <witek> e.g. do you know if there are any tasks which should be added to "test coverage" story?
15:19:40 <witek> please also add other stories or tasks which you feel should appear there
15:21:31 <witek> #topic Monasca+CloudKitty
15:22:05 <witek> there was an interesting discussion in the Scientific SIG today
15:22:17 <witek> around this blog article:
15:22:24 <witek> https://www.stackhpc.com/cloudkitty-and-monasca-1.html
15:23:30 <witek> it's the report about the work on using Monasca and CloudKitty for billing
15:23:47 <witek> updates on further work will follow
15:23:59 <joadavis> very good
15:24:18 <witek> I knew you would be interested :)
15:25:18 <witek> the discussion logs are available here:
15:25:25 <witek> http://eavesdrop.openstack.org/meetings/scientific_sig/2019/scientific_sig.2019-07-31-11.00.log.html#l-25
15:26:41 <witek> the importance of the possibility to collect notifications was stressed
15:28:19 <joadavis> yes, that is one of our wants for Monasca
15:28:56 <witek> also, there was an open question around possibility to collect flavor metadata with Ceilosca
15:29:19 <witek> can you share some information about it?
15:30:45 <joadavis> I'll have to dig in to what is available for flavors
15:30:55 <joadavis> seems possible
15:31:18 <joadavis> theoretically, anything Ceilometer can get we can pass to Monasca
15:31:30 <witek> yes, that was my understanding as well
15:32:15 <witek> alright, I guess we can move on
15:32:45 <witek> #topic default alarms Ansible role
15:32:53 <Wasaac> Hey o/
15:33:18 <Wasaac> Would like to have some feedback on a little ansible role + modules I rewrote
15:33:53 <Wasaac> Based on the original https://github.com/hpcloud-mon/ansible-monasca-default-alarms I've rewritten the modules to support the newer keystone auth methods
15:34:11 <Wasaac> Can be downloaded from ansible galaxy here: https://galaxy.ansible.com/stackhpc/monasca_default_alarms
15:34:53 <Wasaac> In particular, I'm looking to refine a set of alarms applicable to most users
15:35:07 <witek> that's very helpful
15:35:46 <witek> I don't see instructions, how to run it
15:36:51 <Wasaac> There's a readme available on both galaxy and our github https://github.com/stackhpc/monasca-default-alarms
15:37:29 <dougsz> I suppose we could include a small note on how to run a playbook for people not familiar
15:37:38 <Wasaac> It assumes a little knowledge of ansible roles but I'm happy to clear it up if that would get more people using it
15:38:42 <witek> yes, just a simple command how to run the example playbook
15:38:44 <dougsz> What do we think about moving this role to github.com/monasca?
15:39:00 <witek> +1
15:39:34 <dougsz> my preference too, we can do that
15:40:08 <Wasaac> That'd be cool
15:40:11 <witek> about the content, we could think about adding some alarm definitions based on metrics from prometheus-openstack-exporter
15:43:01 <Wasaac> Some suggestions I've had recently were about separating alarms logically into those specific to the control-plane and those applicable to hosts
15:44:12 <Wasaac> Given it allows custom alarm definitions I'm thinking a base set applicable to everyone and a few sets of handy alarms that can be toggled
15:44:37 <Wasaac> If anyone would like to share useful alarm definitions that'd be greatly appreciated
15:44:42 <Wasaac> And that's all from me
15:45:09 <joadavis> I was trying to remember what we define for devstack out of the box, but I think we don't.  Maybe something in https://github.com/ArdanaCLM/monasca-ansible
15:45:45 <joadavis> If I find something, I'll try to share it
15:45:57 <witek> Wasaac: ansible supports tags for controlling which tasks are executed, do we use it here?
15:46:24 <Wasaac> We do, the task includes can be toggled with both tags and vars
15:46:39 <witek> we don't ship anything in DevStack
15:47:23 <witek> we could also add a pointer in docs.o.o to make the repository more visible
15:49:54 <witek> thanks Wasaac for this work, I think we should do more things like this to improve user experience out of the box
15:50:16 <Wasaac> My pleasure
15:50:28 <joadavis> https://github.com/ArdanaCLM/monasca-ansible/blob/cde600dc28b8a384aada756f9f526e7777a83cd4/roles/monasca-default-alarms/vars/main.yml gives some defaults, though some may not be generic enough
15:50:40 <dougsz> +1, Optionally using this role in Kolla Ansible would be nice to have some alarms out of the box,
15:51:20 <Wasaac> joadavis: very handy, much appreciated
15:53:12 <witek> #topic AOB
15:53:26 <witek> anything else we want to discuss?
15:54:22 <witek> apparently not
15:54:38 <witek> thank you for joining today and interesting discussion
15:54:52 <witek> thanks for contributions and see you next week
15:54:53 <dougsz> thanks all
15:55:03 <witek> #endmeeting