13:00:12 #startmeeting monasca 13:00:12 Meeting started Tue Nov 9 13:00:12 2021 UTC and is due to finish in 60 minutes. The chair is chaconpiza. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:00:12 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:00:12 The meeting name has been set to 'monasca' 13:00:31 Hi 13:00:49 Hi Adrian 13:01:19 I came back from vacations 13:01:22 Let's start 13:01:35 The agenda as usual https://etherpad.opendev.org/p/monasca-team-meeting-agenda 13:02:11 #topic [WIP] Adding parameters 'time' and 'times' by creating Alarm Definitions in Monasca-UI 13:02:39 Yes, cementy I'm working on this topic 13:02:40 This is one of the topics from the PTG priorities 13:03:23 I created change for that 13:03:24 https://review.opendev.org/c/openstack/monasca-ui/+/815961 13:03:42 This still WIP 13:03:55 but main functionality is working 13:04:35 As discussed internally, I already stacked Devstack with the 1st patch set of your change. It looks promising! 13:04:45 is possible to create Alarm Definitione with time and times parameters 13:05:50 Yes, main funcionality is working. It is an important improvement for all the Monasca users that use Monasca-UI Horizon's plugin. 13:07:36 In our specific experience, one client requires to set all Alarm Definitions with time/times parameters different than 60/1 respectively. 13:08:27 Ok, let's go to next topic... 13:09:24 This is a change for Monasca-UI too: 13:09:33 "Change policy file format to yaml" 13:09:41 https://review.opendev.org/c/openstack/monasca-ui/+/816125 13:10:06 from Oleksandr Kozachenko 13:10:27 he already contributed to Monasca previously 13:11:28 This change looks good 13:12:16 Yes, at first glance it looks ok. I will stack a Devstack with the change an check it. 13:12:48 Cherry picks are available for Wallaby and Xena too 13:13:33 this change recall us that we need to do the a similar change (at least) for Monasca-API 13:14:15 I executed before the meeting all Tox tests, they are on green... but PY38 with a lot of warnings like: 13:14:25 2021-11-09 13:51:19.047 5134 WARNING oslo_policy.policy [-] JSON formatted policy_file support is deprecated since Victoria release. You need to use YAML format which will be default in future. You can use ``oslopolicy-convert-json-to-yaml`` tool to convert existing JSON-formatted policy file to YAML-formatted in backward compatible way: 13:14:25 https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html. 13:16:10 So Adrian, please continue working in the time/times change in Monasca-UI and I will take care of these changes 'oslopolicy-convert-json-to-yaml' 13:16:21 + 1 13:17:35 One more thing, recently we had to use a Workaround in Monasca-Agent: https://review.opendev.org/c/openstack/monasca-agent/+/813692 13:18:35 I abandoned this change 13:18:43 This change is no longer needed 13:18:59 it was because of Oslo-vmware. They already fixed the issue: https://github.com/openstack/oslo.vmware/commit/7bc343173751330d2e989c28bc6fefed56d358d6 13:19:28 Yes, the change is no longer needed. 13:19:58 btw. in Monasca-Agent we don't use the lower-constraints 13:20:20 (because Monasca-Agent is meant to be installed in a virtual-env.) 13:21:09 otherwise, we should upgrade oslo-wmware to the version 3.10.0 13:23:35 last but not least, we got this question: 13:23:35 http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025654.html 13:24:53 question from Adam Tomas from Poland 13:26:09 any ideas? 13:26:12 I think i this case we can add extra configuration for max deseniom length 13:27:49 I think that Adam's question is about the other places besides monasca-api> 13:28:04 This error looks very strange 13:28:05 "..,but how to check if this max value do not cause problems in monasca_log_transformer or any other service in the stack (kafka/monasca_persister/elasticsearch)?" 13:29:27 this should not cause any problem in transformer or persister 13:30:41 I will stack a Devstack with log-pipe line and check the messages in kafka after monasca-api, log-transformet and how they came in log-persister. 13:30:53 +1 13:31:03 otherwise would be difficult to confirm it. 13:35:34 so, those are all topics for now 13:36:45 do you have any other topic for today? 13:37:16 Nothing from me 13:37:42 Then let's close the meeting. 13:37:52 Thanks for coming, see you next week. 13:38:12 Thanks 13:38:20 #endmeeting