Thursday, 2022-08-18

opendevreviewAreg proposed openstack/openstacksdk master: Bugfix for paginating for complex paths  https://review.opendev.org/c/openstack/openstacksdk/+/85365613:22
seongsoochoHi, Do we have a monthly meeting today after 2 hrs? 14:14
opendevreviewAreg proposed openstack/openstacksdk master: Bugfix for paginating for complex paths  https://review.opendev.org/c/openstack/openstacksdk/+/85365614:44
diablo_rojoI do think we should meet briefly today.15:08
seongsoochookay15:08
fricklergtema: couple of failures with osc 6, maybe you can also a look? https://review.opendev.org/c/openstack/requirements/+/85361215:49
gtemaok, will check15:53
gtema    python-octaviaclient 3.0.0 depends on python-openstackclient>=3.12.015:54
gtema    The user requested (constraint) python-openstackclient===6.0.015:54
gtemainterestingly just 1 hour ago was looking into octaviaclient issues - LOL15:55
johnsomgtema Let me know if I can help with any octavia client questions15:56
gtemasure. Now need to decode why for pip >=3.12.0 is not good with constraint ===6.0.015:57
diablo_rojomeeting agenda is here: https://etherpad.opendev.org/p/openstacksdk-meeting-agenda15:59
seongsoochoHi o/ , I invited our mentee here to join and watch the meeting.16:00
zezehi16:00
hoosaHi o/16:01
diablo_rojoseongsoocho: excellent!16:01
YooSoo_LIMHi \o/16:01
diablo_rojogtema: do you want to run the meeting or shall I?16:01
frickleractually those failures look unrelated, maybe some pypi hickup16:01
gtemafeel free to run, since I am again "surprised" by the meeting16:02
diablo_rojo#startmeeting sdk_osc16:02
opendevmeetMeeting started Thu Aug 18 16:02:33 2022 UTC and is due to finish in 60 minutes.  The chair is diablo_rojo. Information about MeetBot at http://wiki.debian.org/MeetBot.16:02
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:02
opendevmeetThe meeting name has been set to 'sdk_osc'16:02
gtemaI am here, but absolutely not prepared16:02
diablo_rojogtema: no worries at all- I definitely sprung it on you16:02
diablo_rojo#link https://etherpad.opendev.org/p/openstacksdk-meeting-agenda16:03
diablo_rojoPing List: gouthamr: stephenfin amotoki 16:03
gouthamrheyy! :) 16:03
diablo_rojo+ myself and gtema but we are already here lol16:03
diablo_rojoOh weird. I did a + at the start of that message and my element client turned it into a bullet point. 16:04
stephenfino/16:04
diablo_rojoAnywho, feel free to throw things on the agenda and we will get started. 16:04
diablo_rojo#topic BU Students16:04
diablo_rojoSo, again we have the opportunity to mentor some students at BU 16:05
diablo_rojogtema and I started putting together a project proposal16:05
diablo_rojobut would love extra eyes on it before I send it back to the professors (Alan and Orran)16:05
diablo_rojo#link https://etherpad.opendev.org/p/BU-202216:06
diablo_rojoI think I will plan to send it mid next week so if you have comments/edits/feedback please get them in the etherpad by then16:06
gtemagreat16:06
diablo_rojoand then we can just use this etherpad for the actual mentorship too16:06
stephenfinsounds good16:06
diablo_rojoAll in one place as much as possible16:07
diablo_rojoAnything else on this topic? 16:07
gtemaany info on when they start?16:07
seongsoochoI'm really interesting the agenda of mentoship to BU.16:07
diablo_rojoIt would be early to mid September16:07
gtemaokay16:07
diablo_rojoseongsoocho: for inspiration for you own mentorship? 16:07
diablo_rojogtema: and it will end probably mid December16:08
gtemaughm, again so short16:08
diablo_rojoYeah it is :/16:08
seongsoochoYes. It is very simiilar with my own mentorship . the different is I am a mentor too but I have to study this project :-) 16:08
diablo_rojoAt least Violet is sticking around for the foreseeable future and now is up and running. 16:08
gtemayes, that is good. That change should be merged now16:09
diablo_rojoseongsoocho: well you are welcome to attend our meetings with the students once we get started but idk when that will be or what the tz overlap will look like16:09
diablo_rojoShall I move on? 16:10
gtemayupp, pls16:10
diablo_rojo#topic PTG Planning16:10
seongsoochogreat16:10
diablo_rojoThe team is signed up as participating16:10
diablo_rojoThe deadline isnt till the 26th so the full list of all teams wont be final till the 30th, 16:11
gtemaawesome, thanks16:11
diablo_rojobut after that maybe we can get on some of the teams agendas to give them status/ invite them to get more involved? 16:11
diablo_rojoJust a thought I had16:11
gtemayeah, why not16:12
diablo_rojoAlso, would be good to get any/all of the students we have together to talk about their work and meet each other + the community16:12
diablo_rojotry to build up the connection to keep them around past the semester end16:12
gtemayeah, that would be really cool16:12
gtemasadly last years they were not active enough to participate on PTG16:12
diablo_rojoI will have a think on that a bit more... but any ideas are obviously welcome :) 16:12
diablo_rojogtema: I think there was one like.. a year + ago that we had NDSU students and BU students16:13
diablo_rojoEither way- everyone should register as its free: https://openinfra-ptg.eventbrite.com/16:13
gtemayeah, maybe one. But definitely majority was even with a reminder not participating16:13
diablo_rojogtema: yeah, would be good to stress the importance16:14
gtema:)16:14
diablo_rojomaybe make that our 'check in ' meeting for the week16:14
diablo_rojoor what have you- kinda push them to come16:14
gtemayupp, why not16:14
gtemathe only thing - they should not have courses at this time, otherwise they have excuse16:14
diablo_rojoOnce 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
diablo_rojogtema: +216:15
gtemayeah, no hurry now16:15
diablo_rojoAnything else on the PTG topic?16:15
gtemawe anyway do not even know how many of the students will we have16:15
gtemanothing from my side16:15
diablo_rojogtema: also true16:16
diablo_rojoOkay next topic then16:16
diablo_rojo#topic Last Interface Change before R1.016:16
diablo_rojo#link https://review.opendev.org/c/openstack/openstacksdk/+/85305216:16
gtemayeah, I feel burden with waiting of the R1.0 and decided to pack the last change into the queue16:16
diablo_rojoI think this topic was yours gtema ?16:16
gtemayeah, mine16:16
gtemathis change is unifying listing filtering16:16
diablo_rojoAh okay. 16:16
gtemabefore in proxy layer we had only service-side filters16:17
diablo_rojoooOOOooo16:17
gtemaand on the cloud layer only client filters16:17
gtemasince we discourage usage of cloud layer I have created this change16:17
gtemathat is actually taking all possible filters in a single parameter16:17
diablo_rojoI am all for unifying of functionality16:17
gtemaand applies server side what possible and rest on the fetched results16:18
diablo_rojoMakes sense to me. 16:18
gtemaI consider this type of change also as partially "breaking", even in reality it is not. But it introduces quite some behavior change16:18
diablo_rojoYeah that can be scary if you're familiar with the old functionality16:19
gtemaexactly16:19
diablo_rojoseongsoocho: maybe you and your mentees can review the patch when you get some time? 16:19
gtemamy idea is that once this lands we can really discuss making R1.0.0 finally16:19
diablo_rojogtema: is that something we want to note in the docs? 16:19
zezewow16:20
seongsoochodiablo_rojo:   maybe , I and we will try it :-) 16:20
gtemahaven't I?16:20
gtemaoh no, you are right16:20
gtemathat is why we need reviews16:20
diablo_rojo_phoneBah, my computer up and died. 16:21
gtemaok, will update it once I have my hands in SDK area next time16:21
diablo_rojo_phoneSounds good gtema 16:22
gtemabut today is neither friday, nor 13. And still things misbehave16:22
diablo_rojo_phoneYeah. Just black screen. No warning. 16:22
diablo_rojo_phoneSo now I'm on my phone but idk how the meeting commands will work. 16:22
gtemacool. In my TZ I would treat it as a sign to stop for today ;-)16:22
gtema#topic manila patches status16:23
diablo_rojo_phoneLol I wish. 16:23
diablo_rojo_phoneOkay uhh.. next topic? 16:23
gtemaI was wondering really what is the status with those batch of changes we had that are bit abandoned now16:24
diablo_rojo_phonegouthamr: ^? 16:24
gouthamrashrodri went around and refreshed a bunch of them recently16:24
* gouthamr finds links16:24
gtema(next topic - I thought you might have difficulties to type specific stuff from mobile)16:24
gouthamrhttps://review.opendev.org/q/topic:openstacksdk-manila-support 16:25
gtemaI hate typing from mobile - this is a fight agains auto-correct16:25
gouthamrlooks like we need to do them again16:25
gouthamrthanks for checking on this though; i'll rebase and try to see if we can un-WIP some of these16:25
gtemaat least rebase would be the beginning16:25
diablo_rojo_phonegtema: yeah less fast and less access to links :) Thank you. 16:25
gtemawelcome diablo_rojo_phone16:26
gtemawrt changes: once I looked last time on them there were unaddressed review comments or so and no activity at all16:26
gtemaif we can land at least some of them I would be happy to include them in R116:27
gtemaotherwise we would need to leave them for later. I do not want to see this much of work simply abandoned16:28
gouthamrgreat! i rechecked a couple and added my +2 back16:28
gtemacool, thks16:28
diablo_rojo_phoneYay progress! 16:28
gtemaonce we land at least some of those I will take care of moving them to master branch16:28
gouthamrgreat thanks gtema!16:28
gtemawlcm16:28
diablo_rojo_phoneI think that was the last topic? 16:29
gtemayupp, the last16:29
diablo_rojo_phoneSweet. 16:29
gtemaI have one more topic, but without neutron folks support we can not do much16:29
diablo_rojo_phoneslaweq: around? 16:30
diablo_rojo_phoneI don't see Lajos in this channel. 16:30
gtemaI 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 devstack16:31
gtemaI did everything like vpnaas code does but tests are still skipped16:32
diablo_rojo_phoneAhh that is indeed an issue.16:32
diablo_rojo_phoneI don't know how to set that stuff up in devstack either16:32
gtemayeah, that is the point. I was asking slaweq about that, he promised to have a look, but most likely no time16:33
diablo_rojo_phoneThat happens. 16:33
gtemaright, this is life16:33
diablo_rojo_phoneIndeed16:34
gtemathat's all folks (c)16:34
gtemaor is it (r) - no clue16:34
diablo_rojo_phoneYep that's it16:35
diablo_rojo_phone#endmeeting16:36
diablo_rojo_phoneExcept I have no authority. 16:36
gtema#agreed :)16:36
diablo_rojo_phoneOn this nick apparently 16:36
seongsoochodiablo_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
gtema#endmeeting16:36
fricklerwait until the hour is up, then anyone can end the meeting16:37
gtemahmm. My problem is that I can't use storyboard effectively, I just become mad after 10 seconds of starting with it16:37
diablo_rojo_phonefrickler: ahh got it. Thank you. 16:37
seongsoochogtema:  Yes..  The storyboard is really slow.16:38
gtemaseongsoocho, 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:38
gtemaand with that at least I will have a chance to comment or really close it16:39
seongsoochoOkay. I'll comment if I think I can close it.16:39
gtemathanks16:39
seongsoochothanks16:39
slaweqgtema: hi, sorry, I forgot about it16:40
slaweqDo you have patch woth that job so I can check it?16:40
gtemaslaweq: no worries, it will not run away16:40
gtemahttps://review.opendev.org/c/openstack/openstacksdk/+/84661816:40
slaweqI'm not at my desk now but I will take a look later tonight or tomorrow morning 16:40
diablo_rojoI'm back!16:41
diablo_rojo#endmeeting16:41
opendevmeetMeeting ended Thu Aug 18 16:41:16 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:41
opendevmeetMinutes:        https://meetings.opendev.org/meetings/sdk_osc/2022/sdk_osc.2022-08-18-16.02.html16:41
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/sdk_osc/2022/sdk_osc.2022-08-18-16.02.txt16:41
opendevmeetLog:            https://meetings.opendev.org/meetings/sdk_osc/2022/sdk_osc.2022-08-18-16.02.log.html16:41
diablo_rojoI guess I could have kept it going since slaweq is here now16:41
* diablo_rojo facepalms16:41
gtemaawesome, thanks. In the change I just repeated how vpnaas code sets up jobs, but tests are still skipped, so I do not know whether the it is not activated, or whether tests are having wrong skip16:41
gtemahe is not on desk, therefore no problems of not logging it16:42
gtemas/on/at/16:42
*** rcastillo|rover_ is now known as rcastillo|rover19:16
opendevreviewhai wu proposed openstack/openstacksdk master: Add support for fault object per Server API  https://review.opendev.org/c/openstack/openstacksdk/+/85370320:36
opendevreviewhai wu proposed openstack/openstacksdk master: Add support for fault object per Server API  https://review.opendev.org/c/openstack/openstacksdk/+/85370320:56
opendevreviewhai wu proposed openstack/openstacksdk master: Add support for fault object per Server API  https://review.opendev.org/c/openstack/openstacksdk/+/85370320:57
*** rcastillo|rover is now known as rcastillo23:13

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