13:00:31 <witek> #startmeeting monasca
13:00:32 <openstack> Meeting 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:33 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:00:35 <openstack> The meeting name has been set to 'monasca'
13:00:52 <witek> hello everyone
13:00:59 <bandorf> Hello
13:01:06 <adriancz> Hello
13:01:10 <witek> hi
13:01:13 <chaconpiza> Hi
13:01:37 <witek> the agenda for today in the usual place:
13:01:40 <witek> https://etherpad.opendev.org/p/monasca-team-meeting-agenda
13:01:52 <witek> seems to be light today
13:02:01 <witek> let's start
13:02:10 <witek> #topic vPTG planning
13:02:35 <witek> as agreed last week, I've created the etherpad for the planning meeting
13:02:41 <witek> https://etherpad.opendev.org/p/monasca-ptg-victoria
13:03:00 <witek> empty right now, but we should start collecting topics
13:03:53 <witek> I've also reserved the time slot in the official schedule spreadsheet
13:04:08 <witek> https://ethercalc.openstack.org/126u8ek25noy
13:04:25 <chaconpiza> We have planned an internal brain-storming at Fujitsu before of the PTG
13:05:04 <witek> very good, and it definitely makes sense to discuss topics before PTG as well
13:05:40 <witek> it's easier then to get common understanding and consensus
13:05:46 <chaconpiza> right
13:07:16 <witek> it might be also worth to check other etherpads to see if there are potentially interesting topics where we could participate
13:09:23 <witek> on another topic, some other projects reserve additional time slots aside of main discussions for users/ops from other timezones
13:10:13 <witek> I was thinking if that would make sense to reserve a one-hour time slot in the APAC friendly time
13:10:22 <witek> a Monasca office hour
13:10:58 <bandorf> I think you can judge best if you think that there will be interest from APAC?
13:11:08 <bandorf> If yes, I think it definitely makes sense
13:12:02 <witek> there hasn't been during last PTG in China, but we're not investing much
13:13:21 <KeithMnemonic> are the ussuri branches open for use? i tried to backport my patch from master to ussuri,train,... and it fails on ussuri
13:13:43 <KeithMnemonic> with it not finding upper constraints
13:14:00 <KeithMnemonic> also are the queens /pike branches still eligible for merging bug fixes?
13:14:03 <witek> KeithMnemonic: please hold on, I'll take it as the next topic
13:14:09 <KeithMnemonic> thanks!
13:15:27 <witek> back to the early office hour at the PTG, I think it's worth to try, but I honestly don't expect much interest
13:16:32 <chaconpiza> I could be helpful for our colleagues in Fujitsu Japan, Haruki and Koji
13:16:51 <witek> for sure, if they're interested
13:17:32 <witek> the time slot could be 7-8 UTC, e.g. on Tue
13:18:10 <chaconpiza> +1
13:18:39 <witek> nice, I'm blocking the slot then
13:19:05 <witek> #topic stable branches
13:19:48 <chaconpiza> KeithMnemonic it seems here is the issue https://review.opendev.org/#/c/722969/
13:20:33 <witek> I think it's because stable branch hasn't been cut in requirements repo yet
13:21:13 <KeithMnemonic> thanks, 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 way
13:21:14 <witek> "After all of the cycle-with-rc projects have branched we will branch
13:21:14 <witek> devstack, grenade, and the requirements repos."
13:21:58 <KeithMnemonic> or can we get train merged and come back to the ussuri cherry pick later
13:23:37 <witek> if needed, I'd rather prefer to disable the job again, but they should cut requirements really soon, so probably not worth
13:25:33 <KeithMnemonic> ok and my next topic when you can get to it. "are you still merging to queens/pike?
13:26:27 <witek> yes, they're still active, I think there are some hacking fixes which should be cherry-picked as well
13:27:16 <KeithMnemonic> ok thanks, so i have some patches ready for review when people have time to look at them, thanks
13:28:27 <witek> owner:keith.berger@suse.com status:open project:openstack/monasca-agent
13:28:31 <witek> oops
13:28:34 <witek> https://review.opendev.org/#/q/owner:keith.berger%2540suse.com+status:open+project:openstack/monasca-agent
13:29:28 <chaconpiza> The branches queens and pike have already the tag queens-em pike-em
13:30:20 <chaconpiza> KeithMnemonic do you create your tarballs, images, etc based on a commit hash?
13:31:24 <witek> https://docs.openstack.org/project-team-guide/stable-branches.html#extended-maintenance
13:32:15 <witek> meaning, no releases after em
13:32:36 <witek> but members are encouraged to engage in maintaining branches
13:33:29 <witek> let's move on
13:33:41 <witek> #topic Ussuri release
13:34:18 <witek> we've created release candidates for all remaining components last week
13:34:32 <witek> we also manged to merge some last minute changes
13:34:52 <witek> like Kibana plugin installation in DevStack
13:35:14 <witek> or dropping yaml config support in monasca-notification
13:35:50 <witek> next week is the deadline for the final RC
13:36:05 <witek> we already know we'll need new release for persister
13:36:25 <witek> because of simplejson
13:36:56 <witek> that was my fault, I haven't noticed that the release was done on the older commit
13:37:18 <witek> the official release date is May 13
13:37:47 <witek> any questions or comments?
13:38:35 <witek> #topic alarm definition update
13:38:52 <witek> bandorf: your stage please
13:39:03 <bandorf> OK, thanks
13:39:40 <bandorf> 3.1: I accidentally found documentation that describes that update of function, time, times is allowed.
13:39:45 <bandorf> See link in 3.1
13:40:33 <bandorf> 3.2: Testing of periods with AD update has been completed for non-deterministic alarms (including system test): Result is OK
13:41:20 <bandorf> 3.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:48 <bandorf> 3.4 Update of function: Tests started, but no real results yet
13:42:39 <bandorf> 3.5: Some initial tests with AD update for deterministic alarms (number of periods) were confusing, but we need to test more, no judgement possible yet
13:42:48 <bandorf> That's it :-)
13:43:06 <witek> what's the difference between functional and system tests?
13:43:38 <bandorf> Functional tests, as I use it here: single tests, running separately, every results evaluated.
13:44:20 <bandorf> System test: Many measurements are sent, multiple alarms may be triggered. Judgement based on min/max/90% values
13:44:29 <witek> ad 3.3 do you expect the result to be possibly different for system test?
13:45:00 <bandorf> I don't expect that, but I'd like to ensure that we can reproduce the test results. Just to be sure
13:45:16 <witek> I see, misunderstood it at first
13:45:24 <bandorf> It's better if different test approaches provide the same results.
13:45:58 <witek> thanks for the update!
13:46:42 <witek> seems, the testing is almost completed
13:47:12 <bandorf> Well, let's see how results look for deterministic alarms.
13:47:45 <witek> good luck then :)
13:47:52 <witek> #topic AOB
13:47:57 <bandorf> Thanks! :-)
13:48:48 <witek> Martin has been officially assigned the PTL role!
13:48:52 <witek> https://governance.openstack.org/tc/reference/projects/monasca.html
13:49:08 <witek> I think I've missed the mailing list announcement for that
13:49:43 <witek> anyway, it's time to officially step down for me
13:49:52 <witek> thanks for all the support
13:50:07 <chaconpiza> I appreciate the help of witek to ramp-up as PTL
13:50:25 <chaconpiza> and the support of all of you
13:50:27 <witek> I'm glad I can pass it over in the good hands
13:50:36 <bandorf> And many thanks, Witek, for your excellent work as PTL!
13:51:03 <witek> thanks, it was a great journey
13:51:05 <chaconpiza> yes, thanks
13:51:07 <adriancz> Thank Witek fot you hard work !!! : )))
13:51:42 <adriancz> and congratulates for Martin
13:52:08 <witek> anyway, I'm not going away, so you'll still find me here :)
13:52:20 <witek> and all success Martin!
13:52:43 <chaconpiza> Thanks :)
13:52:47 <bandorf> Good! All the best, Martin!
13:52:56 <adriancz> good to hear that Witek :)
13:53:51 <witek> alright, do you have anything else for today?
13:54:20 <chaconpiza> no from my side
13:54:31 <witek> thanks for joining
13:54:36 <witek> and see you next week
13:54:38 <witek> bye bye
13:54:45 <bandorf> Bye, everybody!
13:54:51 <witek> #endmeeting