Earlier  
Posted Nick Remark
#openstack-sdks - 2022-08-18
16:14:11 diablo_rojo maybe make that our 'check in ' meeting for the week
16:14:24 diablo_rojo or what have you- kinda push them to come
16:14:24 gtema yupp, why not
16:14:53 gtema the only thing - they should not have courses at this time, otherwise they have excuse
16:15:15 diablo_rojo Once I have the final list of teams, I will get them loaded into the PTGbot and the etherpad will get generated and then we can build our agenda- we can start early but I dont think we are in a rush and need to start it now?
16:15:21 diablo_rojo gtema: +2
16:15:38 gtema yeah, no hurry now
16:15:43 diablo_rojo Anything else on the PTG topic?
16:15:51 gtema we anyway do not even know how many of the students will we have
16:15:54 gtema nothing from my side
16:16:07 diablo_rojo gtema: also true
16:16:11 diablo_rojo Okay next topic then
16:16:25 diablo_rojo #topic Last Interface Change before R1.0
16:16:31 diablo_rojo #link https://review.opendev.org/c/openstack/openstacksdk/+/853052
16:16:37 gtema yeah, I feel burden with waiting of the R1.0 and decided to pack the last change into the queue
16:16:38 diablo_rojo I think this topic was yours gtema ?
16:16:44 gtema yeah, mine
16:16:54 gtema this change is unifying listing filtering
16:16:56 diablo_rojo Ah okay.
16:17:07 gtema before in proxy layer we had only service-side filters
16:17:10 diablo_rojo ooOOOooo
16:17:16 gtema and on the cloud layer only client filters
16:17:36 gtema since we discourage usage of cloud layer I have created this change
16:17:48 gtema that is actually taking all possible filters in a single parameter
16:17:55 diablo_rojo I am all for unifying of functionality
16:18:10 gtema and applies server side what possible and rest on the fetched results
16:18:36 diablo_rojo Makes sense to me.
16:18:41 gtema I consider this type of change also as partially "breaking", even in reality it is not. But it introduces quite some behavior change
16:19:01 diablo_rojo Yeah that can be scary if you're familiar with the old functionality
16:19:09 gtema exactly
16:19:31 diablo_rojo seongsoocho: maybe you and your mentees can review the patch when you get some time?
16:19:32 gtema my idea is that once this lands we can really discuss making R1.0.0 finally
16:19:46 diablo_rojo gtema: is that something we want to note in the docs?
16:20:04 zeze wow
16:20:05 seongsoocho diablo_rojo: maybe , I and we will try it :-)
16:20:29 gtema haven't I?
16:20:34 gtema oh no, you are right
16:20:39 gtema that is why we need reviews
16:21:32 diablo_rojo_phone Bah, my computer up and died.
16:21:35 gtema ok, will update it once I have my hands in SDK area next time
16:22:00 diablo_rojo_phone Sounds good gtema
16:22:04 gtema but today is neither friday, nor 13. And still things misbehave
16:22:19 diablo_rojo_phone Yeah. Just black screen. No warning.
16:22:36 diablo_rojo_phone So now I'm on my phone but idk how the meeting commands will work.
16:22:48 gtema cool. In my TZ I would treat it as a sign to stop for today ;-)
16:23:25 gtema #topic manila patches status
16:23:26 diablo_rojo_phone Lol I wish.
16:23:34 diablo_rojo_phone Okay uhh.. next topic?
16:24:11 gtema I was wondering really what is the status with those batch of changes we had that are bit abandoned now
16:24:27 diablo_rojo_phone gouthamr: ^?
16:24:36 gouthamr ashrodri went around and refreshed a bunch of them recently
16:24:43 gtema (next topic - I thought you might have difficulties to type specific stuff from mobile)
16:25:00 gouthamr https://review.opendev.org/q/topic:openstacksdk-manila-support
16:25:00 gtema I hate typing from mobile - this is a fight agains auto-correct
16:25:07 gouthamr looks like we need to do them again
16:25:28 gouthamr thanks for checking on this though; i'll rebase and try to see if we can un-WIP some of these
16:25:52 gtema at least rebase would be the beginning
16:25:52 diablo_rojo_phone gtema: yeah less fast and less access to links :) Thank you.
16:26:07 gtema welcome diablo_rojo_phone
16:26:36 gtema wrt changes: once I looked last time on them there were unaddressed review comments or so and no activity at all
16:27:17 gtema if we can land at least some of them I would be happy to include them in R1
16:28:03 gtema otherwise we would need to leave them for later. I do not want to see this much of work simply abandoned
16:28:04 gouthamr great! i rechecked a couple and added my +2 back
16:28:14 gtema cool, thks
16:28:30 diablo_rojo_phone Yay progress!
16:28:31 gtema once we land at least some of those I will take care of moving them to master branch
16:28:40 gouthamr great thanks gtema!
16:28:49 gtema wlcm
16:29:08 diablo_rojo_phone I think that was the last topic?
16:29:19 gtema yupp, the last
16:29:37 diablo_rojo_phone Sweet.
16:29:41 gtema I have one more topic, but without neutron folks support we can not do much
16:30:11 diablo_rojo_phone slaweq: around?
16:30:23 diablo_rojo_phone I don't see Lajos in this channel.
16:31:51 gtema I added it to agenda anyway. The question is that we have added some of the vpnaas functionality, but we can't test it since I can't understand how to activate it in devstack
16:32:07 gtema I did everything like vpnaas code does but tests are still skipped
16:32:17 diablo_rojo_phone Ahh that is indeed an issue.
16:32:32 diablo_rojo_phone I don't know how to set that stuff up in devstack either
16:33:02 gtema yeah, that is the point. I was asking slaweq about that, he promised to have a look, but most likely no time
16:33:35 diablo_rojo_phone That happens.
16:33:47 gtema right, this is life
16:34:21 diablo_rojo_phone Indeed
16:34:27 gtema that's all folks (c)
16:34:50 gtema or is it (r) - no clue
16:35:21 diablo_rojo_phone Yep that's it
16:36:16 diablo_rojo_phone #endmeeting
16:36:31 diablo_rojo_phone Except I have no authority.
16:36:36 gtema #agreed :)
16:36:38 diablo_rojo_phone On this nick apparently
16:36:43 seongsoocho diablo_rojo: gtema I have an one question to you. There seem to be a lot of old and already resolved issues registered in the storyboard. We want to find these and close the issue, but rather than closing it at will, we want to have you review it. How to do it efficiently?
16:36:44 gtema #endmeeting
16:37:14 frickler wait until the hour is up, then anyone can end the meeting
16:37:26 gtema hmm. My problem is that I can't use storyboard effectively, I just become mad after 10 seconds of starting with it
16:37:30 diablo_rojo_phone frickler: ahh got it. Thank you.
16:38:03 seongsoocho gtema: Yes.. The storyboard is really slow.
16:38:39 gtema seongsoocho, maybe you comment inside the issues whether you think it can be closed. At least I will receive email (if spamfilter will not catch it first)
16:39:01 gtema and with that at least I will have a chance to comment or really close it
16:39:27 seongsoocho Okay. I'll comment if I think I can close it.
16:39:40 gtema thanks
16:39:44 seongsoocho thanks

Earlier   Later