<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://gibizer.github.io/</id><title>gibi's blog</title><subtitle>...</subtitle> <updated>2026-06-21T21:24:02+02:00</updated> <author> <name>Balazs Gibizer</name> <uri>https://gibizer.github.io/</uri> </author><link rel="self" type="application/atom+xml" href="https://gibizer.github.io/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://gibizer.github.io/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 Balazs Gibizer </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>We Need Bigger Machines</title><link href="https://gibizer.github.io/posts/We-Need-Bigger-Machines/" rel="alternate" type="text/html" title="We Need Bigger Machines" /><published>2026-06-21T17:45:00+02:00</published> <updated>2026-06-21T17:45:00+02:00</updated> <id>https://gibizer.github.io/posts/We-Need-Bigger-Machines/</id> <content type="text/html" src="https://gibizer.github.io/posts/We-Need-Bigger-Machines/" /> <author> <name>Balazs Gibizer</name> </author> <category term="AI" /> <category term="code-review" /> <summary>After 20 years, I re-read The Hitchhiker’s Guide to the Galaxy books. It was cozy and nostalgic, exactly what I expected. Then, weeks later, one morning my overslept brain made a surprising association. “All right,” said Deep Thought. “The Answer to the Great Question…” “Yes…!” “Of Life, the Universe and Everything…” said Deep Thought. “Yes…!” “Is…” said Deep Thought, and paused. “Yes…!” “I...</summary> </entry> <entry><title>The Bottleneck Is Us</title><link href="https://gibizer.github.io/posts/The-Bottleneck-Is-Us/" rel="alternate" type="text/html" title="The Bottleneck Is Us" /><published>2026-04-12T19:45:00+02:00</published> <updated>2026-04-12T19:45:00+02:00</updated> <id>https://gibizer.github.io/posts/The-Bottleneck-Is-Us/</id> <content type="text/html" src="https://gibizer.github.io/posts/The-Bottleneck-Is-Us/" /> <author> <name>Balazs Gibizer</name> </author> <category term="AI" /> <category term="code-review" /> <summary>Coincidentally, I wrote a post about AI Code Review a year ago. Many things changed since then out there about technology, about the shape of the hype, but also many things changed around me and in me. I expect this trend will continue in hard to predict ways, so here in this post I don’t want to focus on what changed, but rather try to use the noise of those changes to look at what stayed the ...</summary> </entry> <entry><title>Eventlet removal - Gazpacho status</title><link href="https://gibizer.github.io/posts/Eventlet-Removal-Gazpacho/" rel="alternate" type="text/html" title="Eventlet removal - Gazpacho status" /><published>2026-03-22T06:30:00+01:00</published> <updated>2026-03-22T06:30:00+01:00</updated> <id>https://gibizer.github.io/posts/Eventlet-Removal-Gazpacho/</id> <content type="text/html" src="https://gibizer.github.io/posts/Eventlet-Removal-Gazpacho/" /> <author> <name>Balazs Gibizer</name> </author> <category term="OpenStack" /> <category term="Eventlet" /> <summary>Bah, it’s been a long time. I published my last update 10 months ago. I’m sorry. It was not the plan. But like any real plan, mine also died soon after meeting the enemy. Time. Due to the size of the time gap to cover, I won’t try to make this a chronological update, but rather a status report focusing on where we are at the end of the Gazpacho release. Then, I will tell some selected stories ...</summary> </entry> <entry><title>Eventlet removal - The first threading bug</title><link href="https://gibizer.github.io/posts/Eventlet-Removal-The-First-Threading-Bug/" rel="alternate" type="text/html" title="Eventlet removal - The first threading bug" /><published>2025-05-10T18:45:00+02:00</published> <updated>2025-05-10T18:45:00+02:00</updated> <id>https://gibizer.github.io/posts/Eventlet-Removal-The-First-Threading-Bug/</id> <content type="text/html" src="https://gibizer.github.io/posts/Eventlet-Removal-The-First-Threading-Bug/" /> <author> <name>Balazs Gibizer</name> </author> <category term="OpenStack" /> <category term="Eventlet" /> <summary>A bit more than a week passed since the last Eventlet removal post. So it was time to summarize what happened and draw up some plans for the next week. We have 20 weeks left from the Flamingo cycle, and we have 258 references to Eventlet in the Nova git repo. xychart-beta title "Eventlet references and in-flight removals in the Nova repo" x-axis "Weeks left from Flamingo" ["Epoxy",...</summary> </entry> <entry><title>Eventlet removal - Scheduler first run</title><link href="https://gibizer.github.io/posts/Eventlet-Removal-Scheduler-First-Run/" rel="alternate" type="text/html" title="Eventlet removal - Scheduler first run" /><published>2025-04-30T15:00:00+02:00</published> <updated>2025-04-30T15:00:00+02:00</updated> <id>https://gibizer.github.io/posts/Eventlet-Removal-Scheduler-First-Run/</id> <content type="text/html" src="https://gibizer.github.io/posts/Eventlet-Removal-Scheduler-First-Run/" /> <author> <name>Balazs Gibizer</name> </author> <category term="OpenStack" /> <category term="Eventlet" /> <summary>This is a mid-week update on the Eventlet removal work as we hit a milestone. We had a first green tempest run with nova-scheduler running in native threaded mode. You can browse the rest of the blog series here. What happened Pulling in multiple hacks we had the first CI run where the nova-scheduler ran in native threading mode and multiple tempest jobs (e.g. nova-next, nova-multi-cell) suc...</summary> </entry> </feed>
