| chaconpiza | #startmeeting monasca | 13:00 |
|---|---|---|
| opendevmeet | 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 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:00 |
| opendevmeet | The meeting name has been set to 'monasca' | 13:00 |
| adriancz | Hi | 13:00 |
| chaconpiza | Hi Adrian | 13:00 |
| chaconpiza | I came back from vacations | 13:01 |
| chaconpiza | Let's start | 13:01 |
| chaconpiza | The agenda as usual https://etherpad.opendev.org/p/monasca-team-meeting-agenda | 13:01 |
| chaconpiza | #topic [WIP] Adding parameters 'time' and 'times' by creating Alarm Definitions in Monasca-UI | 13:02 |
| adriancz | Yes, cementy I'm working on this topic | 13:02 |
| chaconpiza | This is one of the topics from the PTG priorities | 13:02 |
| adriancz | I created change for that | 13:03 |
| adriancz | https://review.opendev.org/c/openstack/monasca-ui/+/815961 | 13:03 |
| adriancz | This still WIP | 13:03 |
| adriancz | but main functionality is working | 13:03 |
| chaconpiza | As discussed internally, I already stacked Devstack with the 1st patch set of your change. It looks promising! | 13:04 |
| adriancz | is possible to create Alarm Definitione with time and times parameters | 13:04 |
| chaconpiza | Yes, main funcionality is working. It is an important improvement for all the Monasca users that use Monasca-UI Horizon's plugin. | 13:05 |
| chaconpiza | In our specific experience, one client requires to set all Alarm Definitions with time/times parameters different than 60/1 respectively. | 13:07 |
| chaconpiza | Ok, let's go to next topic... | 13:08 |
| chaconpiza | This is a change for Monasca-UI too: | 13:09 |
| chaconpiza | "Change policy file format to yaml" | 13:09 |
| chaconpiza | https://review.opendev.org/c/openstack/monasca-ui/+/816125 | 13:09 |
| chaconpiza | from Oleksandr Kozachenko | 13:10 |
| chaconpiza | he already contributed to Monasca previously | 13:10 |
| adriancz | This change looks good | 13:11 |
| chaconpiza | Yes, at first glance it looks ok. I will stack a Devstack with the change an check it. | 13:12 |
| chaconpiza | Cherry picks are available for Wallaby and Xena too | 13:12 |
| chaconpiza | this change recall us that we need to do the a similar change (at least) for Monasca-API | 13:13 |
| chaconpiza | I executed before the meeting all Tox tests, they are on green... but PY38 with a lot of warnings like: | 13:14 |
| chaconpiza | 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 |
| chaconpiza | https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html. | 13:14 |
| chaconpiza | 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 |
| adriancz | + 1 | 13:16 |
| chaconpiza | One more thing, recently we had to use a Workaround in Monasca-Agent: https://review.opendev.org/c/openstack/monasca-agent/+/813692 | 13:17 |
| adriancz | I abandoned this change | 13:18 |
| adriancz | This change is no longer needed | 13:18 |
| chaconpiza | it was because of Oslo-vmware. They already fixed the issue: https://github.com/openstack/oslo.vmware/commit/7bc343173751330d2e989c28bc6fefed56d358d6 | 13:18 |
| chaconpiza | Yes, the change is no longer needed. | 13:19 |
| chaconpiza | btw. in Monasca-Agent we don't use the lower-constraints | 13:19 |
| chaconpiza | (because Monasca-Agent is meant to be installed in a virtual-env.) | 13:20 |
| chaconpiza | otherwise, we should upgrade oslo-wmware to the version 3.10.0 | 13:21 |
| chaconpiza | last but not least, we got this question: | 13:23 |
| chaconpiza | http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025654.html | 13:23 |
| chaconpiza | question from Adam Tomas from Poland | 13:24 |
| chaconpiza | any ideas? | 13:26 |
| adriancz | I think i this case we can add extra configuration for max deseniom length | 13:26 |
| chaconpiza | I think that Adam's question is about the other places besides monasca-api> | 13:27 |
| adriancz | This error looks very strange | 13:28 |
| chaconpiza | "..,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:28 |
| adriancz | this should not cause any problem in transformer or persister | 13:29 |
| chaconpiza | 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 |
| adriancz | +1 | 13:30 |
| chaconpiza | otherwise would be difficult to confirm it. | 13:31 |
| chaconpiza | so, those are all topics for now | 13:35 |
| chaconpiza | do you have any other topic for today? | 13:36 |
| adriancz | Nothing from me | 13:37 |
| chaconpiza | Then let's close the meeting. | 13:37 |
| chaconpiza | Thanks for coming, see you next week. | 13:37 |
| adriancz | Thanks | 13:38 |
| chaconpiza | #endmeeting | 13:38 |
| opendevmeet | Meeting ended Tue Nov 9 13:38:20 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:38 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/monasca/2021/monasca.2021-11-09-13.00.html | 13:38 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/monasca/2021/monasca.2021-11-09-13.00.txt | 13:38 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/monasca/2021/monasca.2021-11-09-13.00.log.html | 13:38 |
| adriancz | See you next week | 13:38 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!