13:00:08 #startmeeting monasca 13:00:09 Meeting started Tue Nov 10 13:00:08 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:10 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:00:13 The meeting name has been set to 'monasca' 13:00:25 Hi 13:00:39 The agenda as usual https://etherpad.opendev.org/p/monasca-team-meeting-agenda 13:00:59 Hi 13:01:13 Hello Witek, welcome back. 13:01:22 Hi, all 13:01:28 Hello Matthias 13:01:56 Before to start with todays topics, we have a couple from last week 13:02:07 #topic Set stable branches in DevStack plugin 13:02:33 In the PTL we spoke about this change for train https://review.opendev.org/#/c/718622 13:02:52 and whether we need similar changes for Ussuri and Victoria 13:03:33 Ussuri and Victoria changes are ready and on green 13:03:41 Victoria https://review.opendev.org/#/c/760981 13:03:49 Ussuri https://review.opendev.org/#/c/761020 13:04:02 I think we can merge them 13:04:52 please take a look on them. 13:05:26 #topic Remove Java part from monasca-api and monasca-persister (and possible monasca-common) 13:05:38 will do, I see that e.g. kibana plugin does not have stable branch 13:06:12 the same for grafana datasource 13:06:33 Good point, in Monasca-Kibana-Plugin last stable is Train 13:07:13 #action I will check why we don't have the branches. 13:08:44 these repositories follow different release models 13:09:01 and we haven't created stable branches for them 13:09:53 https://opendev.org/openstack/releases/src/branch/master/deliverables/_independent 13:11:02 At least for monasca-kibana-plugin we needed for the changes of Arseni upgrading to ELK-7 13:12:19 we can still create a releases and branches but they are not bound to OpenStack releases 13:12:20 When I stack using stable/ussuri, I didn't tried to open neither Grafana nor Kibana 13:12:30 ok 13:13:46 alright, the next one is whether this is a good release to remove java part from api, persister and possible monasca-common 13:14:23 deploying api and persister with java is deprecated for long time. 13:14:24 in general +1, apart from monasca-common 13:14:49 probably in monasca-common we have parts used in Thresh 13:15:05 right, so at least parts of it would have to remain 13:15:33 Then let's start with api and persister, of course only for master branches. 13:15:44 +1 13:16:03 #topic Remove Six library from Monasca modules 13:17:03 Recently we received a big effort to remove six from monasca-agent from Likui. 13:17:26 https://review.opendev.org/#/c/758006/ 13:17:55 This change can help as well as a model for the rest of Monasca modules 13:18:02 in order to remove six 13:19:09 good stuff 13:19:22 the problem with monasca-agent is that it's poorly tested :( 13:20:23 We are currently enhancing our system tests to cover monasca-agent. Not part of monasca, but at least some tests will be executed 13:21:21 ideal would be to land them into Tempest-test 13:22:39 Yes, but the test approach is different 13:23:03 We have other changes with same topic: six_removed but still incompleted. If I would like to completed them, i.e. take the initial partial work of someone, then it is ok to send a new patchset with: Co-authored-by: ??? 13:24:18 the Author field remains unchanged, if you submit a new PS, you'll be added as Committer 13:25:11 So, no extra information like Co-authored-by is needed? 13:26:38 that's my take on it, Co-authored-by is meant for cases when you're using someone's work and submit the initial commit 13:26:58 but it doesn't hurt to put it anyway 13:27:12 I see, thanks for the explanation. 13:27:28 #topic Imported Translations from Zanata 13:27:57 recently we have received this change https://review.opendev.org/#/c/761291/ 13:28:38 In this case I am not sure whether it is correct. I see they are removing some messages from several languages. 13:29:25 hm, good point 13:29:31 I added Ian Y. Choi (I think he's the PTL of i18n project) as a reviewer 13:29:59 and today I wrote a note in the #openstack-i18n channel 13:30:34 So, let's wait for an answer.. 13:30:48 for now let's keep it open 13:31:17 #topic Add chaconpiza into monasca organization in Docker Hub 13:31:24 ;-) 13:32:15 I am not sure Witek you have the access, if not I will contact Tim Buckley 13:32:57 I'll look up my DB, but I cannot find any credentials at the first glance 13:33:17 could you check with Dobek please? 13:33:24 Right 13:34:05 next topic is related 13:34:15 #topic Fix encrypted Docker Hub user/password of monasca-tempest 13:34:26 https://zuul.opendev.org/t/openstack/builds?job_name=publish-monasca-tempest-plugin-docker-image 13:35:19 The user/password in zuul files are encrypted, unfortunatelly for this repo there is a mistake, so Zuul can't login into Docker Hub 13:35:41 I will contact Dobek about it too 13:35:53 Each repository as a Public and Private key 13:36:37 This is way it would be pointless try to use the encrypted user/password from other monasca zuul configuration file 13:36:53 makes sense 13:38:09 right 13:38:48 #topic AOB 13:39:27 I am fixing/finishing the docker configuration template for Monasca-Notification https://review.opendev.org/#/c/760081/ 13:40:39 And deploying the pipeline using the master images, victoria images and ussuri images successfully (tempest test ok) 13:41:17 soon I will add stable/ussuri and stable/victoria branches into github.com/monasca/monasca-docker 13:42:11 the review looks good at the first glance, is it ready to merge? 13:42:26 create a branch called "legacy" to keep the current code of monasca-docker (which basically points to queens-rocky) 13:43:01 ^^ I wand to check one more time the notification plugins 13:43:10 (at least webhook and email) 13:44:02 for mail I used Mailhog as a dev. mail server https://hub.docker.com/r/mailhog/mailhog/ 13:44:58 perhaps instead of "legacy" use more explicit name like "stable/queens" 13:45:17 mmm... but it is not really uniform 13:46:17 timestamp with date of last update? 13:46:39 yes 13:47:14 so it could be "legacy-2018_10" 13:47:48 it sounds good to me 13:49:13 in case of tempest, we still pointing to the tempest-test when it was part of monasca-api repo 13:49:48 So, it will be ok to make order there ;-) 13:51:37 allright, I think these were all topics for today. Then let's close the meeting. 13:51:53 thanks 13:51:58 see you next week 13:52:15 Thank you Witek and Matthias, see you next week. 13:52:26 Bye, everybody 13:52:44 #endmeeting