Tuesday, 2020-04-21

*** k_mouza has joined #openstack-monasca04:17
*** k_mouza has quit IRC04:21
*** vishalmanchanda has joined #openstack-monasca05:09
*** mensis has joined #openstack-monasca07:06
*** witek_ has joined #openstack-monasca08:41
*** k_mouza has joined #openstack-monasca09:02
*** vishalmanchanda has quit IRC09:09
*** k_mouza has quit IRC09:41
openstackgerritWitold Bedyk proposed openstack/monasca-persister master: Migrate from ujson to simplejson  https://review.opendev.org/71998910:36
*** witek_ is now known as witek10:36
witekchaconpiza: I've updated https://review.opendev.org/71998911:29
witekplease review11:29
chaconpizaHi, sure.11:29
chaconpizaI see you are using the std mock.11:30
witekyes, coverage tests were failing otherwise11:30
witekhttps://zuul.opendev.org/t/openstack/build/e857b2a9218446bcb020bca2aec0677811:30
chaconpizaI can't find what have changed that now it fails11:31
chaconpizaThis is a previous one that finished successfully https://zuul.opendev.org/t/openstack/build/21348d014fde4f70976fc12ffd39fc64/log/job-output.txt11:31
chaconpizathe version of the libraries seems to be the same11:32
witeknothing changed in our code, some dependency has changed probably11:32
chaconpizaright11:33
witekbut mock is being removed in other projects as well as part of dropping Python 2 support11:33
chaconpizaI have added this topic to today's meeting11:36
*** k_mouza has joined #openstack-monasca11:42
*** k_mouza has quit IRC11:46
*** dougsz has joined #openstack-monasca12:14
*** k_mouza has joined #openstack-monasca12:16
dougszApologies I missed the meeting earlier, looks like this is the final patch for the ujson work? https://review.opendev.org/#/c/720879/12:36
openstackgerritMerged openstack/python-monascaclient master: Fix mock import statements  https://review.opendev.org/71777912:44
witekdougsz: you haven't, we've got summer time12:53
dougszdoh, yes of course, need to fix my reminder :)12:53
witekCourtesy Monasca meeting reminder in 5 minutes in #openstack-monasca: witek, jayahn,iurygregory,ezpz,igorn,haad,sc,joadavis, akiraY,tobiajo,dougsz,fouadben, amofakhar, haru5ny (haruki),kaiokmo,pandiyan,guilhermesp,chaconpiza,hosanai,Wasaac,brtknr,bandorf12:53
*** bandorf has joined #openstack-monasca12:54
*** bandorf has quit IRC13:01
witek#startmeeting monasca13:01
openstackMeeting started Tue Apr 21 13:01:10 2020 UTC and is due to finish in 60 minutes.  The chair is witek. Information about MeetBot at http://wiki.debian.org/MeetBot.13:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
*** openstack changes topic to " (Meeting topic: monasca)"13:01
openstackThe meeting name has been set to 'monasca'13:01
witekhello everyone13:01
chaconpizaHi13:01
adrianczHI13:01
dougszhi all13:01
*** bandorf has joined #openstack-monasca13:01
witekthe agenda for today:13:01
witekhttps://etherpad.opendev.org/p/monasca-team-meeting-agenda13:01
witekwe've got a number of items to discuss, let's start13:02
witek#topic virtual PTG13:02
*** openstack changes topic to "virtual PTG (Meeting topic: monasca)"13:02
witekit has been decided the PTG will be held virtually this time around13:02
witekin the week 1-5 June13:03
chaconpizaThe original schedule before the covid pandemic was 8-11 June13:04
witekreally, haven't realized that13:04
chaconpizaI have vacations exactly 1-5 June, but of course I can join one day13:05
witekanyway, all the teams have been asked to decide how many sessions they'd like to hold and when13:05
witekthat's unfortunate, indeed13:05
witekalso 1 June is holiday in Germany13:05
openstackgerritMerged openstack/monasca-persister master: Migrate from ujson to simplejson  https://review.opendev.org/71998913:06
witekI've looked up the notes from our previous PTGs13:07
witekin Denver we had 3 slots 3,5 hours each13:07
witekhttps://wiki.openstack.org/wiki/MonascaTrainPTG13:07
witekbut the last session has ended very early from what I recall13:08
witekthen the Ussuri planning meeting was virtual13:10
witekhttps://etherpad.opendev.org/p/monasca-planning-ussuri13:10
witekit was one slot of 4 hours13:10
witekany preferences for this time?13:11
witekthe organizers have suggested to not put more than 4 hours on a single day13:12
chaconpizaTuesday in the morning13:12
dougszI'm pretty flexible. Tuesday in the morning would work.13:13
witekmorning could be difficult for US13:14
chaconpizathat's right13:14
witekdoes Tuesday afternoon work for you?13:15
witeknot many projects have declared their slot yet13:15
witekhttps://ethercalc.openstack.org/126u8ek25noy13:16
witekdo you know what ECG stands for?13:16
chaconpizaEdge Computing Group - OpenStack13:16
witekthanks13:16
chaconpiza(I just google it : ) )13:17
dougsz:) Afternoon is good too13:17
witekthe proposed afternoon slot is 13-17 UTC13:17
chaconpizaOk, what about Tuesday 13:00 UTC to keep the habit13:18
chaconpizayes13:18
adriancz +113:18
witekwow, indeed, that's out time! :)13:18
chaconpiza:)13:18
witeklet's start with that then13:19
bandorfok with me13:19
witekgreat, thanks13:19
witekI'll also create an etherpad to start collecting topics13:19
witekand if we feel like we're running out of time we can decide to extend13:20
witekeven in the following week13:20
witekwe haven't book any convention center ;P13:20
witekwe could also hold a cross-project monitoring session13:21
witekperhaps as part of automation SIG?13:22
witekI could talk with Rico if you like the idea13:22
witek#action witek create etherpad for PTG planning13:23
chaconpiza+113:24
witek#action witek book a slot for Monasca session at PTG13:24
witekif there are no other comments, I guess we can move on13:25
witek?13:25
*** toabctl has quit IRC13:25
witek#topic updating alarm definitions13:26
*** openstack changes topic to "updating alarm definitions (Meeting topic: monasca)"13:26
bandorfOK13:26
*** toabctl has joined #openstack-monasca13:27
bandorfTopic 2.1.1: acceptance criteria: This was a difficult one, but I found some schema that is "good enough" for the specific purpose13:27
bandorf2.1.3 Execute reference tests: Basically, validation of acceptance criteria13:27
bandorfWorked ok without issues (exception, valid for most of the test cases: time it takes to change to "UNDETERMINED". But this is not considered for now)13:28
bandorf2.1.4: Execute tests with alarm definition update, but no existing alarms:13:28
bandorfAgain, everything worked ok - as expected.13:29
bandorf2.1.5 Tests with update alarm definitions, alarms exist:13:29
bandorfchanging time period definitely doesn't work as expected13:29
bandorfchaning number of time period might work, I need to execute further tests13:30
bandorfAs a note: I executed a subset of tests of 2.1.5, stopping/restarting monasca-thresh.13:30
bandorfThen, test results are as expected.13:31
bandorfNo big surprise, but I wanted to be sure.13:31
witekyou're testing your updated API calls, is that correct?13:31
bandorfYes, correct. I fixed monasca-api, nothing else. And then, I executed the tests.13:31
witekthanks, wanted to be sure13:31
bandorf2.2 Current status:13:32
bandorf2.2.1.1 update of FUNCTION: I executed some quick tests some time ago. These worked. But I still have to do "proper testing"13:33
bandorf2.3 Next steps:13:33
bandorf2.3.1 and 2.3.2 are clear.13:33
bandorfI'm curious: Assuming that test results would be time cannot be updated, times can be updated.13:34
bandorfWhat would be your opinion? Allow update for times or not?13:34
witekif it works as expected, I'd allow it13:35
bandorfOK.13:35
chaconpiza+113:35
witekand the rest we could document as the limitation13:35
witekI mean, as the workaround we still could recreate the alarm definition, right?13:35
bandorfWell, we can restrict in the API as well, like other params.13:35
witek+113:36
bandorfRecreation of alarm definition of course always works. That's the work-around we used for our customer13:36
bandorfI will add one more "next step": Elfriede has just extended system test with alarms.13:37
chaconpizayeah!13:37
witeknice work, thanks13:37
bandorfWhen I come to the conclusion that some parameters can be updated, we will test this as well with system test13:37
witekgood to have it tested in a systematic way, should we extend tempest as well?13:38
bandorfYes, of course. But I haven't gone into this topic.13:39
witekfair enough, thanks for the update13:39
bandorfI'll provide an update next week. System test execution for update AD might not be ready then13:39
witeknice13:40
dougszThanks bandorf. +1 for extending tempest / upstream coverage if possible.13:40
bandorfYes, I have it on my list. But this will take some more time, due to other internal priorities13:40
dougszunderstood13:41
witekOK, should we move on?13:41
bandorfI' done :-)13:42
witekthanks bandorf13:42
witek#topic reviews13:42
*** openstack changes topic to "reviews (Meeting topic: monasca)"13:42
witekwe've struggled with CI in the last time13:42
chaconpizaThe ripple effect13:43
witekbut we managed to get ujson->simplejson finally merged13:43
witekit should be possible to merge other changes now13:44
dougszthanks for that effort!13:44
witeklike topic:periodic_notifications13:44
witekhttps://storyboard.openstack.org/#!/story/200683713:45
witekor topic:update-hacking13:45
witekhttps://review.opendev.org/#/q/projects:openstack/monasca+is:open+topic:update-hacking13:45
witekI'm not sure how to proceed for monasca-log-api repository13:46
witekhttps://review.opendev.org/71640813:46
witekwe actually have said, we don't want new code merged there, just bug fixes for old API13:46
dougszI see your point13:48
witekon the other hand Python 2 is deprecated anyway, so we should probably use Python 3 for old API as well13:49
dougszIt's a can of worms13:50
witekhow do you mean that?13:50
dougszSorry, just thinking about Kolla not using Python 3 in older releases13:51
witekyeah, get it13:51
witekhm, I guess we should comment on review and see what AJaeger thinks of it13:51
dougszAgreed, seems likely he will have some wisdom to share13:52
witekanother set of reviews up there is topic:unittest.mock13:53
witekit's replacing third party lib with Python 2 support included13:53
witekwith standard library's  unittest.mock13:53
chaconpizawhere monasca-log-api is in the list13:54
witekhttps://review.opendev.org/#/q/(projects:openstack/monasca+OR+project:openstack/python-monascaclient)+is:open+topic:unittest.mock13:54
witekchaconpiza: https://review.opendev.org/71640813:54
witekand https://review.opendev.org/72094313:55
chaconpizayes, it was a statement ;)13:55
witekoh, I see13:55
chaconpizaAbout the list related to the mock, it is strange that monasca-persister was not there13:56
chaconpizado you know why?13:56
witekindeed, don't know13:56
chaconpizaand exactly that blocked us13:57
witekOK, please spend some time on these reviews, should be easy in most cases13:57
chaconpiza+113:57
witekbefore we end, last topic13:57
witek#topic RC113:58
*** openstack changes topic to "RC1 (Meeting topic: monasca)"13:58
witekthis week is deadline for RC1 release13:58
witekplease ping me if there is something which should be included in Ussuri13:59
*** dougsz has quit IRC13:59
witekafter RC1 the stable branch will be created and only bug fixes are allowed to be cherry-picked13:59
chaconpizaok13:59
witekfor other changes feature freeze exempts have to be created14:00
witekthat's a new process for us but we moved to release-with-rc model in this cycle14:01
witekall from me14:01
witekthanks for joining14:01
witekand see you next week14:01
bandorfWhat does that mean for threshold replacement?14:01
witeknot ready in Ussuri14:01
bandorfok14:01
bandorfthanks everybody, bye14:02
chaconpizathanks, bye!14:02
witekbye bye14:02
witek#endmeeting14:02
*** openstack changes topic to "OpenStack Monitoring as a Service | https://wiki.openstack.org/wiki/Monasca"14:02
openstackMeeting ended Tue Apr 21 14:02:28 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2020/monasca.2020-04-21-13.01.html14:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2020/monasca.2020-04-21-13.01.txt14:02
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2020/monasca.2020-04-21-13.01.log.html14:02
AJaegerwhat was the question on python2 and kolla? Sorry, just coming back online and didn't get the statement14:02
witekwell, we have a kind of special situation with monasca-log-api repo14:03
witekwe've moved the code to monasca-api, but want to keep the old repository for maintanance purposes14:04
witekcherry-picking to stable branches14:04
witeknow, we're wondering how to handle the dropping Python 2 support changes in that maintanance repository (monasca-log-api)14:05
witekfor Kolla context, that would be best when dougsz is online again14:08
witekbut from what I understood the older versions run with Python 2 only14:08
AJaegerwitek, monasca-log-api has stable branches14:11
witekyes14:11
AJaegera backport should work just fine - that's something every project faces. You might need to re-add six py2 but that should be it.14:11
AJaegerwitek: the dropping python 2 change is not really changing code, so should not affect it.14:12
witekyeah, you're probably right, and python2 jobs have been disabled already on master14:15
*** dougsz has joined #openstack-monasca14:16
witekdougsz: do you have some more context on Python 2 and Kolla?14:17
AJaegerall other repos are gone python3, so monasca is not special here for Kolla14:17
dougszI think Train onwards will support Py3, but no plans to backport before that.14:19
dougszSorry, I think my IRC client disconnected14:19
dougsz AJaeger: This is in reference to how far to back port py3 patches14:20
AJaegerdougsz: why do you want to backport py3 patches?14:23
AJaegerperhaps we have a different definition on py3 patches - train is supporting both py2 and py3, ussuri is supporting only py314:23
witekthat's indeed strange situation with monasca-log-api, we actually don't need the master branch anymore, but want to have functional CI14:27
witekdougsz: different question, do you have any problems in Kolla with building Docker images with newest confluent-kafka?14:29
witekhere the context: https://github.com/confluentinc/confluent-kafka-python/issues/83014:29
*** KeithMnemonic has joined #openstack-monasca14:32
dougszhmm, haven't hit it yet, but will keep an eye out14:32
KeithMnemonicreviews please when you have time https://review.opendev.org/#/c/719982/3 Thank you!14:32
AJaegerwitek: do it like networking-ovn and retire master14:34
AJaegerhttp://lists.openstack.org/pipermail/openstack-discuss/2020-April/014308.html14:34
witekAJaeger: thanks for the reference!14:35
*** bandorf has left #openstack-monasca14:52
*** viks____ has quit IRC15:07
joadavisRegarding removing agent configuration, this may be helpful - https://review.opendev.org/#/c/623611/15:25
joadavisI apologize for not adding it to the agenda for today, it needs review and merge15:26
witekthanks, adding to my list15:27
joadavisthank you15:33
openstackgerritWitold Bedyk proposed openstack/monasca-agent master: Temporarily disable building Docker images  https://review.opendev.org/72167115:35
*** adriancz has quit IRC16:26
*** adriancz has joined #openstack-monasca16:26
*** srwilkers has quit IRC16:39
*** piotrowskim has quit IRC16:40
*** srwilkers has joined #openstack-monasca16:42
*** piotrowskim has joined #openstack-monasca16:44
*** srwilkers has quit IRC16:48
*** srwilkers has joined #openstack-monasca16:51
*** witek has quit IRC17:03
*** dougsz has quit IRC17:03
*** k_mouza has quit IRC17:22
openstackgerritAndreas Jaeger proposed openstack/monasca-persister master: Update hacking for Python3  https://review.opendev.org/71652117:27
*** gmann is now known as gmann_lunch18:31
*** gmann_lunch is now known as gmann18:51
*** k_mouza has joined #openstack-monasca19:23
*** k_mouza has quit IRC19:28
*** dougsz has joined #openstack-monasca19:53
*** dougsz has quit IRC20:35
*** mensis has quit IRC21:12
*** k_mouza has joined #openstack-monasca21:25
*** k_mouza has quit IRC21:29

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!