13:00:11 #startmeeting monasca 13:00:12 Meeting started Tue Jul 14 13:00:11 2020 UTC and is due to finish in 60 minutes. The chair is chaconpiza. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:00:13 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:00:15 The meeting name has been set to 'monasca' 13:00:21 hello all 13:00:25 hi 13:00:37 Hello Doug 13:00:40 Hello Witek 13:00:55 The agenda as usual https://etherpad.opendev.org/p/monasca-team-meeting-agenda 13:01:55 The only one topic from the agenda is related to the action items from last week 13:02:52 #topic monasca-persister branch/master openstack-tox-py38 13:03:49 I checked for the monasca-projects that the tarballs are created and published 13:04:33 There is only a change waiting: https://review.opendev.org/#/c/722515/ 13:05:37 in the new PY38 only a test case fails https://opendev.org/openstack/monasca-persister/src/branch/master/monasca_persister/tests/test_token_range_query_manager.py#L51 13:05:58 hmm 13:06:20 I had a look at the trace log, but nothing comes to my mind 13:06:34 In Victoria adds PY38 as a Runtime https://governance.openstack.org/tc/reference/runtimes/victoria.html#python-runtimes-for-victoria 13:07:28 Same test case is working on py36 13:08:43 you might ask at #openstack-infra or in the mailing list 13:09:02 I'll try to have a closer look as well 13:09:40 right, I searched for differences in multiprocessing between py36 and py38 13:09:54 but I can't find nothing. 13:10:43 The two test cases in that file were written by Arseni, I will ask whether he as an idea. 13:10:48 he has* 13:12:02 at the last instance, we should disable these tests, I don't think they are very useful 13:14:22 There are two test_query and test_close_pool I tried locally just removing test_close_pool and then py38 tests pass 13:15:48 Ok, continuing the investigation. At the last instance removing test_close_pool. 13:16:11 I'd tip on differences in exception handling between Python versions 13:16:36 right 13:17:05 still trying to reproduce locally, but will see if I spot anything when I do 13:18:06 I'll have to install 3.8 first ;) openSUSE Leap comes with 3.6 13:18:57 I ran it on Ubuntu 18.04 I had to install python3.8 (adding dead sneaks repo) 13:19:14 and important python3.8-dev package too 13:19:18 Witold Bedyk proposed openstack/monasca-api master: Set legacy_kafka_client_enabled = False on default https://review.opendev.org/740954 13:19:26 I am behind you on that path chaconpiza 13:20:23 Thanks for the change https://review.opendev.org/740954 witek, it is part of the action topics from last week. 13:20:42 right, I've created a story: 13:20:48 https://storyboard.openstack.org/#!/story/2007924 13:20:57 and added to the board: 13:21:02 https://storyboard.openstack.org/#!/board/217 13:21:04 great 13:21:35 Thanks Witek - trying this out at the moment - will you update the others? 13:21:55 yes, should be ready today 13:22:02 :) 13:23:29 I forget - on that topic - did you try unpinning the Kafka messaging version yet? 13:24:28 I think not 13:25:18 the only problems could be related with monasca-thresh 13:25:45 yeah - now that we have modern logstash 13:26:31 Ok, the next action from last week is about the migration of CI/CD jobs to new Ubuntu LTS Focal. It still on my ToDo list. 13:26:48 Hello Witek, Martin.. 13:26:52 Could you please give reference of people who worked in monasca-analytics? 13:27:30 sure, I'll send you in private message 13:27:37 thanks :) 13:27:56 Hi Manik 13:28:41 The info is public: https://review.opendev.org/#/q/owner:fuzita.daisuke 13:29:04 https://review.opendev.org/#/q/owner:osanai.hisashi 13:29:31 ohh.ok 13:31:01 #topic AOB 13:32:45 Previously I said that the new RedHat OSP 16 was using Kolla, but it is not fully true. It is using TripleO for deployment. The containers that TripleO uses are the same containers that Kolla creates. 13:33:39 But OSP16 don't deploy using Kolla-Ansibe. 13:34:02 hm, yeah, and don't they heavily customise them? 13:34:40 and build a subset? 13:34:52 Yes, and OSP container repository is not Docker Hub, but "registry.redhat.io" 13:36:32 Not sure about OSP16 support in Kolla Ansible as well - Centos 8 is fully supported now at least 13:36:54 might just work, but not sure 13:37:07 (Train release onwards) 13:38:17 On Centos8 with tripleO I was able to deploy the containers from Ussuri successfully 13:39:07 Witold Bedyk proposed openstack/monasca-notification master: Set legacy_kafka_client_enabled = False on default https://review.opendev.org/740959 13:39:23 OpenStack core + Monasca? 13:40:15 But using OSP16 13:40:59 I am worndering how to provide to the custumer the Monasca-plugin for Horizon 13:41:14 since Horizon will be now running in a container 13:41:28 so the setup was, OSP16 + Monasca Ussuri from Kolla? 13:42:41 OSP16 (which is based on Train) + Monasca 13:43:46 Monasca images from where though? 13:44:52 In OSP16 server will run the metric-agent and log-agent bare-metal 13:45:53 and we need to modify (or patch) the Horizon container in order to add the monitoring menus 13:46:23 The rest of services of Monasca will be deployed in other server with docker-compose 13:46:33 If you're using Kolla Monasca images, you should be able to add the plugin via this var: https://github.com/openstack/kolla/blob/master/docker/horizon/Dockerfile.j2#L14 13:47:26 (https://docs.openstack.org/kolla/latest/admin/image-building.html#generic-customisation) 13:47:26 Great, I will try it 13:48:01 Cool - I should patch it into the Kolla image anyway, but it will be Victoria onwards 13:49:51 was something blocking adding Monasca to Horizon? 13:50:26 or simply was not a priority 13:50:39 Nothing at all blocking 13:50:47 cool 13:51:09 yeah - we have used the Grafana App mostly, but I keep meaning to add it to Horizon 13:51:32 Right, I remember. 13:51:36 Witold Bedyk proposed openstack/monasca-persister master: Set legacy_kafka_client_enabled = False on default https://review.opendev.org/740966 13:52:02 Thanks for the hints Doug 13:52:27 All right, if there is no other topic let's close the meeting 13:52:29 hi from your friendly Zuul v3 community goal volunteer - can I get a minute before you close? 13:52:38 Sure 13:52:43 Hi Luigi 13:53:05 chaconpiza: np - happy to help out any time 13:53:09 very briefly: monasca in a very good shape (good job!) as almost all the jobs are now Zuul v3 native 13:53:41 I only found one that needs to be ported: legacy-tempest-dsvm-monasca-transform-python35-functional, which is used by monasca-transform, and defined inside openstack-zuul-jobs 13:53:49 can you please take care of that one as well? 13:54:30 Monasca-transform is (or is going to be) deprecated. 13:54:59 oh, ok - that's fine too of course 13:54:59 yes, I think I'll speak internally, but I guess it'll end up in deleting this job 13:55:55 whatever works for you, just please make sure it's done before the end of the cycle 13:55:59 so that we can deprecated devstack-gate 13:56:02 thanks! 13:56:12 thanks tosky for coordinating this! 13:56:49 +1 13:56:51 Thanks Luigi #action Check monasca-transform job legacy-tempest-dsvm-monasca-transform-python35-functional 13:59:04 Ok, thanks for coming today to the meeting. See you next week. 13:59:15 thanks, see you next week 13:59:35 #endmeeting