Earlier  
Posted Nick Remark
#openstack-sdks - 2021-03-17
00:24:51 openstackgerrit Ashley Rodriguez proposed openstack/openstacksdk master: Add share resource to shared file system https://review.opendev.org/c/openstack/openstacksdk/+/775707
00:43:43 openstackgerrit Ashley Rodriguez proposed openstack/openstacksdk master: Add share resource to shared file system https://review.opendev.org/c/openstack/openstacksdk/+/775707
05:06:21 openstackgerrit Goutham Pacha Ravi proposed openstack/openstacksdk master: Add export location resource to shared file system https://review.opendev.org/c/openstack/openstacksdk/+/780990
17:09:01 openstackgerrit Ryan Zimmerman proposed openstack/openstacksdk master: Add compute microversion 2.57 https://review.opendev.org/c/openstack/openstacksdk/+/781131
17:24:31 openstackgerrit Ryan Zimmerman proposed openstack/openstacksdk master: Add compute microversion 2.57 https://review.opendev.org/c/openstack/openstacksdk/+/781131
17:24:56 openstackgerrit Ryan Zimmerman proposed openstack/openstacksdk master: Add compute microversion 2.57 https://review.opendev.org/c/openstack/openstacksdk/+/781131
17:37:57 diablo_rojo stephenfin, gtema do you have some time today to review zimmerry's patch?
17:38:04 diablo_rojo zimmerry, got a link for them? :)
17:38:19 zimmerry https://review.opendev.org/c/openstack/openstacksdk/+/745375
17:39:28 gtema ok, will try to have another look tomorrow, today no buffer, sorry
17:39:42 diablo_rojo no worries gtema tomorrow works
21:07:36 openstackgerrit Dylan Zapzalka proposed openstack/openstacksdk master: Added support for the GroupSnapshot resource https://review.opendev.org/c/openstack/openstacksdk/+/781163
21:42:58 openstackgerrit Polina Gubina proposed openstack/ansible-collections-openstack master: Object module for management Swift objects https://review.opendev.org/c/openstack/ansible-collections-openstack/+/779718
#openstack-sdks - 2021-03-18
02:27:15 openstackgerrit Shnaidman Sagi (Sergey) proposed openstack/ansible-collections-openstack master: Object module for management Swift objects https://review.opendev.org/c/openstack/ansible-collections-openstack/+/779718
08:39:40 openstackgerrit Merged openstack/python-openstackclient master: project cleanup https://review.opendev.org/c/openstack/python-openstackclient/+/734485
08:40:15 openstackgerrit Merged openstack/python-openstackclient stable/victoria: Add reno for change Ic3c555226a220efd9b0f27edffccf6c4c95c2747 https://review.opendev.org/c/openstack/python-openstackclient/+/770130
14:06:01 diablo_rojo_phon No meeting today?
14:06:34 gtema yes/no/maybe/dunno...
14:06:41 gtema I am available
14:07:27 gtema ah, you mean time? we agreed to reschedule it to 16:00UTC, forgot?
14:07:35 gtema so still time to sleep
14:09:25 diablo_rojo_phon I did forget :)
14:17:43 amotoki I 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:18:05 amotoki I have no topic from me for today's meeting.
14:18:08 gtema no worries, this cycle is for most of us pretty hard
14:18:22 amotoki I still would like to catch up with the recent status :)
15:56:18 twilit_dragon gtema, 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:58 gtema sure - https://opendev.org/openstack/openstacksdk/src/branch/master/openstack/tests/unit/compute/v2/test_flavor.py#L56
15:57:35 twilit_dragon Thanks!
15:57:40 gtema limit, marker are present by "default" everywhere
16:00:41 gtema so, it's time now for the SDK meeting
16:00:51 gtema #startmeeting sdk_osc
16:00:51 openstack Meeting 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:52 openstack Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:54 openstack The meeting name has been set to 'sdk_osc'
16:01:18 gtema diablo_rojo, diablo_rojo_phon, gouthamr, gtema, stephenfin, amotoki is anybody here for the meeting?
16:01:26 diablo_rojo o/
16:01:43 diablo_rojo I am here but I don't think I have anything I need to discuss?
16:02:02 gtema not really, perhaps vPTG planning
16:02:11 diablo_rojo Its mostly if any of the students need to discuss anything
16:02:17 diablo_rojo Oh thats a good idea
16:02:38 diablo_rojo Deadline will be before our next meeting
16:03:06 diablo_rojo I definitely think we should meet for a couple hours one or two days like last time.
16:03:10 gtema I opened ethercalc and my system froze ;-)
16:03:26 gtema I booked Wed 21 15-17
16:03:36 gtema but haven't really planned anything yet.
16:03:43 diablo_rojo gtema, yeah I botched making that link- I somehow managed to use, not our instance of ethercalc and so it likes to freeze.
16:03:46 gtema Is there a demand for PTG?
16:03:57 diablo_rojo gtema, maybe make a planning etherpad and circulate it?
16:04:23 gtema something I wanted to do over a week already, but haven't really managed
16:04:47 diablo_rojo Honestly, 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:50 gtema what was the link I need to follow also for getting booked?
16:05:20 gtema I have one thing for the PTG - it's a R1.0 planning with all the challenges
16:05:27 gtema so there is something to be discussed
16:05:37 diablo_rojo https://openinfrafoundation.formstack.com/forms/april2021_vptg_survey
16:05:41 gtema and getting all the students is surely cool
16:05:42 diablo_rojo Apparently so
16:05:45 diablo_rojo lol
16:05:56 gtema thks
16:06:03 diablo_rojo No problem!
16:06:04 stephenfin o/
16:06:10 diablo_rojo Also, don't forget to register: https://april2021-ptg.eventbrite.com/
16:06:17 diablo_rojo Hello stephenfin :) Just chatting about the PTG
16:07:05 gtema diablo_rojo - filled the survey. Thanks, lost the link
16:07:27 diablo_rojo gtema, no worries :)
16:08:09 gtema I will try not to forget to send email with planning
16:09:40 gtema are there other interesting topics to discuss?
16:09:59 diablo_rojo gtema, if you don't by the middleish of next week I can try to remember.
16:10:03 diablo_rojo Nothing else from me?
16:10:14 gtema thks
16:10:31 gtema was it a question? "Nothing else from me?"
16:10:41 stephenfin I've one thing
16:10:45 stephenfin Releases
16:11:19 stephenfin I _think_ we're currently tied to trailing release or some such thing for OSC
16:11:28 stephenfin i.e. we have 'stable/{release}' branches
16:11:46 gtema ah yeah, this one is also completely lost in overload this week
16:11:56 diablo_rojo gtema, no question :) Sorry to be confusing.
16:12:25 stephenfin Do we want to look at changing that to independent?
16:12:37 gtema diablo_rojo - was more a joke ;-)
16:12:46 diablo_rojo I feel like that's reasonable stephenfin ?
16:12:51 stephenfin Rationale being that OSC isn't really tied to any particular OpenStack release. In theory it should support every release
16:13:05 diablo_rojo gtema, lol I am too tired to catch that sorry. Need more caffeine.
16:13:29 gtema I have no problems with that. But maybe TC have something in mind?
16:13:52 stephenfin Yeah, I'm not sure how we do it, but I can investigate
16:14:13 amotoki I think we are still in sync with our release to some extent I think.
16:14:16 diablo_rojo From a TC standpoint, I don't think we care? It's more the release team?
16:14:24 stephenfin I figure we can and should release any time we have enough "stuff" to justify it
16:14:36 stephenfin amotoki: You think? How so?
16:15:20 amotoki stephenfin: I thoght we are discussing about _indepedent release, but I might misundertand the context.
16:15:52 stephenfin No, you understood correctly :)
16:15:54 amotoki we sometimes have things related to releases
16:16:12 stephenfin Most 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 releases
16:16:13 gtema we can actually release client things for not yet released stuff
16:16:14 amotoki so stable branches can help us regarding backports.
16:16:36 stephenfin and you can use new OSC versions with old service versions
16:16:49 stephenfin Hmm, can we get stable branches that are based on releases instead?
16:16:58 stephenfin i.e. stable/5.0 ?
16:17:14 stephenfin Maybe that's too much work unless we're very careful about how often we release
16:17:14 gtema ugh, that's interesting
16:17:37 amotoki it is debatable. we cover most releases, so it is not a problem for most cases I think,

Earlier   Later