<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>openstack/octavia — Stackers Network</title>
    <link>https://stackers.network/projects/openstack-octavia/</link>
    <atom:link href="https://stackers.network/projects/openstack-octavia/feed.xml" rel="self" type="application/rss+xml"/>
    <language>en</language>
    <lastBuildDate>Sat, 12 Sep 2026 00:00:00 +0000</lastBuildDate>
    <description>Weekly code-activity digest for openstack/octavia from Stackers Network.</description>
    <item>
      <title>openstack/octavia — Week of 2026-09-12</title>
      <link>https://stackers.network/projects/openstack-octavia/2026-09-12</link>
      <guid>https://stackers.network/projects/openstack-octavia/2026-09-12</guid>
      <pubDate>Sat, 12 Sep 2026 00:00:00 +0000</pubDate>
      <description>TLS configuration. The largest change of the week reworks cipher handling so that TLSv1.3 is configured correctly on listeners, a ~300-line fix across the amphora TLS path (review.opendev.org/c/openstack/octavia/+/919846). Complementing it, the deprecated ssl_version option is…</description>
      <content:encoded><![CDATA[<p><strong>TLS configuration.</strong> The largest change of the week reworks cipher handling so that TLSv1.3 is configured correctly on listeners, a ~300-line fix across the amphora TLS path (<a href="https://review.opendev.org/c/openstack/octavia/+/919846">review.opendev.org/c/openstack/octavia/+/919846</a>). Complementing it, the deprecated <code translate="no">ssl_version</code> option is replaced with <code translate="no">ssl_minimum_version</code>, aligning Octavia with the modern SSL context API.</p>
<p><strong>Bug fixes.</strong> Two data-path issues landed: neutron client sockets were being leaked and are now released explicitly, and members were being plugged onto the wrong subnet in certain topologies. Both are small, targeted patches against long-standing behavior.</p>
<p><strong>Maintenance.</strong> The legacy Upstart init configuration was removed outright (-169 lines), retiring support for a boot system Octavia no longer needs to carry. A typo fix rounds out the cleanup.</p>
<p><strong>Tooling and CI.</strong> Most of the remaining activity is CI plumbing: three patches repair mirror usage on stable branches, <code translate="no">DIB_PIP_RETRIES=0</code> is dropped when the CI mirror is in use, and the grenade skip-level job is disabled for the 2026.2 cycle.</p>]]></content:encoded>
    </item>
    <item>
      <title>openstack/octavia — Week of 2026-08-29</title>
      <link>https://stackers.network/projects/openstack-octavia/2026-08-29</link>
      <guid>https://stackers.network/projects/openstack-octavia/2026-08-29</guid>
      <pubDate>Sat, 29 Aug 2026 00:00:00 +0000</pubDate>
      <description>Security hardening. The dominant work this cycle was closing HAProxy config-injection vectors, with fixes landed for both the tls_ciphers field and L7 policy redirect URLs, each backported across three branches. A separate ~850-line change tightens amphora firewalling so VRRP…</description>
      <content:encoded><![CDATA[<p><strong>Security hardening.</strong> The dominant work this cycle was closing HAProxy config-injection vectors, with fixes landed for both the <code translate="no">tls_ciphers</code> field and L7 policy redirect URLs, each backported across three branches. A separate ~850-line change tightens amphora firewalling so VRRP and HAProxy peer ports are no longer open to 0.0.0.0/0 (<a href="https://review.opendev.org/c/openstack/octavia/+/971408">review.opendev.org/c/openstack/octavia/+/971408</a>). A trio of backports also corrects HAProxy configuration when <code translate="no">cpu-map</code> is combined with <code translate="no">external-check</code>.</p>
<p><strong>Amphora reliability.</strong> A VRRP split-brain during failover in ACTIVE_STANDBY topologies was fixed, and amphora certificate generation now derives the AKI from the issuer's SKI rather than recomputing it. On the datapath side, interface allocation to the network namespace on reboot was corrected so amphorae come back up cleanly.</p>
<p><strong>Tooling.</strong> Amphora image build jobs were switched to CI mirrors, and a devstack <code translate="no">unstack</code> failure when Redis/Valkey isn't installed was fixed.</p>]]></content:encoded>
    </item>
    <item>
      <title>openstack/octavia — Week of 2026-08-01</title>
      <link>https://stackers.network/projects/openstack-octavia/2026-08-01</link>
      <guid>https://stackers.network/projects/openstack-octavia/2026-08-01</guid>
      <pubDate>Sat, 01 Aug 2026 00:00:00 +0000</pubDate>
      <description>Taskflow and worker reliability. The largest change rewrites the ZookeeperTaskFlowDriver to eliminate session churn (993556, ~294 lines), and the worker now honors the configured retry count for taskflow persistence instead of hardcoded values. Sensitive keys are masked in…</description>
      <content:encoded><![CDATA[<p><strong>Taskflow and worker reliability.</strong> The largest change rewrites the <code translate="no">ZookeeperTaskFlowDriver</code> to eliminate session churn (<a href="https://review.opendev.org/c/openstack/octavia/+/993556">993556</a>, ~294 lines), and the worker now honors the configured retry count for taskflow persistence instead of hardcoded values. Sensitive keys are masked in taskflow logging so credentials no longer leak through job state, and the <code translate="no">AbstractNetworkDriver.update_vip</code> signature is aligned across implementations.</p>
<p><strong>Python 3.14 readiness.</strong> Two changes overhaul multiprocessing usage — one for octavia-worker specifically and a broader fix across the codebase — to work under 3.14's stricter defaults. Hacking and pyupgrade were bumped in step to keep linting green on the new interpreter.</p>
<p><strong>Image and platform surface.</strong> ARM64 is now an accepted architecture for amphora image builds, expanding the set of hosts that can produce official images.</p>
<p><strong>Cleanup and CI.</strong> The unused <code translate="no">[DEFAULT] octavia_plugins</code> option was dropped, along with a stray devstack token, a redundant Pygments dep, and an explicit <code translate="no">None</code> choice on a config option. On the CI side, the failing centos-9-stream job was removed and periodic FIPS jobs on stable branches were disabled.</p>]]></content:encoded>
    </item>
  </channel>
</rss>
