<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>openstack/kayobe — Stackers Network</title>
    <link>https://stackers.network/projects/openstack-kayobe/</link>
    <description>Weekly code-activity digest for openstack/kayobe from Stackers Network.</description>
    <item>
      <title>openstack/kayobe — Week of 2026-06-06</title>
      <link>https://stackers.network/projects/openstack-kayobe/2026-06-06</link>
      <guid>https://stackers.network/projects/openstack-kayobe/2026-06-06</guid>
      <pubDate>Sat, 06 Jun 2026 00:00:00 +0000</pubDate>
      <description>Agent context. The week's headline is a ~750-line addition providing context for agents, landing a substantial new body of documentation/configuration material in the repository (983903). Alongside this, baremetal registration was switched to a per-host XDG cache, avoiding…</description>
      <content:encoded><![CDATA[<p><strong>Agent context.</strong> The week's headline is a ~750-line addition providing context for agents, landing a substantial new body of documentation/configuration material in the repository (<a href="https://review.opendev.org/c/openstack/kayobe/+/983903">983903</a>). Alongside this, baremetal registration was switched to a per-host XDG cache, avoiding cross-host interference when the workflow runs concurrently.</p>
<p><strong>Custom configuration surface.</strong> Support for custom Watcher configuration files landed on two branches, extending the existing pattern of per-service config overrides to the infrastructure-optimization service. On the cleanup side, support for the deprecated networking-infoblox plugin was dropped.</p>
<p><strong>Stability and CI.</strong> A pair of fixes corrected the naming of custom container variables, addressing a regression in how operators inject container-level overrides. CI jobs were moved off Docker Hub-hosted images on two branches to dodge rate-limit and availability issues, <code translate="no">which</code> was replaced with the more portable <code translate="no">command</code> builtin in shell paths, and <code translate="no">previous_release</code> was set to 2026.2 Hibiscus for upgrade testing.</p>]]></content:encoded>
    </item>
    <item>
      <title>openstack/kayobe — Week of 2026-05-30</title>
      <link>https://stackers.network/projects/openstack-kayobe/2026-05-30</link>
      <guid>https://stackers.network/projects/openstack-kayobe/2026-05-30</guid>
      <pubDate>Sat, 30 May 2026 00:00:00 +0000</pubDate>
      <description>nmstate networking engine. The headline addition is a new nmstate engine for host network configuration, landing across master and the new stable branch at roughly 2,400 lines apiece (990265). It arrives with VLAN QoS map support and a follow-up that trims low-signal…</description>
      <content:encoded><![CDATA[<p><strong>nmstate networking engine.</strong> The headline addition is a new nmstate engine for host network configuration, landing across master and the new stable branch at roughly 2,400 lines apiece (<a href="https://review.opendev.org/c/openstack/kayobe/+/990265">990265</a>). It arrives with VLAN QoS map support and a follow-up that trims low-signal permutations from the nmstate unit tests, alongside release-note tweaks. Each of the four nmstate patches was mirrored to both branches, accounting for the bulk of the week's ~6,000-line churn.</p>
<p><strong>Bug fixes.</strong> Several real-world breakages were addressed: <code translate="no">systemd-networkd-wait-online</code> now copes with interfaces that have no IP, lookup plugins work correctly for external playbooks, the <code translate="no">ansible-collection-kolla</code> install path was repaired (landed on three branches), sensitive inspector rules are hidden from Ansible output, and a <code translate="no">known_hosts</code> module issue on Rocky Linux 9.8 was patched. The <code translate="no">stackhpc.openstack</code> collection was bumped to 0.10.1.</p>
<p><strong>Release branching.</strong> Master was opened for the stable/2026.1 cycle via <code translate="no">.gitreview</code> and version updates, though the "Use OpenStack 2026.1 release" change was reverted on master. Docs gained a kolla-playbook usage page on both branches.</p>
<p><strong>Elsewhere.</strong> CI dropped SLURP jobs on master, disabled <code translate="no">openstack-tox-py310</code>, and replaced a deprecated yaml callback plugin.</p>]]></content:encoded>
    </item>
    <item>
      <title>openstack/kayobe — Week of 2026-05-23</title>
      <link>https://stackers.network/projects/openstack-kayobe/2026-05-23</link>
      <guid>https://stackers.network/projects/openstack-kayobe/2026-05-23</guid>
      <pubDate>Sat, 23 May 2026 00:00:00 +0000</pubDate>
      <description>Container coverage. The headline change broadens what Kayobe actually deploys, wiring up a substantial set of additional containers so operators get more of the Kolla catalog out of the box rather than bolting it on by hand (review.opendev.org/c/openstack/kayobe/+/922402)…</description>
      <content:encoded><![CDATA[<p><strong>Container coverage.</strong> The headline change broadens what Kayobe actually deploys, wiring up a substantial set of additional containers so operators get more of the Kolla catalog out of the box rather than bolting it on by hand (<a href="https://review.opendev.org/c/openstack/kayobe/+/922402">review.opendev.org/c/openstack/kayobe/+/922402</a>). Alongside it, support landed for custom Watcher configuration files, a new <code translate="no">os_family</code> variable to simplify cross-distro role logic, and an option to bind the inspection store to the internal network rather than exposing it on the public side.</p>
<p><strong>2026.1 release prep.</strong> Kayobe was cut over to the OpenStack 2026.1 release and resynced with Kolla Ansible for the same cycle, with a parallel bump of pinned Ansible collections and roles. IPA documentation was reconciled with the defaults the role has actually been shipping.</p>
<p><strong>Stability.</strong> A real fix landed for the network connectivity check on modern Ansible, the trust-store playbook stopped gathering facts unnecessarily, <code translate="no">kolla_ansible_host_vars</code> fact caching was removed, the missing <code translate="no">ansible-collection-kolla</code> install path was repaired, and the deprecated <code translate="no">ansible_managed</code> variable was retired. Baremetal node create arguments are now properly quoted.</p>
<p><strong>Tooling and CI.</strong> Five backports excluding docker-ce 29.5.1 on CentOS/Rocky were merged and then promptly reverted across branches once upstream cleared, repos moved to baseurl, and the deprecated <code translate="no">cp -n</code> flag was dropped from CI scripts.</p>]]></content:encoded>
    </item>
  </channel>
</rss>
