<?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/designate — Stackers Network</title>
    <link>https://stackers.network/projects/openstack-designate/</link>
    <atom:link href="https://stackers.network/projects/openstack-designate/feed.xml" rel="self" type="application/rss+xml"/>
    <language>en</language>
    <lastBuildDate>Sat, 31 Oct 2026 00:00:00 +0000</lastBuildDate>
    <description>Weekly code-activity digest for openstack/designate from Stackers Network.</description>
    <item>
      <title>openstack/designate — Week of 2026-10-31</title>
      <link>https://stackers.network/projects/openstack-designate/2026-10-31</link>
      <guid>https://stackers.network/projects/openstack-designate/2026-10-31</guid>
      <pubDate>Sat, 31 Oct 2026 00:00:00 +0000</pubDate>
      <description>Security hardening. The bulk of the week was a security-fix push across the API and TSIG surfaces, with each fix landing on master plus two or three stable branches. TSIG key handling gained validation that key scope matches the referenced resource_id. The floating IP PTR API…</description>
      <content:encoded><![CDATA[<p><strong>Security hardening.</strong> The bulk of the week was a security-fix push across the API and TSIG surfaces, with each fix landing on master plus two or three stable branches. TSIG key handling gained validation that key scope matches the referenced <code translate="no">resource_id</code>. The floating IP PTR API picked up a missing authorization check and a separate fix for a <a href="https://review.opendev.org/c/openstack/designate/+/1012280">cross-tenant zone hijack</a>. The Infoblox backend saw PQC compliance gaps closed alongside a TSIG warning cleanup.</p>
<p><strong>Catalog zones and pools.</strong> Pool management got two notable corrections: nameserver updates now behave correctly when the pool has a catalog zone, and <code translate="no">pool_move_zone</code> now properly bumps catalog zone serials. Related zone-building work makes the lowest-priority <code translate="no">ns_record</code> the SOA MNAME and ensures <code translate="no">Zone.refresh</code> is populated when constructing from a dnspython zone.</p>
<p><strong>API and storage fixes.</strong> Pagination on the <code translate="no">service_statuses</code> endpoint was repaired, a MySQL migration was tweaked for ProxySQL compatibility, and a client attribute is now initialized up front to prevent an <code translate="no">AttributeError</code>.</p>
<p><strong>Tooling.</strong> DevStack dropped <code translate="no">mod_wsgi</code> deployment support and a redundant <code translate="no">install_apache_uwsgi</code> call, and the Xena upgrade script was removed.</p>]]></content:encoded>
    </item>
    <item>
      <title>openstack/designate — Week of 2026-10-24</title>
      <link>https://stackers.network/projects/openstack-designate/2026-10-24</link>
      <guid>https://stackers.network/projects/openstack-designate/2026-10-24</guid>
      <pubDate>Sat, 24 Oct 2026 00:00:00 +0000</pubDate>
      <description>Floating IP PTR security. Two authz holes in the floating IP PTR API were closed: a missing authorization check and a cross-tenant zone hijack. Both landed on master without visible backports in this window. Catalog zone handling. Pool management grew more robust around catalog…</description>
      <content:encoded><![CDATA[<p><strong>Floating IP PTR security.</strong> Two authz holes in the floating IP PTR API were closed: a missing authorization check and a cross-tenant zone hijack. Both landed on master without visible backports in this window.</p>
<p><strong>Catalog zone handling.</strong> Pool management grew more robust around catalog zones, with a ~210-line fix for nameserver updates when a pool hosts a catalog zone (<a href="https://review.opendev.org/c/openstack/designate/+/1010386">1010386</a>) and a companion fix for pool deletion in the same situation. The delete fix was fanned out as four parallel backports across stable branches.</p>
<p><strong>Record and resolver correctness.</strong> The CAA record <code translate="no">flags</code> field was widened to cover the full RFC 6844 range, shipped once on master and backported to four stable branches. Separately, zone deletion no longer fails when BIND has recursion enabled.</p>
<p><strong>Stability.</strong> The coordination driver now stops safely when it was never initialized, with the fix mirrored to four stable branches.</p>
<p>Activity this week was entirely bugfix and backport work from a single contributor, with roughly two-thirds of the churn concentrated in the catalog-zone and CAA fixes and their stable-branch propagation.</p>]]></content:encoded>
    </item>
    <item>
      <title>openstack/designate — Week of 2026-10-17</title>
      <link>https://stackers.network/projects/openstack-designate/2026-10-17</link>
      <guid>https://stackers.network/projects/openstack-designate/2026-10-17</guid>
      <pubDate>Sat, 17 Oct 2026 00:00:00 +0000</pubDate>
      <description>Stability. The week was almost entirely bug-fix traffic, with each fix landing on master plus three stable branches. Notification handlers got corrected IPv6 address parsing (~440 lines across four branches), and the BIND backend got a fix for zone deletion failing when…</description>
      <content:encoded><![CDATA[<p><strong>Stability.</strong> The week was almost entirely bug-fix traffic, with each fix landing on master plus three stable branches. Notification handlers got corrected IPv6 address parsing (~440 lines across four branches), and the BIND backend got a fix for <a href="https://review.opendev.org/c/openstack/designate/+/1009178">zone deletion failing when recursion is enabled</a>. A separate correctness fix stops the zone serial from being incremented on description-only updates, where the DNS payload hasn't actually changed — that one also rode the full set of backports.</p>
<p><strong>Races and tests.</strong> A smaller fix addresses a timer-restart race in <code translate="no">HeartbeatEmitter.stop()</code>, closing a window where the heartbeat could resurrect itself during shutdown. On the test side, the zone import tests were adjusted to send raw zone files rather than pre-parsed payloads, and that change was likewise fanned out across stable branches.</p>
<p><strong>Elsewhere.</strong> No feature work, API changes, or driver additions merged this week — the full 1,123 lines of churn are backport-heavy maintenance, with roughly four fixes multiplied across master and three maintained releases.</p>]]></content:encoded>
    </item>
    <item>
      <title>openstack/designate — Week of 2026-09-26</title>
      <link>https://stackers.network/projects/openstack-designate/2026-09-26</link>
      <guid>https://stackers.network/projects/openstack-designate/2026-09-26</guid>
      <pubDate>Sat, 26 Sep 2026 00:00:00 +0000</pubDate>
      <description>API service cleanup. The standalone designate-api command and its WSGIService wrapper were removed, cutting ~430 lines and pushing deployments toward the WSGI-application entry point; a companion change makes the API service tests skip cleanly once oslo.service WSGI support…</description>
      <content:encoded><![CDATA[<p><strong>API service cleanup.</strong> The standalone <code translate="no">designate-api</code> command and its <code translate="no">WSGIService</code> wrapper were removed, cutting ~430 lines and pushing deployments toward the WSGI-application entry point; a companion change makes the API service tests skip cleanly once <code translate="no">oslo.service</code> WSGI support disappears. On the management side, <code translate="no">designate-manage pool update</code> gained a <code translate="no">--replace</code> flag (<a href="https://review.opendev.org/c/openstack/designate/+/976247">976247</a>) to overwrite pool state rather than merge it.</p>
<p><strong>Bug fixes.</strong> Zone deletion no longer fails when BIND is configured with recursion enabled, and a zone's serial now increments correctly on description-only updates. The CAA record type accepts the full RFC 6844 flags range, pool deletion succeeds when the pool contains a catalog zone, and the pool-validation error surfaced during zone creation is clearer. The TLD list API picked up a <code translate="no">description</code> filter, and a coordination-driver shutdown path is now safe when the driver was never initialized.</p>
<p><strong>Docs and housekeeping.</strong> A batch of documentation work landed: obsolete 2015–2017 upgrade guides were dropped, zone-import API docs corrected, AppArmor setup for BIND9 <code translate="no">rndc.key</code> documented, Neutron DNS extension availability clarified, and stray auth headers removed from admin-only endpoints. Grenade jobs got an extended <code translate="no">irrelevant-files</code> list, and a translations import from Zanata rounded out the week.</p>]]></content:encoded>
    </item>
  </channel>
</rss>
