<?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-tempest-plugin — Stackers Network</title>
    <link>https://stackers.network/projects/openstack-neutron-tempest-plugin/</link>
    <atom:link href="https://stackers.network/projects/openstack-neutron-tempest-plugin/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/neutron-tempest-plugin from Stackers Network.</description>
    <item>
      <title>openstack/neutron-tempest-plugin — Week of 2026-09-12</title>
      <link>https://stackers.network/projects/openstack-neutron-tempest-plugin/2026-09-12</link>
      <guid>https://stackers.network/projects/openstack-neutron-tempest-plugin/2026-09-12</guid>
      <pubDate>Sat, 12 Sep 2026 00:00:00 +0000</pubDate>
      <description>Test coverage expansion. The largest addition is a substantial new suite of Tap-as-a-Service scenarios (~1,100 lines touched) that broadens TaaS coverage well beyond the existing cases. Alongside it, EVPN gains two significant pieces: dynamic VNI provisioning for EVPN tests and…</description>
      <content:encoded><![CDATA[<p><strong>Test coverage expansion.</strong> The largest addition is a substantial new suite of Tap-as-a-Service scenarios (~1,100 lines touched) that broadens TaaS coverage well beyond the existing cases. Alongside it, EVPN gains two significant pieces: dynamic VNI provisioning for EVPN tests and a new advanced server operations suite exercising EVPN networks end to end. See <a href="https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/998604">the dynamic VNI change</a> for the provisioning bits that unblock those flows.</p>
<p><strong>API surface.</strong> The indirect Floating IPs API extension picks up both a scenario test and a dedicated negative API test module, and the <code translate="no">ovn_router_indirect_snat</code> toggle is switched back on in the OVN job so the extension is actually exercised there. PVLAN negative API tests are also un-skipped now that the upstream BadRequest handling is fixed.</p>
<p><strong>FWaaS and VPNaaS cleanup.</strong> The FWaaS scenarios are rebased onto the shared Neutron Tempest plugin test bases (net removal of ~130 lines) and gain firewall-group cleanup on scenario failure. VPNaaS scenarios move to unique per-class CIDRs to stop tests colliding on address space.</p>
<p><strong>Tooling.</strong> An experimental <code translate="no">neutron-ovn-evpn-tempest-multinode</code> job lands to support EVPN development.</p>]]></content:encoded>
    </item>
  </channel>
</rss>
