<?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/neutron-lib — Stackers Network</title>
    <link>https://stackers.network/projects/openstack-neutron-lib/</link>
    <atom:link href="https://stackers.network/projects/openstack-neutron-lib/feed.xml" rel="self" type="application/rss+xml"/>
    <language>en</language>
    <lastBuildDate>Sat, 19 Sep 2026 00:00:00 +0000</lastBuildDate>
    <description>Weekly code-activity digest for openstack/neutron-lib from Stackers Network.</description>
    <item>
      <title>openstack/neutron-lib — Week of 2026-09-19</title>
      <link>https://stackers.network/projects/openstack-neutron-lib/2026-09-19</link>
      <guid>https://stackers.network/projects/openstack-neutron-lib/2026-09-19</guid>
      <pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate>
      <description>API definition filtering. The dominant theme was a sweep adding an is_filter marker to attributes across a dozen API definitions: agent, flavors, logging, metering, floatingip-pools, network-ip-availability, qos, auto-allocated-topology, segment, network-segment-range, and all…</description>
      <content:encoded><![CDATA[<p><strong>API definition filtering.</strong> The dominant theme was a sweep adding an <code translate="no">is_filter</code> marker to attributes across a dozen API definitions: <code translate="no">agent</code>, <code translate="no">flavors</code>, <code translate="no">logging</code>, <code translate="no">metering</code>, <code translate="no">floatingip-pools</code>, <code translate="no">network-ip-availability</code>, <code translate="no">qos</code>, <code translate="no">auto-allocated-topology</code>, <code translate="no">segment</code>, <code translate="no">network-segment-range</code>, and all TaaS definitions. Each change landed twice (paired reviews), so the churn is roughly doubled but the surface touched is broad and consistent, making explicit which fields are legal query filters. A companion doc change spells out URL-path hyphen/underscore equivalence.</p>
<p><strong>Extension reverts.</strong> Four extensions were rolled back: the <code translate="no">sfc</code>/<code translate="no">flowclassifier</code> definitions for networking-sfc (~574 lines removed), the <code translate="no">rbac-bgpvpn</code> extension, the "Delete floating IPs on network turned internal" behavior, and the neutron-lib half of "Let Neutron enforce rule on create_subnet with segment_id". Together these strip out roughly 850 lines of previously merged API surface.</p>
<p><strong>Fixes.</strong> <code translate="no">placement</code> now raises <code translate="no">PlacementResourceProviderNotFound</code> on delete, <code translate="no">db.is_retriable()</code> exception handling was corrected, and <code translate="no">api.convert_to_int()</code> now tolerates <code translate="no">None</code> input. Two pylint cleanups also landed, addressing <code translate="no">abstract-method</code> and <code translate="no">attribute-defined-outside-init</code> warnings.</p>]]></content:encoded>
    </item>
  </channel>
</rss>
