| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2023-08-29 | |||
| 16:21:32 | bauzas | I'll continue to give a few review rounds till the last day, but I also need traction from others :) | |
| 16:22:50 | bauzas | and if you're an owner of one of those series, feel free to ping us on IRC if you think you'd like feedback | |
| 16:24:11 | bauzas | I think we're done on this topic | |
| 16:24:46 | bauzas | I'll probably ping a couple of folks after this meeting to get a proper status | |
| 16:25:30 | bauzas | #topic Review priorities | |
| 16:25:36 | bauzas | #link https://review.opendev.org/q/status:open+(project:openstack/nova+OR+project:openstack/placement+OR+project:openstack/os-traits+OR+project:openstack/os-resource-classes+OR+project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/osc-placement)+(label:Review-Priority%252B1+OR+label:Review-Priority%252B2) | |
| 16:26:27 | bauzas | #topic Stable Branches | |
| 16:26:34 | bauzas | elodilles: floor is yours | |
| 16:26:46 | elodilles | well, i was on PTO last week, | |
| 16:27:02 | elodilles | and i didn't see much activity on stable branches | |
| 16:27:16 | elodilles | i guess people are more focused on Bobcat nowadays ;) | |
| 16:27:25 | bauzas | this week, for sure | |
| 16:27:34 | elodilles | anyway, i'm not aware of any stable gate failures | |
| 16:27:47 | elodilles | #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci | |
| 16:28:02 | elodilles | feel free to add anything there if you find any issue ^^^ | |
| 16:28:28 | elodilles | that's all from me | |
| 16:28:49 | auniyal | #info Please{10} *review* these backport patches of stable 2023.1, zed and yoga for next minor release | |
| 16:28:59 | auniyal | #info most of these already have one +2. | |
| 16:29:07 | auniyal | #link https://etherpad.opendev.org/p/release-liaison-PatchesToReview | |
| 16:30:15 | bauzas | yeah, it would be nice to deliver some stable releases while we reach the rc period | |
| 16:30:23 | elodilles | ++ | |
| 16:30:53 | bauzas | I'll personnally doublecheck if some are missing my +2 | |
| 16:31:13 | auniyal | I added 2 more patches for stable/2023.1 | |
| 16:31:34 | auniyal | earlier bauzas had merged all | |
| 16:31:44 | bauzas | a 2023.1 stable release before we cut rc1 is important | |
| 16:32:09 | bauzas | operators can then upgrade to the latest .z release on Antelope before upgrading smoothly to Bobcat | |
| 16:32:27 | bauzas | but ok, I'll try to chase them down | |
| 16:32:54 | bauzas | on a note, my usual stable branches item : | |
| 16:33:00 | bauzas | #info train-eol patch proposed https://review.opendev.org/c/openstack/releases/+/885365 | |
| 16:33:08 | bauzas | I guess it's waiting a second releases core | |
| 16:33:13 | elodilles | oh, it's still not merged... :S | |
| 16:33:23 | elodilles | yes, it is waiting for that | |
| 16:33:35 | bauzas | I know US trains are pretty long | |
| 16:33:43 | elodilles | :) | |
| 16:33:55 | bauzas | anyway, moving on, last topic | |
| 16:34:01 | bauzas | #topic Open discussion | |
| 16:34:21 | bauzas | nothing on my agenda, ever after a wiki refresh | |
| 16:34:29 | bauzas | so, anything anyone ? | |
| 16:37:03 | bauzas | looks not | |
| 16:37:30 | bauzas | thanks all, and tbh I'm happy to see all of you back :) | |
| 16:37:36 | bauzas | #endmeetinh | |
| 16:37:38 | bauzas | doh | |
| 16:37:43 | opendevmeet | Log: https://meetings.opendev.org/meetings/nova/2023/nova.2023-08-29-16.00.log.html | |
| 16:37:43 | opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/nova/2023/nova.2023-08-29-16.00.txt | |
| 16:37:43 | opendevmeet | Minutes: https://meetings.opendev.org/meetings/nova/2023/nova.2023-08-29-16.00.html | |
| 16:37:43 | opendevmeet | Meeting ended Tue Aug 29 16:37:43 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | |
| 16:37:43 | bauzas | #endmeeting | |
| 16:37:46 | elodilles | thanks o/ | |
| 16:38:31 | gibi | o/ | |
| 17:38:47 | opendevreview | Merged openstack/os-vif master: Don't break traffic if port already exists https://review.opendev.org/c/openstack/os-vif/+/885127 | |
| 18:11:00 | opendevreview | Raul Moldovan proposed openstack/nova master: Update resources post live migration https://review.opendev.org/c/openstack/nova/+/892614 | |
| 20:28:41 | opendevreview | Raul Moldovan proposed openstack/nova master: Update resources post live migration https://review.opendev.org/c/openstack/nova/+/892614 | |
| #openstack-nova - 2023-08-30 | |||
| 00:01:08 | opendevreview | melanie witt proposed openstack/nova master: nova-manage: Add 'limits migrate_to_unified_limits' https://review.opendev.org/c/openstack/nova/+/891646 | |
| 01:26:45 | opendevreview | melanie witt proposed openstack/nova master: nova-manage: Add 'limits migrate_to_unified_limits' https://review.opendev.org/c/openstack/nova/+/891646 | |
| 04:33:18 | opendevreview | melanie witt proposed openstack/nova master: Add documentation for unified limits https://review.opendev.org/c/openstack/nova/+/893127 | |
| 04:42:28 | melwitt | bauzas: I looked at the blueprint status etherpad after reading the nova meeting notes, just fyi it's no longer WIP https://review.opendev.org/q/topic:bp%252Funified-limits-nova-tool-and-docs | |
| 06:44:22 | opendevreview | melanie witt proposed openstack/nova master: Add documentation for unified limits https://review.opendev.org/c/openstack/nova/+/893127 | |
| 06:50:49 | bauzas | melwitt: ack, will then look today :) | |
| 07:51:28 | opendevreview | Amit Uniyal proposed openstack/nova master: Delete dangling bdms https://review.opendev.org/c/openstack/nova/+/882284 | |
| 07:51:28 | opendevreview | Amit Uniyal proposed openstack/nova master: Reproducer for dangling bdms https://review.opendev.org/c/openstack/nova/+/889947 | |
| 08:43:04 | auniyal | bauzas, I have updated patches, can you please have another look | |
| 08:45:29 | bauzas | auniyal: sure | |
| 08:45:58 | auniyal | thanks | |
| 08:46:19 | auniyal | there are very less zuul jobs ran for reproducer patch -https://review.opendev.org/c/openstack/nova/+/889947/6?tab=change-view-tab-header-zuul-results-summary | |
| 08:46:26 | auniyal | like no nova-next | |
| 08:47:45 | auniyal | bauzas, is it because the only file which added/modified is in nova/tests directory ? | |
| 08:55:41 | bauzas | auniyal: indeed | |
| 08:55:57 | bauzas | hmmm, looks like we have a venv issue | |
| 08:56:07 | bauzas | https://zuul.opendev.org/t/openstack/build/b915c9886c2a420fbc686b2ca4ccece0 | |
| 08:56:43 | bauzas | most of the jobs are failing when creating the venv due to a NoneType exception | |
| 08:56:52 | bauzas | AttributeError I mean | |
| 09:01:46 | bauzas | nvm, this looks a transient issue https://zuul.opendev.org/t/openstack/builds?job_name=openstack-tox-py39&project=openstack%2Fnova&skip=0 | |
| 09:21:45 | opendevreview | melanie witt proposed openstack/nova master: Add documentation for unified limits https://review.opendev.org/c/openstack/nova/+/893127 | |
| 09:40:52 | bauzas | auniyal: I'm eventually +2 on the repro patch but please read my comment for understanding the difference between annotations and defaulting arguments, and why you should *never* set default args with mutables https://review.opendev.org/c/openstack/nova/+/889947/comment/34e10b03_a5d53174/ | |
| 09:51:55 | auniyal | bauzas, ack thanks | |
| 09:52:21 | auniyal | I knew about setting list() insignature but missed, thanks for the comments | |
| 09:53:20 | auniyal | can we +W this https://review.opendev.org/c/openstack/nova/+/881457 | |
| 09:55:32 | auniyal | bauzas, regading this https://review.opendev.org/c/openstack/nova/+/882284/47/nova/compute/manager.py#4246 | |
| 09:55:55 | auniyal | s on bdm.destroy(), bdm object wont get updated correct ? | |
| 09:56:17 | auniyal | from DB bdm will will deleted | |
| 09:56:33 | auniyal | but locally bdm object, will stay as same | |
| 09:59:52 | bauzas | auniyal: not if you play with mutables | |
| 10:00:01 | bauzas | bdms is a list, right? | |
| 10:00:09 | auniyal | yes | |
| 10:04:05 | bauzas | auniyal: https://paste.opendev.org/show/bBaeGvpA8Bx5sSF3wKgZ/ | |
| 10:05:02 | bauzas | in my example, tamper_bdms is altering a mutable object, which is a list | |
| 10:05:20 | bauzas | that's semantically identical to your _delete_dangling_bdms() method | |
| 10:05:30 | bauzas | (provided you alter it) | |
| 10:19:42 | auniyal | bauzas, I might be wrong but this is what I tested - https://paste.opendev.org/show/bnMHd0uJuFYaSWSuP3Gu/ | |
| 10:20:44 | auniyal | the first obj was bdms, then I destroyed one of bdm from it, there is no change in bdms, then later when I retrieved new bdms list, it did not have deleted bdm | |
| 10:20:55 | bauzas | auniyal: because you haven't deleted the local copy | |
| 10:21:05 | auniyal | yes, | |
| 10:21:08 | bauzas | bdm.destroy() doesn't remove the object from the list | |
| 10:21:30 | bauzas | you somehow need to either pop it from the list, or just delete it by hand | |
| 10:21:37 | auniyal | yes, so the same I was trying to say, so instead of deleted their, we ca have fresh copy | |
| 10:22:12 | auniyal | will it affect performance | |
| 10:22:35 | bauzas | auniyal: sure, I don't disagree, but it's just doing an extra RPC roundtrip for some calculation we already made | |
| 10:23:12 | bauzas | auniyal: if you compare your new bdm list after the cleanup with the old one, you should in theory see that only the destroyed BDMs are left | |
| 10:23:33 | bauzas | auniyal: well, it's optimization | |
| 10:23:53 | bauzas | you know what? I'll switch my vote to +1 and I'll leave others chime in | |