Wednesday, 2020-07-29

*** k_mouza has joined #openstack-monasca00:15
*** k_mouza has quit IRC00:20
*** adriancz has quit IRC00:22
*** k_mouza has joined #openstack-monasca01:31
*** k_mouza has quit IRC01:36
*** k_mouza has joined #openstack-monasca02:45
*** k_mouza has quit IRC02:50
*** k_mouza has joined #openstack-monasca03:27
*** k_mouza has quit IRC03:31
*** brtknr has quit IRC06:17
*** vishalmanchanda has joined #openstack-monasca06:39
*** nikparasyr has joined #openstack-monasca06:53
*** dougsz has joined #openstack-monasca07:32
*** tosky has joined #openstack-monasca07:39
*** brtknr has joined #openstack-monasca08:47
*** witek has joined #openstack-monasca09:07
*** witek has quit IRC09:09
*** k_mouza has joined #openstack-monasca09:29
*** witek has joined #openstack-monasca10:39
nikparasyrhello :). a couple of notes about the influx HA setup. couple of weeks ago i mentioned setting the legacy_kafka_client_enabled = false on persister.conf, allowed it to work properly. last week i changed that option on api.conf as well but that lead to errors -- im not sure on which service now and logs are flushed. I saw that upstream the default value is set to false. So my remark is that we might need to check if it works pr12:23
nikparasyroperly if set on api.conf12:23
nikparasyrim currently running monasca train on a test cluster, so i can enable it again and provide logs etc. let me know12:24
nikparasyrapologies for not setting it and mentioning it earlier12:24
nikparasyranother thing, which i sort of want to see if there are ppl interested in this. This is mostly a kolla-ansible "proposal" but i want to run it through here. We have deployed a stand-alone 3-node monasca cluster with external keystone with kolla-ansible. this works quite well. We have 2 configurations, one for the openstack cluster and one for the monasca cluster. The issue we have now is that with k-a we cannot config the mona12:28
nikparasyrsca role to only deploy the agent on the openstack nodes.12:28
nikparasyrI am thinking of making functionality on the k-a monasca role to define external_monasca and then only services such as the agent are configured and deployed on the nodes. similarly ceilometer config is changed to make it work for monasca etc12:29
nikparasyrIs this something that makes sense and we expect more ppl to need/require it? if yes i could make a blueprint on k-a about this change and start working on it (not in the next couple of weeks though)12:30
dougsznikparasyr: good questions - will reply in an hour or so when I am out of the current meeting.13:03
*** piotrowskim has joined #openstack-monasca13:46
dougsznikparasyr: So about the first point - I'm working on that now. It seems to work fine on master, but we're going to run Monasca Tempest against it in CI to be sure14:13
dougszAbout the other question - it's a good idea to decouple Monasca Agent from the Monasca to support what you need.14:15
dougszWe already have a similar mechanism with Prometheus + Prometheus Exporters threre14:15
dougszIt would get my +2!14:15
dougszI wouldn't worry about a blueprint for it, just propose it when you have time.14:16
dougszOne thing I was thinking about the consumer groups change is that we could use sticky sessions so the user hits the same InfluxDB instance each time they refresh14:18
dougszAnd also for Tempest14:18
dougszwhich suffers race conditions with multiple Influx instances14:19
nikparasyrok. i think the prometheus + prometheus exporters was introduced recently so i will have a look into how you decoupled that one14:20
nikparasyri might need some help with some "design" decisions. also i've only made one upstream change to k-a (yday) so it might take some time to get used to the workflow and conventions used. but only one way to learn14:21
nikparasyrabout the sticky sessions i've seen the story/todo on the WIP you have. i havent worked a lot with sticky sessions on haproxy but it seems like a good addition14:21
nikparasyranother thing which i am a bit sceptical is that on a 3-node setup you get 3 grafana's which is... well weird. for the time being i changed the inventory to only deploy one14:24
dougsznikparasyr: no problem - I think you have got the workflow correct and happy to help out with any design14:41
dougszAre you accessing Grafana via the VIP/HAProxy?14:42
nikparasyryep14:42
dougszThe idea is that all Grafana instances store state in the MariaDB cluster14:42
nikparasyrhmmm, wasnt aware of that. so basically configuring lets say a data source to one will make the datasource to all 3, etc with dashboards14:43
dougszSo to the end user won't be aware of which instance they use since they are all identical14:43
dougszyeah, that's correct, because they are configured to use the DB14:43
nikparasyroh wasnt aware of that. that's great actually :) thanks!14:44
dougsznp! For loading dashboards this is one option: https://github.com/stackhpc/ansible-role-grafana-conf14:44
dougszWe were planning on adding to KA, but no time yet14:44
dougszAnd this for generating dashboards: https://github.com/stackhpc/grafana-reference-dashboards14:45
*** irclogbot_0 has quit IRC14:52
*** irclogbot_2 has joined #openstack-monasca14:59
nikparasyrok thanks for the dashboards as well :)15:06
*** nikparasyr has left #openstack-monasca15:16
*** k_mouza has quit IRC16:09
*** k_mouza has joined #openstack-monasca16:28
*** dougsz has quit IRC16:31
*** k_mouza has quit IRC16:33
*** witek has quit IRC16:45
*** k_mouza has joined #openstack-monasca16:46
*** k_mouza has quit IRC16:50
*** k_mouza has joined #openstack-monasca16:57
*** k_mouza has quit IRC17:01
*** k_mouza has joined #openstack-monasca17:15
*** k_mouza has quit IRC17:19
*** k_mouza has joined #openstack-monasca17:35
*** k_mouza has quit IRC17:39
*** k_mouza has joined #openstack-monasca17:54
*** k_mouza has quit IRC17:58
*** k_mouza has joined #openstack-monasca18:10
*** k_mouza has quit IRC18:14
*** vishalmanchanda has quit IRC18:29
*** k_mouza has joined #openstack-monasca18:31
*** k_mouza has quit IRC18:39
*** k_mouza has joined #openstack-monasca19:22
*** k_mouza has quit IRC19:27
*** k_mouza has joined #openstack-monasca19:33
*** k_mouza has quit IRC19:37
*** k_mouza has joined #openstack-monasca19:42
*** k_mouza has quit IRC19:47
*** k_mouza has joined #openstack-monasca20:05
*** k_mouza has quit IRC20:09
*** piotrowskim has quit IRC23:12
*** tosky has quit IRC23:21

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!