*** dangtrinhnt has left #openstack-monasca | 00:55 | |
*** pandy has joined #openstack-monasca | 06:16 | |
*** pcaruana has joined #openstack-monasca | 06:19 | |
*** witek has joined #openstack-monasca | 08:35 | |
*** pandy has quit IRC | 09:07 | |
*** dougsz has joined #openstack-monasca | 09:10 | |
*** pandy has joined #openstack-monasca | 09:46 | |
*** mohankumar has joined #openstack-monasca | 09:50 | |
mohankumar | Hi @witek @dougsz one qq , is it possiple one user (admin) to read alarms from across all tenents ? | 09:51 |
---|---|---|
dougsz | They need the correct role in all the projects | 09:52 |
witek | and iterate across the projects | 09:53 |
mohankumar | say for (e.g) i need to list all the alarms using monasca alarm-list using keystone admin user . | 09:54 |
mohankumar | now with admin user i can list only alarms configured for admin tenant | 09:55 |
mohankumar | @dougsz : I ve added admin user in all the projects and assigned admin role | 09:56 |
dougsz | you can change the OS_PROJECT env var and then list alarms in each project individually as witek says above | 09:56 |
pandy | https://github.com/openstack/monasca-agent/blob/master/docs/MonascaMetrics.md#cross-tenant-metric-submission | 09:56 |
dougsz | (assuming you are using env vars for auth) | 09:57 |
pandy | in sourcerc file for OS_PROJECT try to iterate all projects from "openstack project list" | 09:58 |
mohankumar | dougsz , witek: yes that can be done . But every time I query alarm list for particular projects (tenants) I'm afraid more keystone hits will happen to fetch project specific tokens | 10:01 |
*** pandy has quit IRC | 10:03 | |
mohankumar | **In my case I've more projects ~800-1000 projects | 10:04 |
*** pandy has joined #openstack-monasca | 10:05 | |
witek | do you define the alarms for every project individually? | 10:06 |
mohankumar | yes | 10:07 |
mohankumar | I use grafana to create alarms | 10:07 |
mohankumar | witek , if i use cli , may it help ? | 10:08 |
witek | you could automate the process, but the problem remains the same | 10:08 |
mohankumar | witek : so current code base , we don't ve this option right to list alarms from cross tenants with single api call? | 10:10 |
witek | I think it's a valid use case, we could think about adding a convenience function to get all alarms across the tenants | 10:10 |
witek | no | 10:11 |
mohankumar | witek : yes , it helps if we could add this option , something like "monasca alarm-list --all-projects" | 10:12 |
mohankumar | can I take it forward ? | 10:12 |
witek | sure, that would be great | 10:13 |
mohankumar | witek : Thanks ! | 10:13 |
witek | please start with the story describing the motivation and expected result | 10:14 |
mohankumar | witek : yes sure | 10:14 |
*** pandy has joined #openstack-monasca | 10:15 | |
witek | we should also think about restricting access to this resource only for admins | 10:15 |
mohankumar | witek : agree | 10:20 |
*** pandy has quit IRC | 10:20 | |
*** pandy has joined #openstack-monasca | 10:23 | |
pandy | similar like openstack server list --all-tenants | 10:25 |
pandy | Sorry my network went down and just noticed all my messages are back logged | 10:26 |
pandy | witek, I am agreed with mohankumar & keystone hit will be more for large project numbers, can have dedicated api or customised parameters to monasca similar like "server list --all-projects" | 10:31 |
*** chaconpiza has joined #openstack-monasca | 10:33 | |
pandy | witek, FYI regarding customising mail template, added new notification type as "CUSTOM_MAIL" to monasca-client and doing necessary changes in monasca-notification, will send merge request to review | 10:35 |
openstackgerrit | jianweizhang proposed openstack/monasca-api master: monasca-api can not config cassandra cluster port https://review.openstack.org/642216 | 10:35 |
witek | thanks pandy | 10:38 |
*** mohankumar has quit IRC | 10:57 | |
openstackgerrit | Daisuke Fujita proposed openstack/monasca-analytics master: add download_file function in devstack plugin.sh https://review.openstack.org/437215 | 11:02 |
*** dougsz has quit IRC | 11:50 | |
*** dougsz has joined #openstack-monasca | 12:19 | |
*** dougsz has quit IRC | 12:28 | |
*** dougsz has joined #openstack-monasca | 12:38 | |
openstackgerrit | Dobroslaw Zybort proposed openstack/monasca-common master: Don't remove tempest tests from installation folder https://review.openstack.org/643036 | 12:40 |
*** pandy has quit IRC | 12:41 | |
*** pandy has joined #openstack-monasca | 12:41 | |
*** dougsz has quit IRC | 13:12 | |
openstackgerrit | Merged openstack/monasca-common master: Support full links in Docker wait script https://review.openstack.org/642742 | 13:43 |
openstackgerrit | Adrian Czarnecki proposed openstack/monasca-api master: [WIP] Add unit test https://review.openstack.org/641631 | 14:01 |
*** irclogbot_2 has quit IRC | 14:09 | |
openstackgerrit | Dobroslaw Zybort proposed openstack/monasca-tempest-plugin master: Create Docker image and build in Zuul https://review.openstack.org/640361 | 14:10 |
*** irclogbot_2 has joined #openstack-monasca | 14:11 | |
openstackgerrit | MichaĆ Piotrowski proposed openstack/python-monascaclient master: Create Docker image and build in Zuul https://review.openstack.org/640033 | 14:19 |
*** irclogbot_2 has quit IRC | 14:25 | |
*** irclogbot_2 has joined #openstack-monasca | 14:26 | |
*** dougsz has joined #openstack-monasca | 14:29 | |
openstackgerrit | Merged openstack/monasca-api master: Improve tests coverage https://review.openstack.org/632718 | 14:52 |
openstackgerrit | Merged openstack/monasca-common master: Don't remove tempest tests from installation folder https://review.openstack.org/643036 | 14:52 |
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 | 15:01 |
witek | #startmeeting monasca | 15:01 |
openstack | Meeting started Wed Mar 13 15:01:29 2019 UTC and is due to finish in 60 minutes. The chair is witek. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:01 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:01 |
*** openstack changes topic to " (Meeting topic: monasca)" | 15:01 | |
openstack | The meeting name has been set to 'monasca' | 15:01 |
witek | hello | 15:01 |
dougsz | \o hey | 15:01 |
Dobroslaw | Hi | 15:01 |
witek | hi dougsz and Dobroslaw | 15:01 |
witek | please put items into agenda if you have any | 15:02 |
witek | https://etherpad.openstack.org/p/monasca-team-meeting-agenda | 15:02 |
witek | and if not we can go through the list of new changes in review | 15:03 |
witek | #topic reviews | 15:03 |
*** openstack changes topic to "reviews (Meeting topic: monasca)" | 15:03 | |
witek | https://review.openstack.org/642082 | 15:04 |
witek | first one from Stig | 15:04 |
dougsz | Still need to review that one | 15:05 |
dougsz | My main concern is making sure it's backwards compatible | 15:05 |
*** hosanai has joined #openstack-monasca | 15:05 | |
witek | it gets some configuration details from Ceph config file and configures the plugin using that, right? | 15:06 |
dougsz | ah yes, there is another change in the pipeline I am thinking of | 15:07 |
witek | I see, not published yet | 15:07 |
Dobroslaw | It looks mostly as handling edge case | 15:08 |
witek | OK, the next two are the changes for Cassandra | 15:10 |
witek | https://review.openstack.org/642372 | 15:10 |
witek | https://review.openstack.org/642216 | 15:10 |
witek | good to see some changes there after a long time | 15:11 |
witek | building Docker image for python client: | 15:12 |
witek | https://review.openstack.org/640033 | 15:12 |
Dobroslaw | I will test it tomorrow, code looks fine for me now | 15:13 |
witek | is it enough to run `./build_image.sh` to try it out? | 15:13 |
Dobroslaw | Yes | 15:13 |
witek | and how can the client be used afterwards? | 15:14 |
Dobroslaw | Like for connecting to existing network of docker comppse | 15:15 |
witek | any example? what should I run if I would like to list metrics for example? | 15:15 |
Dobroslaw | Ugh, I'm writing from phone now, will sent you tomorrow | 15:16 |
witek | I'll ask in review :) | 15:16 |
Dobroslaw | OK | 15:16 |
*** mohankumar has joined #openstack-monasca | 15:17 | |
Dobroslaw | Readme could be updated with more examples | 15:17 |
witek | next one: | 15:18 |
witek | https://review.openstack.org/#/c/632718/ | 15:18 |
witek | oh, merged already | 15:18 |
witek | great | 15:18 |
Dobroslaw | Merged already :-) | 15:19 |
witek | +2000 lines | 15:19 |
joadavis | impressive | 15:19 |
Dobroslaw | All thanks to adriancz | 15:19 |
witek | good job, that's pre step for API merging | 15:20 |
witek | any other reviews? | 15:20 |
pandy | witek, am submitting review for custom email notification in couple of minutes | 15:21 |
dougsz | Good stuff! adriancz | 15:21 |
witek | #topic bugs | 15:22 |
*** openstack changes topic to "bugs (Meeting topic: monasca)" | 15:22 | |
witek | we have three bug reports in etherpad | 15:23 |
witek | https://storyboard.openstack.org/#!/story/2005224 | 15:23 |
openstackgerrit | Pandiyan proposed openstack/monasca-notification master: [WIP] Adding custom_email notification method https://review.openstack.org/643075 | 15:23 |
witek | I think we miss some details here | 15:23 |
dougsz | ^ That one is from the monasca grafana fork | 15:23 |
dougsz | Not the datasource | 15:23 |
dougsz | Questions are: 1) How do we track bugs for that component? | 15:24 |
dougsz | 2) Is the monasca-grafana fork 'supported'? | 15:24 |
witek | we haven't had many bug reports for Grafana fork, so I'm fine with having it in StoryBoard | 15:26 |
witek | althought it would fit better as Github issue | 15:26 |
dougsz | They are disabled at the moment - perhaps we should enable them? | 15:26 |
witek | oh, yes, probably good idea :) | 15:27 |
kaiokmo | I've run through this same issue as well a couple times :) | 15:27 |
dougsz | Yeah, there is no token refresh mechanism. I think you should at least get sent back to the login page. | 15:27 |
kaiokmo | that would make sense | 15:28 |
dougsz | We should hopefully be able to pick it up, as quite a few users complain about it. | 15:28 |
Dobroslaw | Unfortunately adding backend plugins to grafana do not have any progress in last year... | 15:29 |
witek | for supporting Grafana fork, we still don't have a better mechanism if you don't want or cannot proxy requests via Horizon | 15:29 |
witek | what we could do is to start working on adding support for Keystone Application Credentials in Monasca datasource | 15:30 |
dougsz | yeah, that is one promising avenue | 15:31 |
dougsz | Just need to find the manpower | 15:31 |
witek | the problem is, that we're storing these credentials on client, which is a security risk | 15:31 |
witek | the work on adding whitelisting to Application Credentials in Keystone is work in progress though | 15:32 |
witek | so I think we can use them securely soon | 15:32 |
dougsz | I've enabled github issues for the fork and moved the bug report | 15:33 |
witek | thanks dougsz ! | 15:33 |
witek | does Palimariu work with you? | 15:34 |
dougsz | He's a user of a Monasca deployment we've done. | 15:34 |
dougsz | Trying to encourage upstream involvement :) | 15:35 |
witek | I see, very good! | 15:35 |
witek | then we have two security issues | 15:36 |
witek | https://storyboard.openstack.org/#!/story/2005215 | 15:36 |
*** irclogbot_2 has quit IRC | 15:36 | |
*** hosanai has quit IRC | 15:36 | |
pandy | witek, I have initiated custom-email changes for monasca-notification, I need to add test cases for the same and added witek, dougz to review. | 15:37 |
witek | hold on pandy | 15:37 |
joadavis | The two security issues are from a batch I came across last week | 15:37 |
joadavis | they are old ones from a year or so ago, though I still see them in the code | 15:38 |
*** irclogbot_2 has joined #openstack-monasca | 15:38 | |
joadavis | I think these are "hardening opportunities" rather than gaping security issues | 15:38 |
witek | I cannot open https://storyboard.openstack.org/#!/story/2005217 | 15:38 |
dougsz | +1 | 15:38 |
dougsz | 404 | 15:38 |
joadavis | There are a few more in our internal bug tracking which I need to try publishing | 15:38 |
joadavis | Sorry, I think I marked that one with the 'security bug' checkbox, which makes it private | 15:39 |
joadavis | I can go uncheck that | 15:39 |
dougsz | ah, I see | 15:39 |
joadavis | ok, you can try again | 15:39 |
witek | now I can see it | 15:40 |
joadavis | I'll go back through the list today and post any other relevant ones | 15:40 |
joadavis | In general, these seem like small changes. | 15:40 |
witek | should we tag these as bugs, so that these are easier to find? | 15:40 |
joadavis | But I know at least one would likely need a configuration setting to be implemented well | 15:41 |
joadavis | Sure. I wanted to bring it up in this meeting so we can discuss how best to handle them | 15:41 |
dougsz | Thanks for reporting joadavis | 15:41 |
dougsz | https://storyboard.openstack.org/#!/story/2005215 is relevant to you Pandy? | 15:42 |
pandy | dougsz, not relevant to me | 15:43 |
witek | these seem to be small tasks which should be easy to be picked up by anyone | 15:43 |
joadavis | yes. I wish I'd been aware of this internal list months ago, as we could have easily included them in Rocky. | 15:43 |
witek | well, we can have them in Stein or Train :) | 15:44 |
witek | thanks joadavis | 15:45 |
witek | here, pandy's change for email notification templating: | 15:45 |
witek | https://review.openstack.org/643075 | 15:46 |
witek | I've added it to the list on etherpad | 15:46 |
pandy | witek, I have just proposed WIP patch for custom email notification. | 15:46 |
joadavis | cool (and that might be a good pairing with story 2005215) | 15:47 |
pandy | Still I need to add "Tenant_Name" in subject, for that need to through libraries to import. | 15:48 |
witek | I think, I'd rather modify the existing plugin instead of adding a new one | 15:48 |
*** irclogbot_2 has quit IRC | 15:49 | |
witek | ha, the same comment from dougsz in review :) | 15:49 |
dougsz | :) | 15:49 |
pandy | yes, I was thought about it, but don't want to change existing functionality did like this | 15:50 |
witek | thanks for the change pandy | 15:50 |
*** irclogbot_2 has joined #openstack-monasca | 15:50 | |
witek | do you think you can do the second step of adding it to the API after that one is merged? | 15:51 |
pandy | You mean after python-client changes ? | 15:52 |
*** irclogbot_2 has quit IRC | 15:52 | |
dougsz | Both really, so users can set custom templates from the client, and the API supports that operation | 15:53 |
witek | yes | 15:53 |
pandy | dougsz, yes. I feel good to have new plugins without touching existing one, so users can choose as their wish | 15:54 |
dougsz | A fair bit of work there I would imagine, I assume we would store templates in the DB | 15:54 |
witek | new point in the agenda | 15:55 |
*** irclogbot_2 has joined #openstack-monasca | 15:55 | |
pandy | yes, dougsz need to store in DB, which witek conveyed last time | 15:55 |
witek | #topic building Kolla images | 15:55 |
*** openstack changes topic to "building Kolla images (Meeting topic: monasca)" | 15:55 | |
dougsz | ah yes, so this came up last week, totally possible. | 15:55 |
witek | do you know any details, I guess Dobroslaw is interested | 15:56 |
dougsz | You can easily get Kolla to build per repo images. | 15:57 |
pandy | Sorry to interupt. witek, dougsz hope both are agreed to have new plugins, if need to do changes in existing one please let me know, so I can find the possiblities. | 15:57 |
dougsz | I think the configuration mechanism is quite different to the existing Monasca docker images | 15:57 |
dougsz | As Dobroslaw knows :) | 15:57 |
Dobroslaw | Yes | 15:57 |
Dobroslaw | Providing config files Vs env variables | 15:58 |
dougsz | The images are also fairly heavyweight - either Debian or Centos based | 15:58 |
dougsz | On the plus side, the Kolla images maintained to some extent by the Kolla team | 15:59 |
dougsz | *are maintained | 15:59 |
witek | if I understood correctly, we had a problem with triggering the CI job when tagging the repo | 16:00 |
dougsz | pandy: I would rather not have a duplicate plugin, would be nice if we have one email plugin, and it does it's job well | 16:00 |
witek | I have to jump to another meeting | 16:00 |
witek | see you next week | 16:01 |
witek | bye | 16:01 |
dougsz | np, thanks all | 16:01 |
Dobroslaw | Thanks | 16:01 |
witek | #endmeeting | 16:01 |
*** openstack changes topic to "OpenStack Monitoring as a Service | https://wiki.openstack.org/wiki/Monasca" | 16:01 | |
openstack | Meeting ended Wed Mar 13 16:01:16 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:01 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/monasca/2019/monasca.2019-03-13-15.01.html | 16:01 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/monasca/2019/monasca.2019-03-13-15.01.txt | 16:01 |
openstack | Log: http://eavesdrop.openstack.org/meetings/monasca/2019/monasca.2019-03-13-15.01.log.html | 16:01 |
Dobroslaw | pandy: maybe it would be possible to have such defaults that for end user there will be no difference with old mail plugin | 16:02 |
joadavis | +1. Then you could put the new custom templating in place in the existing email plugin | 16:03 |
Dobroslaw | Difference only would be that user could provide custom template if he want | 16:03 |
pandy | dougsz, understand. | 16:03 |
dougsz | pandy, if you look at the Slack template patch in review, it should only change the default behaviour *if* a template is provided | 16:04 |
pandy | dougsz, yes, just had a look. I will refer it :) | 16:05 |
*** sum12 has left #openstack-monasca | 16:07 | |
*** mohankumar has quit IRC | 16:07 | |
*** sum12 has joined #openstack-monasca | 16:10 | |
*** jamesgu__ has joined #openstack-monasca | 17:39 | |
*** pandy has quit IRC | 17:48 | |
*** dougsz has quit IRC | 17:58 | |
*** pcaruana has quit IRC | 18:29 | |
*** gmann is now known as gmann_afk | 18:48 | |
*** sum12 has quit IRC | 19:51 | |
*** sum12 has joined #openstack-monasca | 19:51 | |
*** gmann_afk is now known as gmann | 20:41 | |
*** witek has quit IRC | 21:21 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!