| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2025-07-08 | |||
| 09:27:50 | mhen | alright, thanks for confirming | |
| 12:51:48 | opendevreview | Balazs Gibizer proposed openstack/nova master: Reproduce bug/2115905 https://review.opendev.org/c/openstack/nova/+/954336 | |
| 12:51:48 | opendevreview | Balazs Gibizer proposed openstack/nova master: [pci]Keep used dev in Placement regardless of dev_spec https://review.opendev.org/c/openstack/nova/+/954149 | |
| 13:25:51 | sean-k-mooney | gibi: i reviewed the first couple of patches in your eventlet work and im back up to where i left off before (the stats priting one) for the most part they look fine to me | |
| 13:27:16 | sean-k-mooney | i also looked at kamils patch, https://review.opendev.org/c/openstack/nova/+/949754/17 i think ThreadingEventWithResult should just be a future not a event with a result, i woudl be interested to know if you agree but i left that as a comment in gerrit so no rush | |
| 13:56:05 | zigo | I tried using an older version of pymysql (the one in Bookworm), it didn't help. I tried doing a gc.disable() to check if that was another instance of the GC issue in Python 3.13, and it didn't help either. Anyone has an idea of what's going on? | |
| 13:56:05 | zigo | Hi there! I filled-up a new bug: https://bugs.launchpad.net/nova/+bug/2116186 | |
| 13:59:07 | gibi | sean-k-mooney: on the ThreadingEventWithResult: I wanted a solution that changes as minimal in the current flow of the code as possible. Hence the direct replication of the Eventlet.Event behavior with threading.Event + a variable approach. The Future based approach has the drawback in my mind that the concurrent Future interface explicitly says that setting the result of the Future should happen by | |
| 13:59:13 | gibi | the implementation of an Executor. So it seems using a Future in that nova code would create a lot more code churn if it is even possible. | |
| 13:59:50 | sean-k-mooney | am so future are usabel with raw thread | |
| 13:59:58 | sean-k-mooney | so an executor is not stritly required | |
| 14:00:14 | gibi | https://docs.python.org/3/library/concurrent.futures.html#concurrent.futures.Future.set_result | |
| 14:00:33 | gibi | This method should only be used by Executor implementations and unit tests. | |
| 14:01:11 | sean-k-mooney | hum | |
| 14:01:22 | sean-k-mooney | that does not conform to what i would normally consider a future then | |
| 14:02:17 | sean-k-mooney | we would have to use a queue isnterad which is less obvious | |
| 14:03:43 | gibi | we started with a queue actually :) If you look back of previous PSs it is there | |
| 14:04:17 | sean-k-mooney | to me a future is concpetiulaly the same as a a queue of lenth 1 with blocking or non blocking gets dependign on if you pass a timeout to result | |
| 14:04:18 | gibi | then we learned that eventlet.Event has the behavior that it sends the same piece of result to all waiters so a queue with a lenght of 1 is not optimal | |
| 14:04:34 | sean-k-mooney | ah i see | |
| 14:04:40 | gibi | as it requires requeueing the same result :/ | |
| 14:05:02 | sean-k-mooney | well that fan out or multi subsciber behaivor seams non standard too | |
| 14:05:07 | gibi | yep it is not | |
| 14:05:13 | sean-k-mooney | are we actuly reallying on that | |
| 14:05:27 | sean-k-mooney | i think for now im ok with the current approch then | |
| 14:05:34 | gibi | I'm not sure but I'm not willing to risk | |
| 14:05:40 | sean-k-mooney | but we may want to see if we can simplicy in the future | |
| 14:05:50 | gibi | yepp simplifying in the future is the way | |
| 14:06:05 | gibi | first have something that works and then optimize | |
| 14:10:37 | sean-k-mooney | so the asyncio future does nto have that limiation for what its worth | |
| 14:10:39 | sean-k-mooney | https://docs.python.org/3/library/asyncio-future.html#asyncio.Future.set_result | |
| 14:12:47 | sean-k-mooney | i ws not expectign thos to diverge in that regard | |
| 14:16:55 | gibi | yeah it is strange | |
| 14:22:46 | opendevreview | Balazs Gibizer proposed openstack/nova master: Reproduce bug/2115905 https://review.opendev.org/c/openstack/nova/+/954336 | |
| 14:22:47 | opendevreview | Balazs Gibizer proposed openstack/nova master: [pci]Keep used dev in Placement regardless of dev_spec https://review.opendev.org/c/openstack/nova/+/954149 | |
| 14:23:59 | sean-k-mooney | looking at https://peps.python.org/pep-3148/ i think the landed on the current interface by emulating the java and in https://peps.python.org/pep-3156/#futures the intentioally diverged | |
| 14:25:13 | sean-k-mooney | anyway that enough of a distaction | |
| 15:02:09 | Uggla | Nova meeting in ~1h | |
| 15:31:16 | gmaan | Uggla: Due to Board meeting, I might not be able to join today meeting. | |
| 15:31:28 | Uggla | gmaan, ok | |
| 15:31:40 | Uggla | gmaan, thanks for the notification | |
| 15:34:40 | gibi | I know Dan is out this week, so we might have a quick meeting if no quorum is present | |
| 16:00:14 | opendevmeet | The meeting name has been set to 'nova' | |
| 16:00:14 | opendevmeet | Meeting started Tue Jul 8 16:00:14 2025 UTC and is due to finish in 60 minutes. The chair is Uggla. Information about MeetBot at http://wiki.debian.org/MeetBot. | |
| 16:00:14 | opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | |
| 16:00:14 | Uggla | #startmeeting nova | |
| 16:00:24 | Uggla | Hello everyone | |
| 16:01:07 | fwiesel | o/ | |
| 16:01:21 | elodilles | o/ | |
| 16:03:04 | bauzas | o/ | |
| 16:03:14 | Uggla | Let's start slowly so people could join | |
| 16:03:23 | Uggla | #info No Critical bug | |
| 16:03:35 | Uggla | oops | |
| 16:03:37 | Uggla | #topic Bugs (stuck/critical) | |
| 16:03:48 | Uggla | #info No Critical bug | |
| 16:03:57 | Uggla | #topic Gate status | |
| 16:04:04 | Uggla | #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs | |
| 16:04:12 | Uggla | #link https://etherpad.opendev.org/p/nova-ci-failures-minimal | |
| 16:04:21 | Uggla | #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&branch=stable%2F*&branch=master&pipeline=periodic-weekly&skip=0 Nova&Placement periodic jobs status | |
| 16:04:28 | Uggla | #info Please look at the gate failures and file a bug report with the gate-failure tag. | |
| 16:04:35 | Uggla | #info Please try to provide a meaningful comment when you recheck | |
| 16:04:50 | Uggla | #info https://bugs.launchpad.net/nova/+bug/2115980 opened by gibi. It seems nova next has regular failure due to this. | |
| 16:05:17 | Uggla | gibi, do you have more info about ^ | |
| 16:05:53 | clarkb | the underlying issue is that zuul launcher can in some exceptional circumstances assign nodes to multiple providers within the same nodeset. This is due to zuul launcher wanting to be able to support k8s pods and openstack vms in the same nodeset | |
| 16:06:19 | clarkb | unfortauntely there were a few bugs (I think 2 or 3 at this point) that allowed it to mix providers more often than expected. The last of these known bugs was fixed around 2200UTC yseterday | |
| 16:06:35 | gibi | yepp the latest from me is that I'm not seeing the failure today any more | |
| 16:06:41 | clarkb | with each of the bugfixes the occurence of this issue should be lessened. And hopefully if we've fixed the bugs then the issue goes away | |
| 16:07:08 | gibi | I will keep the bug around for couple of days then I will close it if the problem does not re-occure | |
| 16:08:03 | Uggla | thanks clarkb, I appreciate your inputs. | |
| 16:08:33 | Uggla | thanks gibi | |
| 16:08:51 | Uggla | skipping next topic because gmann is not available. | |
| 16:09:08 | Uggla | #topic Release Planning | |
| 16:09:17 | Uggla | #link https://releases.openstack.org/flamingo/schedule.html | |
| 16:09:25 | Uggla | #info Nova deadlines are set in the above schedule | |
| 16:09:50 | Uggla | Spec freeze was last week. So no new specs. | |
| 16:10:15 | Uggla | #topic Review priorities | |
| 16:10:31 | Uggla | #link https://etherpad.opendev.org/p/nova-2025.2-status | |
| 16:12:02 | Uggla | We had a lot of interest just before the spec freeze around io threads. | |
| 16:12:58 | Uggla | Although, the specs were not approved this cycle. We may open a 2026.1 "directory" to keep the momentum around this activity. | |
| 16:13:53 | Uggla | #topic OpenAPI | |
| 16:14:01 | Uggla | #link: https://review.opendev.org/q/topic:%22openapi%22+(project:openstack/nova+OR+project:openstack/placement)+-status:merged+-status:abandoned | |
| 16:14:23 | Uggla | #info 19 remaining. Same as last week. | |
| 16:14:36 | Uggla | #topic Stable Branches | |
| 16:14:51 | Uggla | elodilles, please go ahead. | |
| 16:14:59 | elodilles | i was on vacation last week, so i might missed some stuff | |
| 16:15:04 | elodilles | otherwise, i'm not aware of any issue with stable gates | |
| 16:15:17 | elodilles | so that's all, to be quick o:) | |
| 16:15:25 | elodilles | Uggla: back to you | |
| 16:15:45 | Uggla | thx elodilles | |
| 16:16:00 | Uggla | #topic vmwareapi 3rd-party CI efforts Highlights | |
| 16:16:08 | fwiesel | Hi, no updates from my side. | |
| 16:16:21 | Uggla | fwiesel, thanks. | |
| 16:16:29 | Uggla | #topic Gibi's news about eventlet removal. | |
| 16:16:34 | Uggla | #link Blog: https://gibizer.github.io/categories/eventlet/ | |
| 16:16:42 | Uggla | #link nova-scheduler series is ready for core review, starting at https://review.opendev.org/c/openstack/nova/+/947966 | |
| 16:16:58 | Uggla | gibi, do you want to say something about eventlet removal ? | |
| 16:17:18 | gibi | only that we are slowly landing the approved patches as the gate allows | |
| 16:17:35 | gibi | we have one patch left that is approved but not landed yet | |
| 16:17:43 | gibi | the series is in reviewable state | |
| 16:18:01 | gibi | I'm only tracking minor comment at the moment | |