| *** pcaruana has joined #openstack-monasca | 08:29 | |
| openstackgerrit | Merged openstack/monasca-api master: Remove redundant code https://review.openstack.org/632976 | 08:57 |
|---|---|---|
| *** witek has joined #openstack-monasca | 09:34 | |
| openstackgerrit | Adrian Czarnecki proposed openstack/monasca-api master: [WIP] Improve coverage https://review.openstack.org/632718 | 09:37 |
| openstackgerrit | Adrian Czarnecki proposed openstack/monasca-api master: Improve tests coverage https://review.openstack.org/632718 | 10:02 |
| *** zenirc369 has joined #openstack-monasca | 10:40 | |
| *** dougsz has joined #openstack-monasca | 10:52 | |
| *** pcaruana has quit IRC | 11:04 | |
| *** pcaruana has joined #openstack-monasca | 11:32 | |
| *** chaconpiza has quit IRC | 11:39 | |
| *** chaconpiza has joined #openstack-monasca | 11:53 | |
| *** pcaruana has quit IRC | 13:51 | |
| openstackgerrit | Merged openstack/python-monascaclient master: Update json module to jsonutils https://review.openstack.org/638987 | 13:55 |
| *** pcaruana has joined #openstack-monasca | 14:01 | |
| witek | Courtesy Monasca meeting reminder in #openstack-monasca: witek, jayahn,iurygregory,ezpz,igorn,haad,sc,joadavis, akiraY,tobiajo,dougsz_,fouadben, amofakhar, aagate, haruki,kaiokmo,pandiyan,charana,guilhermesp,chaconpiza,toabctl | 14:55 |
| witek | #startmeeting monasca | 15:00 |
| 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 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:00 |
| *** openstack changes topic to " (Meeting topic: monasca)" | 15:00 | |
| openstack | The meeting name has been set to 'monasca' | 15:00 |
| joadavis | Greetings | 15:00 |
| witek | hello everyone | 15:00 |
| witek | hi joadavis | 15:00 |
| witek | do you have any topics for the agenda? | 15:01 |
| dougsz | o/ | 15:01 |
| witek | hi dougsz | 15:01 |
| joadavis | I don't. I've been wishing I was working upstream a bit more lately | 15:01 |
| dougsz | +1 | 15:01 |
| joadavis | hi dougsz | 15:01 |
| dougsz | hey all | 15:01 |
| witek | thanks for the reviews on Kafka client last week | 15:02 |
| Dobroslaw | Hello | 15:02 |
| witek | hi Dobroslaw | 15:02 |
| witek | dougsz: Dobroslaw please fill in topics in the agenda if you have any | 15:02 |
| dougsz | nothing from me this week | 15:02 |
| Dobroslaw | Don't have any at this moment | 15:03 |
| witek | I've looked again at dropping measurements with parsing errors in persister | 15:03 |
| witek | https://review.openstack.org/638589 | 15:03 |
| witek | actually we do validate that the measurements for empty dimension values in API | 15:04 |
| witek | so the measurement should be rejected before already | 15:04 |
| witek | but I think that the change still can be useful | 15:05 |
| *** haru5ny has joined #openstack-monasca | 15:05 | |
| witek | I've suggested to define a new config option to control if the measurement should be dropped or persister stopped | 15:06 |
| Dobroslaw | So is he sending measurements straight to persister? | 15:06 |
| witek | straight to Kafka, I assume | 15:06 |
| witek | we do it in monasca-log-metrics as well | 15:07 |
| Dobroslaw | Ok | 15:07 |
| witek | please comment in review if you think it's a good idea | 15:09 |
| dougsz | Will try to take a look when I get some time | 15:10 |
| witek | thanks dougsz | 15:10 |
| *** pandy has joined #openstack-monasca | 15:10 | |
| witek | I've added story about broken formatting in Python 3 client to the board | 15:11 |
| witek | https://storyboard.openstack.org/#!/board/111 | 15:11 |
| witek | and I'm working on adding Confluent Kafka client in persister | 15:12 |
| *** mohankumar has joined #openstack-monasca | 15:13 | |
| Dobroslaw | Nice | 15:13 |
| witek | dougsz: do you know if Kolla could need tagging images on releases? | 15:14 |
| 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 |
| Dobroslaw | on every tag at last | 15:16 |
| Dobroslaw | It's probably possible to create docker images on tag but jobs would need to stay in openstack-config | 15:18 |
| Dobroslaw | *project-config | 15:18 |
| dougsz | witek: Not quite sure I understand | 15:19 |
| dougsz | It can apply arbitrary tags to images | 15:20 |
| dougsz | Are you talking about in CI? | 15:20 |
| witek | we would like to have a job in CI which publishes an image on every version tag in repo | 15:20 |
| Dobroslaw | In CI | 15:20 |
| dougsz | ah got it | 15:20 |
| Dobroslaw | To have stable images more frequently | 15:21 |
| dougsz | So in kolla there is a static file which tracks all the versions, but you can override parts of it. | 15:21 |
| dougsz | I will have a look at exactly what goes on in CI and report back next week | 15:22 |
| Dobroslaw | Thank you | 15:22 |
| dougsz | np | 15:22 |
| witek | #topic email notification templating | 15:23 |
| *** openstack changes topic to "email notification templating (Meeting topic: monasca)" | 15:23 | |
| pandy | Hi witek, its mine | 15:23 |
| pandy | I can say that would like to contribute to monasca by customising notification template | 15:24 |
| pandy | Hope dougsz already in testing phase of slack notification, I would like to work similar on email body customisation | 15:24 |
| pandy | Currently email body looks like this http://paste.openstack.org/show/747345/ | 15:25 |
| pandy | From end user comments, It will be good if customise mail subject & body with more simple information. | 15:25 |
| pandy | Looking forward witek & dougsz and all advise here | 15:26 |
| witek | as a final goal it would be great to have an API to control how the notification method looks like | 15:26 |
| dougsz | Yeah, so tenants can customise it individually per project | 15:27 |
| witek | it could be added as parameter to create-notification method | 15:27 |
| pandy | Yes, but here looking forward everyone advise. From our user comments need tenant_name in mail body and subject | 15:27 |
| witek | and then persisted in SQL DB | 15:27 |
| 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:28 |
| 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:30 |
| mohankumar | pandy : I like to ve this feature in Monasca, If you need any help please let me know . we can collaborate | 15:31 |
| witek | I think we could start with putting some requirements and implementation plan to the story | 15:33 |
| 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:33 |
| pandy | witek, yes thats am looking from you all, So I can work on | 15:34 |
| witek | what we want is to have some easy to edit template which would control the shape of notification message | 15:34 |
| joadavis | and have some simple defaults, like a generic message with simple formatting. | 15:35 |
| witek | to follow the spirit of Monasca we would like to have an API resource to control this templates | 15:35 |
| witek | but that could be a second step | 15:35 |
| 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:36 |
| witek | I rather thought about persisting it in the DB | 15:38 |
| mohankumar | witek: agree | 15:38 |
| pandy | witek, please add your comments in https://storyboard.openstack.org/#!/story/2005111, so can follow up | 15:39 |
| witek | probably would fit best in POST notification-methods | 15:40 |
| witek | https://github.com/openstack/monasca-api/blob/master/docs/monasca-api-spec.md#post-v20notification-methods | 15:40 |
| witek | mohankumar: and yes, the users should be able to add own templates | 15:41 |
| witek | pandy: I guess you can start extending the story based on that discussion | 15:42 |
| pandy | sure, I do. | 15:42 |
| witek | thanks | 15:42 |
| pandy | :) | 15:43 |
| witek | cool, some more questions on that? | 15:44 |
| pandy | Nope, witek. will get back if have doubts :) | 15:45 |
| witek | thanks, that's all from me | 15:45 |
| witek | I'll be wrapping up if there's nothing else | 15:45 |
| pandy | Thank you all | 15:46 |
| witek | thank you | 15:46 |
| dougsz | Thanks all, until next week | 15:46 |
| witek | see you next week | 15:46 |
| joadavis | Nothing else | 15:46 |
| Dobroslaw | Thanks | 15:46 |
| witek | buy | 15:46 |
| haru5ny | thank you | 15:46 |
| witek | bye :) | 15:46 |
| joadavis | Til next time. :) | 15:46 |
| witek | #endmeeting | 15:46 |
| *** openstack changes topic to "OpenStack Monitoring as a Service | https://wiki.openstack.org/wiki/Monasca" | 15:46 | |
| openstack | Meeting ended Wed Mar 6 15:46:41 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:46 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/monasca/2019/monasca.2019-03-06-15.00.html | 15:46 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/monasca/2019/monasca.2019-03-06-15.00.txt | 15:46 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/monasca/2019/monasca.2019-03-06-15.00.log.html | 15:46 |
| *** haru5ny has quit IRC | 15:46 | |
| *** pandy has quit IRC | 15:49 | |
| *** pcaruana has quit IRC | 15:53 | |
| *** pcaruana has joined #openstack-monasca | 16:06 | |
| *** pcaruana has quit IRC | 16:55 | |
| *** zenirc369 has quit IRC | 16:56 | |
| *** mohankumar has quit IRC | 17:00 | |
| *** witek has quit IRC | 18:59 | |
| *** dougsz has quit IRC | 19:05 | |
| *** kaiokmo has quit IRC | 19:07 | |
| *** kaiokmo has joined #openstack-monasca | 19:38 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!