15:01:18 #startmeeting monasca 15:01:19 Meeting started Wed Nov 20 15:01:18 2019 UTC and is due to finish in 60 minutes. The chair is witek_. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:20 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:23 The meeting name has been set to 'monasca' 15:01:26 hello everyone 15:01:33 hi 15:01:44 hi chaconpiza 15:02:26 is it just two of us today? 15:02:46 the agenda: 15:02:50 https://etherpad.openstack.org/p/monasca-team-meeting-agenda 15:03:10 #topic new meeting time 15:03:13 today only me from fj 15:03:27 the results of the poll are here 15:03:29 https://doodle.com/poll/ey6brvmbsubkxpp9 15:03:41 hey there 15:03:46 hi dougsz 15:03:50 hi 15:04:48 according to the poll the best new time for the meeting would be on Tuesdays, 1pm UTC 15:05:04 is that OK for you? 15:05:39 Works for me 15:05:56 Works for me too 15:06:05 let's move it then 15:06:13 thanks for voting 15:06:57 I'll update the overview page and send an email 15:07:19 #topic dropping Python 2 support 15:07:52 TC has decided on dropping Python 2 support in Ussuri cycle 15:08:09 there are already changes removing unit tests 15:08:17 https://review.opendev.org/#/q/(projects:openstack/monasca+OR+project:openstack/python-monascaclient)+is:open+topic:drop-py27-support 15:08:57 it has also been nominated to the Community Wide Goal 15:09:01 https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html 15:09:53 taking a look at the changes I noticed that our tox configurations are not always correct 15:10:19 and so for examples py37 tests are not run in some cases 15:10:49 we should take this occasion and review our tox.ini files 15:11:04 As well we continue using PY2 to build Grafana in devstack: 15:11:05 https://github.com/openstack/monasca-api/blob/master/devstack/plugin.sh#L1266 15:12:01 good point, has anyone checked recently if it can be done with Python 3? 15:12:26 no 15:12:46 I wonder if it is worth the effort 15:13:16 we had two init scripts that were only PY2 compatible but recently adriancz fixed them. 15:13:36 that's still the old forked Grafana, right? 15:14:19 https://github.com/openstack/monasca-api/blob/dfd942352611cb4aba53f6bb3d9628ac70b085c7/devstack/settings#L159 15:14:54 `GRAFANA_REPO=${GRAFANA_REPO:-"https://github.com/monasca/grafana.git"}` yeah 15:16:43 ideas how to move forward? 15:17:20 It seems like putting effort into app credentials + getting rid of the fork would be a good objective 15:17:46 +1 15:18:17 +1 15:18:18 what for this fork was created? 15:18:28 Keystone authentication 15:18:29 to include keystone integration 15:18:34 ah ha 15:19:17 heh, sorry. I'm playing catch up as my laptop froze 10 minutes before the meeting and I switched laptops 15:19:43 I think having python 2 here now will not break gate jobs 15:19:59 so we can work on app credentials in this cycle 15:20:04 and upgrade when ready 15:20:07 right, I don't think any gates test grafana integration 15:20:13 sounds good 15:21:33 Cassandra doesn't have Python 3 jobs 15:22:07 meaning it won't be tested anymore after migration on master 15:22:18 only on stable branches 15:22:44 yuck. that is worth fixing if we can 15:23:33 anything else we have to consider? 15:24:24 #topic logs gate job 15:25:26 http://zuul.openstack.org/builds?job_name=monascalog-python3-tempesthttp://zuul.openstack.org/builds?job_name=monascalog-python3-tempest 15:25:37 the failure rate is scary 15:26:08 this job blocks many reviews right now 15:26:15 yeah, I had a quick look but didn't get to the bottom of it yet 15:27:09 I'll try to find out if we can run it on a bigger vm 15:28:20 do we want to create an etherpad to collect debug information? 15:29:12 Good idea 15:29:30 I should have some time early next week to help debug 15:29:48 https://etherpad.openstack.org/p/monascalog-python3-tempest 15:30:28 let's put there all we know 15:31:34 #topic reviews 15:31:53 we've managed to merge few changes this week 15:32:00 I've updated the board 15:32:14 https://storyboard.openstack.org/#!/board/190 15:32:41 still few changes needing reviews 15:32:50 https://review.opendev.org/#/q/topic:story_2006059 15:33:28 this is for buffering messages in API 15:33:28 Thanks for those patches witek 15:34:05 As you say, all blocked on tempest failures 15:34:22 I've added possibility to pass options to the new Kafka producer 15:34:54 it can control number of messages in buffer and many other values 15:35:17 https://review.opendev.org/674204 15:35:35 this one fixes gate jobs for events 15:35:51 https://storyboard.openstack.org/#!/story/2006783 15:35:57 https://storyboard.openstack.org/#!/story/2006783 15:36:06 https://storyboard.openstack.org/#!/story/2006837 15:36:17 these are for periodic notifications 15:36:30 I haven't had time to look at these yet 15:37:12 and then IPv6 change from gmann 15:37:17 https://review.opendev.org/673274 15:37:55 I guess he's busy with Python 2 dropping now, we should help on this one 15:39:08 https://review.opendev.org/#/c/677943/ this too 15:40:15 is also for IPV6 15:40:17 did yeey (Guang) contact you about backporting his https://review.opendev.org/#/c/690477/ back as far as possible? 15:40:32 than you sum12 15:40:50 joadavis: no 15:40:52 he would like to take it to pike, but I talked to him yesterday about how that is difficult with EM releases 15:41:47 I think it will be easier to create a patch in packaging 15:42:13 I think that is where my chat with yeey ended up 15:42:28 but it doesnt hurt to ask. :) 15:42:36 no, it doesn't :) 15:43:30 I saw a new patch on ELK upgrade change 15:43:49 https://review.opendev.org/#/c/675061/ 15:44:04 chaconpiza: is it functional now? 15:44:20 not sure, I will ask arseni tomorrow 15:45:02 thanks, he can leave a comment on review if it's ready 15:45:20 pinging in channel also works 15:46:14 any other reviews? 15:46:17 https://review.opendev.org/#/c/679225 I myself forgot about this one until someone told me that it is needed I will remove the WIP but please keep on eye on it 15:47:07 thanks, adding to the list 15:47:52 thanks 15:48:07 #topic AOB 15:48:21 what was the motivation to change the index-version in influxdb? 15:48:21 Now we have in devstack Influx 1.7.6 index-version = "tsi1" 15:48:21 In the past was used index-version = "inmem" 15:49:00 chaconpiza: tsi1 is recommended now 15:49:10 does it fit better with metric pipeline? 15:49:36 Our influxdb 1.3.4 is consuming too much memory almost 44% of 32GB RAM with no reason, logs look ok. Just normal stuff and every day a shard is being deleted as expected. 15:49:39 it allows for storing more metrics 15:49:43 it reduced memory requirements - it used a disk based index which is cached into RAM 15:50:20 I found as well in influxdb release notes some fixes about memory leaks in 1.4.x versions 15:50:34 I would skip 1.4 entirely and go straight to 1.7 15:50:45 There is a migration procedure in the docs 15:51:11 We've had no issues with the migration 15:51:11 are you using 1.7 in prod? 15:51:14 yeah 15:51:18 cool 15:51:46 it's default in Kolla Ansible 15:54:08 from other topics, there is an interesting discussion on openstack-discuss 15:54:13 thanks, we will test the migration to tsi1 15:54:15 http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010922.html 15:55:52 if there are no other topics, I'll be wrapping up 15:56:22 ok, thanks witek, thanks all 15:56:29 thanks for good discussions 15:56:31 thanks all 15:56:39 thanks 15:56:40 next week we meet on Tuesday, at 1pm 15:56:44 UTC 15:56:48 yeah 15:57:11 bye, bye 15:57:16 #endmeeting