15:00:24 <witek> #startmeeting monasca
15:00:24 <openstack> Meeting started Wed Mar  6 15:00:24 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:25 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:28 <openstack> The meeting name has been set to 'monasca'
15:00:34 <joadavis> Greetings
15:00:38 <witek> hello everyone
15:00:40 <witek> hi joadavis
15:01:05 <witek> do you have any topics for the agenda?
15:01:23 <dougsz> o/
15:01:26 <witek> hi dougsz
15:01:30 <joadavis> I don't. I've been wishing I was working upstream a bit more lately
15:01:37 <dougsz> +1
15:01:39 <joadavis> hi dougsz
15:01:50 <dougsz> hey all
15:02:12 <witek> thanks for the reviews on Kafka client last week
15:02:15 <Dobroslaw> Hello
15:02:19 <witek> hi Dobroslaw
15:02:39 <witek> dougsz: Dobroslaw please fill in topics in the agenda if you have any
15:02:56 <dougsz> nothing from me this week
15:03:06 <Dobroslaw> Don't have any at this moment
15:03:42 <witek> I've looked again at dropping measurements with parsing errors in persister
15:03:50 <witek> https://review.openstack.org/638589
15:04:30 <witek> actually we do validate that the measurements for empty dimension values in API
15:04:57 <witek> so the measurement should be rejected before already
15:05:22 <witek> but I think that the change still can be useful
15:06:16 <witek> I've suggested to define a new config option to control if the measurement should be dropped or persister stopped
15:06:28 <Dobroslaw> So is he sending measurements straight to persister?
15:06:50 <witek> straight to Kafka, I assume
15:07:29 <witek> we do it in monasca-log-metrics as well
15:07:49 <Dobroslaw> Ok
15:09:41 <witek> please comment in review if you think it's a good idea
15:10:17 <dougsz> Will try to take a look when I get some time
15:10:29 <witek> thanks dougsz
15:11:26 <witek> I've added story about broken formatting in Python 3 client to the board
15:11:33 <witek> https://storyboard.openstack.org/#!/board/111
15:12:34 <witek> and I'm working on adding Confluent Kafka client in persister
15:13:48 <Dobroslaw> Nice
15:14:57 <witek> dougsz: do you know if Kolla could need tagging images on releases?
15:16:22 <witek> we wanted to build and publish Monasca images on every release but Dobroslaw has reported it's not supported by infra as of now
15:16:45 <Dobroslaw> on every tag at last
15:18:17 <Dobroslaw> It's probably possible to create docker images on tag but jobs would need to stay in openstack-config
15:18:46 <Dobroslaw> *project-config
15:19:52 <dougsz> witek: Not quite sure I understand
15:20:22 <dougsz> It can apply arbitrary tags to images
15:20:29 <dougsz> Are you talking about in CI?
15:20:40 <witek> we would like to have a job in CI which publishes an image on every version tag in repo
15:20:43 <Dobroslaw> In CI
15:20:50 <dougsz> ah got it
15:21:16 <Dobroslaw> To have stable images more frequently
15:21:35 <dougsz> So in kolla there is a static file which tracks all the versions, but you can override parts of it.
15:22:13 <dougsz> I will have a  look at exactly what goes on in CI and report back next week
15:22:24 <Dobroslaw> Thank you
15:22:31 <dougsz> np
15:23:07 <witek> #topic email notification templating
15:23:22 <pandy> Hi witek, its mine
15:24:05 <pandy> I can say that would like to contribute to monasca by customising notification template
15:24:47 <pandy> Hope dougsz already in testing phase of slack notification, I would like to work similar on email body customisation
15:25:03 <pandy> Currently email body looks like this http://paste.openstack.org/show/747345/
15:25:52 <pandy> From end user comments, It will be good if customise mail subject & body with more simple information.
15:26:21 <pandy> Looking forward witek & dougsz and all advise here
15:26:46 <witek> as a final goal it would be great to have an API to control how the notification method looks like
15:27:18 <dougsz> Yeah, so tenants can customise it individually per project
15:27:25 <witek> it could be added as parameter to create-notification method
15:27:42 <pandy> Yes, but here looking forward everyone advise. From our user comments need tenant_name in mail body and subject
15:27:58 <witek> and then persisted in SQL DB
15:28:43 <dougsz> pandy: If you put a break point in just before it calls the notification method you can see all the information you have available which could be included in the message.
15:30:41 <pandy> dougsz, okay understood. I can pull information whatever i want for my local user. but In general default template need little shape as told like adding few moew information in subject & mail body, so globally all can use
15:31:49 <mohankumar> pandy : I like to ve this feature in Monasca, If you need any help please let me know . we can collaborate
15:33:26 <witek> I think we could start with putting some requirements and implementation plan to the story
15:33:27 <pandy> mohankumar, Yes. based on user story feel to have this info in default in upstream monasca will be good :) Looking forward witek to support to contribute
15:34:20 <pandy> witek, yes thats am looking from you all, So I can work on
15:34:25 <witek> what we want is to have some easy to edit template which would control the shape of notification message
15:35:14 <joadavis> and have some simple defaults, like a generic message with simple formatting.
15:35:15 <witek> to follow the spirit of Monasca we would like to have an API resource to control this templates
15:35:35 <witek> but that could be a second step
15:36:31 <mohankumar> witek: how about enable user to add their template (yaml/j2) . we can expose some API to add them in monasca notification template
15:38:11 <witek> I rather thought about persisting it in the DB
15:38:28 <mohankumar> witek: agree
15:39:17 <pandy> witek, please add your comments in https://storyboard.openstack.org/#!/story/2005111, so can follow up
15:40:08 <witek> probably would fit best in POST notification-methods
15:40:09 <witek> https://github.com/openstack/monasca-api/blob/master/docs/monasca-api-spec.md#post-v20notification-methods
15:41:38 <witek> mohankumar: and yes, the users should be able to add own templates
15:42:27 <witek> pandy: I guess you can start extending the story based on that discussion
15:42:43 <pandy> sure, I do.
15:42:53 <witek> thanks
15:43:08 <pandy> :)
15:44:24 <witek> cool, some more questions on that?
15:45:06 <pandy> Nope, witek. will get back if have doubts :)
15:45:22 <witek> thanks, that's all from me
15:45:33 <witek> I'll be wrapping up if there's nothing else
15:46:00 <pandy> Thank you all
15:46:10 <witek> thank you
15:46:11 <dougsz> Thanks all, until next week
15:46:14 <witek> see you next week
15:46:15 <joadavis> Nothing else
15:46:16 <Dobroslaw> Thanks
15:46:21 <witek> buy
15:46:23 <haru5ny> thank you
15:46:27 <witek> bye :)
15:46:28 <joadavis> Til next time. :)
15:46:41 <witek> #endmeeting