Tuesday, 2020-04-28

*** k_mouza has joined #openstack-monasca03:30
*** k_mouza has quit IRC03:34
*** vishalmanchanda has joined #openstack-monasca04:57
*** nikparasyr has joined #openstack-monasca07:28
*** witek_ has joined #openstack-monasca07:37
*** witek_ has quit IRC08:45
-openstackstatus- NOTICE: Zuul is currently failing testing, please refrain from recheck and submitting of new changes until this is solved.09:04
*** ChanServ changes topic to "Zuul is currently failing testing, please refrain from recheck and submitting of new changes until this is solved."09:04
*** k_mouza has joined #openstack-monasca09:11
-openstackstatus- NOTICE: Zuul is currently failing all testing, please refrain from approving, rechecking or submitting of new changes until this is solved.09:14
*** ChanServ changes topic to "Zuul is currently failing all testing, please refrain from approving, rechecking or submitting of new changes until this is solved."09:14
*** witek has joined #openstack-monasca10:28
*** brtknr has quit IRC11:07
*** brtknr has joined #openstack-monasca11:15
*** brtknr has quit IRC11:23
*** brtknr has joined #openstack-monasca11:28
*** adriancz has joined #openstack-monasca12:24
*** ChanServ changes topic to "OpenStack Monitoring as a Service | https://wiki.openstack.org/wiki/Monasca"12:27
-openstackstatus- NOTICE: Zuul has been restarted, all events are lost, recheck or re-approve any changes submitted since 9:50 UTC.12:27
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:55
witek#startmeeting monasca13:00
openstackMeeting started Tue Apr 28 13:00:31 2020 UTC and is due to finish in 60 minutes.  The chair is witek. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: monasca)"13:00
openstackThe meeting name has been set to 'monasca'13:00
witekhello everyone13:00
bandorfHello13:00
adrianczHello13:01
witekhi13:01
chaconpizaHi13:01
witekthe agenda for today in the usual place:13:01
witekhttps://etherpad.opendev.org/p/monasca-team-meeting-agenda13:01
witekseems to be light today13:01
witeklet's start13:02
witek#topic vPTG planning13:02
*** openstack changes topic to "vPTG planning (Meeting topic: monasca)"13:02
witekas agreed last week, I've created the etherpad for the planning meeting13:02
witekhttps://etherpad.opendev.org/p/monasca-ptg-victoria13:02
witekempty right now, but we should start collecting topics13:03
witekI've also reserved the time slot in the official schedule spreadsheet13:03
witekhttps://ethercalc.openstack.org/126u8ek25noy13:04
chaconpizaWe have planned an internal brain-storming at Fujitsu before of the PTG13:04
witekvery good, and it definitely makes sense to discuss topics before PTG as well13:05
witekit's easier then to get common understanding and consensus13:05
chaconpizaright13:05
witekit might be also worth to check other etherpads to see if there are potentially interesting topics where we could participate13:07
witekon another topic, some other projects reserve additional time slots aside of main discussions for users/ops from other timezones13:09
witekI was thinking if that would make sense to reserve a one-hour time slot in the APAC friendly time13:10
witeka Monasca office hour13:10
bandorfI think you can judge best if you think that there will be interest from APAC?13:10
bandorfIf yes, I think it definitely makes sense13:11
witekthere hasn't been during last PTG in China, but we're not investing much13:12
KeithMnemonicare the ussuri branches open for use? i tried to backport my patch from master to ussuri,train,... and it fails on ussuri13:13
KeithMnemonicwith it not finding upper constraints13:13
KeithMnemonicalso are the queens /pike branches still eligible for merging bug fixes?13:14
witekKeithMnemonic: please hold on, I'll take it as the next topic13:14
KeithMnemonicthanks!13:14
witekback to the early office hour at the PTG, I think it's worth to try, but I honestly don't expect much interest13:15
chaconpizaI could be helpful for our colleagues in Fujitsu Japan, Haruki and Koji13:16
witekfor sure, if they're interested13:16
witekthe time slot could be 7-8 UTC, e.g. on Tue13:17
chaconpiza+113:18
witeknice, I'm blocking the slot then13:18
witek#topic stable branches13:19
*** openstack changes topic to "stable branches (Meeting topic: monasca)"13:19
chaconpizaKeithMnemonic it seems here is the issue https://review.opendev.org/#/c/722969/13:19
witekI think it's because stable branch hasn't been cut in requirements repo yet13:20
KeithMnemonicthanks, so i will wait for that to clear before a recheck. do i need to wait for that to get my cherry pick to train. it is fine either way13:21
witek"After all of the cycle-with-rc projects have branched we will branch13:21
witekdevstack, grenade, and the requirements repos."13:21
KeithMnemonicor can we get train merged and come back to the ussuri cherry pick later13:21
witekif needed, I'd rather prefer to disable the job again, but they should cut requirements really soon, so probably not worth13:23
KeithMnemonicok and my next topic when you can get to it. "are you still merging to queens/pike?13:25
witekyes, they're still active, I think there are some hacking fixes which should be cherry-picked as well13:26
KeithMnemonicok thanks, so i have some patches ready for review when people have time to look at them, thanks13:27
witekowner:keith.berger@suse.com status:open project:openstack/monasca-agent13:28
witekoops13:28
witekhttps://review.opendev.org/#/q/owner:keith.berger%2540suse.com+status:open+project:openstack/monasca-agent13:28
chaconpizaThe branches queens and pike have already the tag queens-em pike-em13:29
chaconpizaKeithMnemonic do you create your tarballs, images, etc based on a commit hash?13:30
witekhttps://docs.openstack.org/project-team-guide/stable-branches.html#extended-maintenance13:31
witekmeaning, no releases after em13:32
witekbut members are encouraged to engage in maintaining branches13:32
witeklet's move on13:33
witek#topic Ussuri release13:33
*** openstack changes topic to "Ussuri release (Meeting topic: monasca)"13:33
witekwe've created release candidates for all remaining components last week13:34
witekwe also manged to merge some last minute changes13:34
witeklike Kibana plugin installation in DevStack13:34
witekor dropping yaml config support in monasca-notification13:35
witeknext week is the deadline for the final RC13:35
witekwe already know we'll need new release for persister13:36
witekbecause of simplejson13:36
witekthat was my fault, I haven't noticed that the release was done on the older commit13:36
witekthe official release date is May 1313:37
witekany questions or comments?13:37
witek#topic alarm definition update13:38
*** openstack changes topic to "alarm definition update (Meeting topic: monasca)"13:38
witekbandorf: your stage please13:38
bandorfOK, thanks13:39
bandorf3.1: I accidentally found documentation that describes that update of function, time, times is allowed.13:39
bandorfSee link in 3.113:39
bandorf3.2: Testing of periods with AD update has been completed for non-deterministic alarms (including system test): Result is OK13:40
bandorf3.3 Update of time period: should work, according to documentation. Didn't work with functional testing. Therefor, we will execute as well system tests - but not yet done.13:41
bandorf3.4 Update of function: Tests started, but no real results yet13:41
bandorf3.5: Some initial tests with AD update for deterministic alarms (number of periods) were confusing, but we need to test more, no judgement possible yet13:42
bandorfThat's it :-)13:42
witekwhat's the difference between functional and system tests?13:43
bandorfFunctional tests, as I use it here: single tests, running separately, every results evaluated.13:43
bandorfSystem test: Many measurements are sent, multiple alarms may be triggered. Judgement based on min/max/90% values13:44
witekad 3.3 do you expect the result to be possibly different for system test?13:44
bandorfI don't expect that, but I'd like to ensure that we can reproduce the test results. Just to be sure13:45
witekI see, misunderstood it at first13:45
bandorfIt's better if different test approaches provide the same results.13:45
witekthanks for the update!13:45
witekseems, the testing is almost completed13:46
bandorfWell, let's see how results look for deterministic alarms.13:47
witekgood luck then :)13:47
witek#topic AOB13:47
*** openstack changes topic to "AOB (Meeting topic: monasca)"13:47
bandorfThanks! :-)13:47
witekMartin has been officially assigned the PTL role!13:48
witekhttps://governance.openstack.org/tc/reference/projects/monasca.html13:48
witekI think I've missed the mailing list announcement for that13:49
witekanyway, it's time to officially step down for me13:49
witekthanks for all the support13:49
chaconpizaI appreciate the help of witek to ramp-up as PTL13:50
chaconpizaand the support of all of you13:50
witekI'm glad I can pass it over in the good hands13:50
bandorfAnd many thanks, Witek, for your excellent work as PTL!13:50
witekthanks, it was a great journey13:51
chaconpizayes, thanks13:51
adrianczThank Witek fot you hard work !!! : )))13:51
adrianczand congratulates for Martin13:51
witekanyway, I'm not going away, so you'll still find me here :)13:52
witekand all success Martin!13:52
chaconpizaThanks :)13:52
bandorfGood! All the best, Martin!13:52
adrianczgood to hear that Witek :)13:52
witekalright, do you have anything else for today?13:53
chaconpizano from my side13:54
witekthanks for joining13:54
witekand see you next week13:54
witekbye bye13:54
bandorfBye, everybody!13:54
witek#endmeeting13:54
*** openstack changes topic to "OpenStack Monitoring as a Service | https://wiki.openstack.org/wiki/Monasca"13:54
openstackMeeting ended Tue Apr 28 13:54:51 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2020/monasca.2020-04-28-13.00.html13:54
chaconpizaThanks, see you13:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2020/monasca.2020-04-28-13.00.txt13:54
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2020/monasca.2020-04-28-13.00.log.html13:54
KeithMnemonicchaconpizza, we are not doing our own tars, but rather we patch rpm-packaging. the patch does not need to merge14:15
KeithMnemonicbut if the policy was to still put them in for those who might do their own tar, i will keep asking for reviews14:15
openstackgerritOpenStack Release Bot proposed openstack/monasca-statsd master: Add Python3 victoria unit tests  https://review.opendev.org/72391914:36
KeithMnemonicwitek: can you also do this to pike ? https://review.opendev.org/#/c/724068/15:32
witekyep15:32
KeithMnemonicthanks!15:33
*** nikparasyr has quit IRC15:39
openstackgerritMerged openstack/monasca-statsd master: Add Python3 victoria unit tests  https://review.opendev.org/72391915:52
*** witek has quit IRC16:10
*** vishalmanchanda has quit IRC16:45
*** k_mouza has quit IRC16:59
*** k_mouza has joined #openstack-monasca17:00
*** k_mouza has quit IRC17:28
*** k_mouza has joined #openstack-monasca17:28
*** k_mouza has quit IRC17:29
openstackgerritAdrian Czarnecki proposed openstack/monasca-agent master: Improve error handling in method that creat monasc client  https://review.opendev.org/72415520:50
openstackgerritAdrian Czarnecki proposed openstack/monasca-agent master: Improve error handling in method that creat monasc client  https://review.opendev.org/72415520:51
*** joadavis has joined #openstack-monasca21:12
*** mensis has joined #openstack-monasca21:47
*** mensis has quit IRC21:48

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!