Thursday, 2021-03-18

*** tosky has quit IRC00:22
*** brinzhang has joined #openstack-sdks01:59
*** brinzhang_ has quit IRC02:00
openstackgerritShnaidman Sagi (Sergey) proposed openstack/ansible-collections-openstack master: Object module for management Swift objects  https://review.opendev.org/c/openstack/ansible-collections-openstack/+/77971802:27
*** LinPeiWen has quit IRC03:05
*** evrardjp has quit IRC03:33
*** evrardjp has joined #openstack-sdks03:33
*** enriquetaso has quit IRC04:10
*** LinPeiWen has joined #openstack-sdks04:47
*** brinzhang_ has joined #openstack-sdks04:57
*** whoami-rajat_ has joined #openstack-sdks04:58
*** brinzhang has quit IRC05:01
*** udesale has joined #openstack-sdks05:04
*** ysandeep|away is now known as ysandeep06:03
*** Luzi has joined #openstack-sdks06:04
*** khomesh24 has joined #openstack-sdks06:42
*** ricolin has quit IRC06:48
*** ralonsoh has joined #openstack-sdks07:18
*** gtema has joined #openstack-sdks07:27
*** rpittau|afk is now known as rpittau07:51
*** jawad_axd has joined #openstack-sdks08:29
*** LinPeiWen has quit IRC08:34
*** tosky has joined #openstack-sdks08:37
openstackgerritMerged openstack/python-openstackclient master: project cleanup  https://review.opendev.org/c/openstack/python-openstackclient/+/73448508:39
openstackgerritMerged openstack/python-openstackclient stable/victoria: Add reno for change Ic3c555226a220efd9b0f27edffccf6c4c95c2747  https://review.opendev.org/c/openstack/python-openstackclient/+/77013008:40
*** LinPeiWen has joined #openstack-sdks08:54
*** jpich has joined #openstack-sdks09:00
*** ysandeep is now known as ysandeep|afk09:26
*** jpich has quit IRC09:33
*** jpich has joined #openstack-sdks09:34
*** whoami-rajat_ is now known as whoami-rajat09:53
*** udesale has quit IRC10:55
*** dtantsur|afk is now known as dtantsur11:02
*** jpich has quit IRC11:18
*** jpich has joined #openstack-sdks11:19
*** ysandeep|afk is now known as ysandeep11:19
*** jawad_axd has quit IRC12:02
*** emmadavis has quit IRC12:04
*** slaweq has quit IRC12:22
*** slaweq has joined #openstack-sdks12:25
*** gtema has quit IRC12:33
*** ricolin has joined #openstack-sdks12:44
*** gtema has joined #openstack-sdks12:47
*** yolanda has quit IRC12:52
*** nightmare_unreal has joined #openstack-sdks12:56
*** enriquetaso has joined #openstack-sdks13:23
*** artom has quit IRC13:24
diablo_rojo_phonNo meeting today?14:06
gtemayes/no/maybe/dunno...14:06
gtemaI am available14:06
gtemaah, you mean time? we agreed to reschedule it to 16:00UTC, forgot?14:07
gtemaso still time to sleep14:07
diablo_rojo_phonI did forget :)14:09
* diablo_rojo_phon goes back to sleep14:09
*** artom has joined #openstack-sdks14:14
amotokiI would like to say sorry on my contributions in this cycle. Delegating horizon topics did not succeed and took more time than I thought.14:17
amotokiI have no topic from me for today's meeting.14:18
gtemano worries, this cycle is for most of us pretty hard14:18
amotokiI still would like to catch up with the recent status :)14:18
*** mgoddard has quit IRC14:49
*** mgoddard has joined #openstack-sdks14:56
*** holser has quit IRC14:58
*** holser has joined #openstack-sdks15:01
*** diablo_rojo has joined #openstack-sdks15:32
*** Luzi has quit IRC15:46
*** ysandeep is now known as ysandeep|away15:51
twilit_dragongtema, when you're able, could you point me to a resource that verifies query parameters in its test file? For reference I've been looking at a couple resources (types, volumes) that have query parameters in their list requests, but to me it looks like there's some inconsistencies when verifying queries within each of their unit test files.15:56
gtemasure - https://opendev.org/openstack/openstacksdk/src/branch/master/openstack/tests/unit/compute/v2/test_flavor.py#L5615:56
twilit_dragonThanks!15:57
gtemalimit, marker are present by "default" everywhere15:57
gtemaso, it's time now for the SDK meeting16:00
gtema#startmeeting sdk_osc16:00
openstackMeeting started Thu Mar 18 16:00:51 2021 UTC and is due to finish in 60 minutes.  The chair is gtema. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: sdk_osc)"16:00
openstackThe meeting name has been set to 'sdk_osc'16:00
gtemadiablo_rojo, diablo_rojo_phon, gouthamr, gtema, stephenfin, amotoki is anybody here for the meeting?16:01
diablo_rojoo/16:01
-amotoki- lurks16:01
diablo_rojoI am here but I don't think I have anything I need to discuss?16:01
gtemanot really, perhaps vPTG planning16:02
diablo_rojoIts mostly if any of the students need to discuss anything16:02
diablo_rojoOh thats a good idea16:02
diablo_rojoDeadline will be before our next meeting16:02
diablo_rojoI definitely think we should meet for a couple hours one or two days like last time.16:03
gtemaI opened ethercalc and my system froze ;-)16:03
gtemaI booked Wed 21 15-1716:03
gtemabut haven't really planned anything yet.16:03
diablo_rojogtema, yeah I botched making that link- I somehow managed to use, not our instance of ethercalc and so it likes to freeze.16:03
gtemaIs there a demand for PTG?16:03
diablo_rojogtema, maybe make a planning etherpad and circulate it?16:03
gtemasomething I wanted to do over a week already, but haven't really managed16:04
diablo_rojoHonestly, I think it would be cool to get all the students together, but also for you to do a braindump of like.. what all needs to be done so we can get that into storyboard so its easier for people to pick things up?16:04
gtemawhat was the link I need to follow also for getting booked?16:04
gtemaI have one thing for the PTG - it's a R1.0 planning with all the challenges16:05
gtemaso there is something to be discussed16:05
diablo_rojohttps://openinfrafoundation.formstack.com/forms/april2021_vptg_survey16:05
gtemaand getting all the students is surely cool16:05
diablo_rojoApparently so16:05
diablo_rojolol16:05
gtemathks16:05
diablo_rojoNo problem!16:06
stephenfino/16:06
diablo_rojoAlso, don't forget to register: https://april2021-ptg.eventbrite.com/16:06
diablo_rojoHello stephenfin :) Just chatting about the PTG16:06
gtemadiablo_rojo - filled the survey. Thanks, lost the link16:07
diablo_rojogtema, no worries :)16:07
gtemaI will try not to forget to send email with planning16:08
gtemaare there other interesting topics to discuss?16:09
diablo_rojogtema, if you don't by the middleish of next week I can try to remember.16:09
diablo_rojoNothing else from me?16:10
gtemathks16:10
gtemawas it a question? "Nothing else from me?"16:10
stephenfinI've one thing16:10
stephenfinReleases16:10
stephenfinI _think_ we're currently tied to trailing release or some such thing for OSC16:11
stephenfini.e. we have 'stable/{release}' branches16:11
gtemaah yeah, this one is also completely lost in overload this week16:11
diablo_rojogtema, no question :) Sorry to be confusing.16:11
stephenfinDo we want to look at changing that to independent?16:12
gtemadiablo_rojo - was more a joke ;-)16:12
diablo_rojoI feel like that's reasonable stephenfin ?16:12
stephenfinRationale being that OSC isn't really tied to any particular OpenStack release. In theory it should support every release16:12
diablo_rojogtema, lol I am too tired to catch that sorry. Need more caffeine.16:13
gtemaI have no problems with that. But maybe TC have something in mind?16:13
stephenfinYeah, I'm not sure how we do it, but I can investigate16:13
amotokiI think we are still in sync with our release to some extent I think.16:14
diablo_rojoFrom a TC standpoint, I don't think we care? It's more the release team?16:14
stephenfinI figure we can and should release any time we have enough "stuff" to justify it16:14
* diablo_rojo digs through pile of hats for release hat16:14
stephenfinamotoki: You think? How so?16:14
amotokistephenfin: I thoght we are discussing about _indepedent release, but I might misundertand the context.16:15
stephenfinNo, you understood correctly :)16:15
amotokiwe sometimes have things related to releases16:15
stephenfinMost of our work now is less about keeping up with new changes, since APIs change less frequently than before. It's more about filling in gaps in old releases16:16
gtemawe can actually release client things for not yet released stuff16:16
amotokiso stable branches can help us regarding backports.16:16
stephenfinand you can use new OSC versions with old service versions16:16
stephenfinHmm, can we get stable branches that are based on releases instead?16:16
stephenfini.e. stable/5.0 ?16:16
stephenfinMaybe that's too much work unless we're very careful about how often we release16:17
gtemaugh, that's interesting16:17
amotokiit is debatable. we cover most releases, so it is not a problem for most cases I think,16:17
gtemaI actually dislike heavily stable branches for SDK and OSC. They are made to be always backward compatible16:17
amotokiso I don't have strong preference on this16:18
stephenfingtema: True, though we do occasionally do things like drop Python versions16:18
gtemayes16:18
gtemaand we are also potentially caught in the service using dedicated version of SDK16:18
stephenfinthat's less of an issue for OSC though, since that's only used in the client environment16:18
stephenfinyeah, more of an issues for sdk since that can be embedded in the service16:19
gtemaI would be careful here16:19
amotokiyes for most cases. no stable branches sometimes disallow us to fix bugs in released versions16:19
amotokithat's all I see as a minus point.16:19
amotokibut that would be minor.16:19
stephenfinlet me think about it more and maybe discuss with release management folks16:20
gtemarecently I landed image command redesign (to rely on SDK) and some time later figured out that some other dependent client got broken by that16:20
amotokiI mean big fixes16:20
gtemaI guess it was masakari16:20
stephenfinIt's not high priority. It just occurred to me that we might want to change things when gtema was working through patches ahead of the release16:20
stephenfinamotoki: Yeah, that's a good point. I'll pay particular attention to this16:20
gtemait clear stephenfin and I am also currently "bombed" by release team wishing a release of OSC16:21
stephenfindo you need help?16:21
stephenfinI've got some spare time at the moment since nova is in feature freeze16:21
stephenfinnot much but some :)16:21
gtemawell, it's generally just cur a release16:21
gtemacut16:22
gtemaand I landed today few things, one self-approved with project cleanup, since around a year it lacks reviews, but people permanently ask for it16:22
gtemaso I guess we can cut release now16:22
stephenfinOh, yes, I saw that. I thought we were still waiting for the openstacksdk side of that to merge so I hadn't reviewed it. Sorry /o\16:23
amotokiantoher way is to overcome it by cutting more releases from master branch independently from OpenStack release cycle16:23
gtemait landed actually 1,5 year ago16:23
stephenfingtema: Ouch. Then I'm doubly sorry. I missed that16:23
amotokibut we still need to take into account our OpenStack distributors like RHOSP16:23
diablo_rojoI could probably help with that if you need too. I vaguely remember how to do it.16:23
stephenfinfwiw, I reviewed this morning and it looks good to me16:23
gtemathere is continuous place for improvement and adding new services inside, but OSC side is now at least capable calling it16:23
stephenfinamotoki: Also a good idea. fwiw, we're having discussions about how we can improve our OSC situation internally at the moment. We kind of ignore it now (as in there is no one person in charge of it) since most people are using OSC from their clients which aren't necessarily running the same stack as their servers16:25
stephenfinso RHOSP shouldn't be a major concern in any changes to lifecycle, IMO16:25
stephenfinI can't speak for any other distro, however16:25
gtemadear RedHatters - clarify it ;-)16:26
gtemaI see lot of "distos" and cloud providers try to tie to the release16:26
* mordred could never get anyone to care about OSC or SDK while I was there ...16:26
openstackgerritJames Palmer proposed openstack/openstacksdk master: Add support for Resource Filters  https://review.opendev.org/c/openstack/openstacksdk/+/77627116:26
gtemaand always they consider SDK/OSC part of that16:26
amotokithanks, so perhaps it is better to keep our release on OSC/SDK from the mater continuously16:27
stephenfinmordred: Horizon either. It's not classed as core, I guess16:27
stephenfineven though it's what 90% of users see, I know16:27
amotokihehe, as my hat of horizon, horizon faield to support system-scope in Wallaby :-(16:28
stephenfingtema: If we're cutting a release, do we want to go through the final few "not in merge conflict" patches for OSC and see if any are good to go?16:28
stephenfinOr should we just cut and punt those to the next release?16:28
gtemastephenfin - yupp, let's do that16:28
stephenfinOkay, I'll spend tomorrow at that so16:28
gtemaI mean the first one (time lag is killing the sense)16:28
stephenfinoh16:28
stephenfinokay yeah16:28
stephenfinI see about 30 or so, and many more in merge conflict. Will see how many are ready to roll and defer the rest16:29
stephenfinThis will be a big release16:29
gtemayupp, but moslty only covering gaps16:29
stephenfinYeah, true16:30
diablo_rojoEven still, exciting to have progress on things16:30
stephenfinindeed16:30
gtemayeah, I sadly admit I failed to complete switch of compute things to use SDK16:30
gtemastarted good but then lost the track16:31
gtemaand then figured out that for SDK R1 we also need lot of love in parallel16:31
gtemaanything else we want to discuss?16:32
stephenfinnot from me16:32
amotokinothing from me too16:33
amotokithis timeslot per month works for me :)16:33
gtemagreat16:33
gtemaokay, then I wish everybody a nice day/evening/sleep16:34
gtema#endmeeting16:34
*** openstack changes topic to "Bug tracker for SDK and OSC is now at https://storyboard.openstack.org"16:34
openstackMeeting ended Thu Mar 18 16:34:30 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:34
openstackMinutes:        http://eavesdrop.openstack.org/meetings/sdk_osc/2021/sdk_osc.2021-03-18-16.00.html16:34
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/sdk_osc/2021/sdk_osc.2021-03-18-16.00.txt16:34
openstackLog:            http://eavesdrop.openstack.org/meetings/sdk_osc/2021/sdk_osc.2021-03-18-16.00.log.html16:34
amotokithanks all!16:34
gtemasee ya16:34
*** Luzi has joined #openstack-sdks17:01
*** rpittau is now known as rpittau|afk17:11
*** jpich has quit IRC17:17
openstackgerritMerged openstack/openstacksdk master: Add set_readonly_volume to BlockStorageCloudMixin  https://review.opendev.org/c/openstack/openstacksdk/+/77626617:24
*** Luzi has quit IRC17:37
*** frenzy_friday is now known as frenzyfriday|bbl17:43
*** dtantsur is now known as dtantsur|afk17:55
*** jawad_axd has joined #openstack-sdks18:14
*** gtema has quit IRC18:16
*** gtema has joined #openstack-sdks18:30
*** frenzyfriday|bbl is now known as frenzy_friday18:46
*** jawad_axd has quit IRC18:47
*** nightmare_unreal has quit IRC18:49
*** khomesh24 has quit IRC18:52
*** openstackgerrit has quit IRC19:34
*** gtema has quit IRC21:05
*** ralonsoh has quit IRC21:20
*** sshnaidm is now known as sshnaidmoff21:21
*** sshnaidmoff is now known as sshnaidm|off21:21
*** whoami-rajat has quit IRC21:26
*** openstackstatus has quit IRC21:26
*** openstack has joined #openstack-sdks21:38
*** ChanServ sets mode: +o openstack21:38
*** openstack has joined #openstack-sdks22:03
*** ChanServ sets mode: +o openstack22:03
*** iurygregory has quit IRC22:09
*** iurygregory has joined #openstack-sdks22:09
*** holser has quit IRC22:23

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