<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>openstack/trove — Stackers Network</title>
    <link>https://stackers.network/projects/openstack-trove/</link>
    <description>Weekly code-activity digest for openstack/trove from Stackers Network.</description>
    <item>
      <title>openstack/trove — Week of 2026-06-20</title>
      <link>https://stackers.network/projects/openstack-trove/2026-06-20</link>
      <guid>https://stackers.network/projects/openstack-trove/2026-06-20</guid>
      <pubDate>Sat, 20 Jun 2026 00:00:00 +0000</pubDate>
      <description>Guest-agent credential hygiene. The biggest change of the week reworks how the guest agent talks to Swift, switching to a pre-authenticated Swift client and dropping the Keystone re-auth path (986547). A follow-up removes the service credentials from trove-guestagent.conf…</description>
      <content:encoded><![CDATA[<p><strong>Guest-agent credential hygiene.</strong> The biggest change of the week reworks how the guest agent talks to Swift, switching to a pre-authenticated Swift client and dropping the Keystone re-auth path (<a href="https://review.opendev.org/c/openstack/trove/+/986547">986547</a>). A follow-up removes the service credentials from <code translate="no">trove-guestagent.conf</code> entirely, continuing the push to keep long-lived auth material off the guest.</p>
<p><strong>Datastore work.</strong> PostgreSQL gains the previously-missing upgrade implementation, with companion fixes to allow upgrading to the same version and to pass <code translate="no">datastore_version.version</code> rather than the name into the upgrade call (landed twice, once on master and once as a backport). MariaDB 10.4+ official images get a corrected defaults config path.</p>
<p><strong>API and compatibility fixes.</strong> Resize validation now copes with Nova microversion ≥ 2.47, the Cinder client defaults to API v3, and a legacy database migration helper drops the deprecated <code translate="no">.values()[0]</code> pattern in favor of <code translate="no">.scalar()</code>.</p>
<p><strong>CI.</strong> The 2025.1 Ubuntu Jammy jobs are pinned to a compatible tempest tag so they keep running green.</p>]]></content:encoded>
    </item>
    <item>
      <title>openstack/trove — Week of 2026-05-30</title>
      <link>https://stackers.network/projects/openstack-trove/2026-05-30</link>
      <guid>https://stackers.network/projects/openstack-trove/2026-05-30</guid>
      <pubDate>Sat, 30 May 2026 00:00:00 +0000</pubDate>
      <description>PostgreSQL datastore. The headline functional work fills in the missing upgrade implementation for PostgreSQL and adds support for PostgreSQL 18, along with a small change permitting upgrade to the same version. The upgrade plumbing landed on master and was backported…</description>
      <content:encoded><![CDATA[<p><strong>PostgreSQL datastore.</strong> The headline functional work fills in the missing upgrade implementation for PostgreSQL and adds support for PostgreSQL 18, along with a small change permitting upgrade to the same version. The upgrade plumbing landed on master and was backported, consistent with the duplicate change pairs in the merge list.</p>
<p><strong>DevStack and deployment.</strong> The largest single change refreshes the DevStack installation flow and accompanying docs (<a href="https://review.opendev.org/c/openstack/trove/+/979488">979488</a>, ~1,000 lines touched), and is followed by smaller fixes: correct detection of <code translate="no">/dev/kvm</code>, optional QEMU software emulation for environments without KVM, and consolidation onto a shared keystoneauth helper. Zuul job definitions also drop hard-coded version numbers.</p>
<p><strong>Compatibility and stability.</strong> Trove now defaults to Cinder API v3 (landed across three branches) and handles Nova microversion ≥ 2.47 in resize validation. A SQLAlchemy modernization replaces <code translate="no">.values()[0]</code> with <code translate="no">.scalar()</code> in <code translate="no">_migrate_legacy_database</code>, and <code translate="no">hashlib.md5</code> call sites are explicitly marked as non-security — both fanned out as three-branch backports. Preparation for removing eventlet also landed.</p>
<p><strong>Elsewhere.</strong> Documentation picked up an updated support matrix, PDF-build fixes, and a small config-parameter refresh.</p>]]></content:encoded>
    </item>
  </channel>
</rss>
