January 2026 - openstack-discuss - lists.openstack.org

[ops][cinder][show-and-tell] I wrote an open-source tool to automate OpenStack Cinder snapshot lifecycles
by aravindhstanley＠gmail.com 05 Jan '26

05 Jan '26

Hello folks, We have been using OpenStack for a while and needed a reliable way to keep snapshots on hot storage for compliance and quick recovery. While Cinder provides the mechanism to create snapshots, the actual scheduling and rotation are largely left for the operator to figure out. I know there are robust commercial tools like Trilio (awesome tool, by the way), but I wanted a lightweight, open-source alternative to manage the snapshot lifecycle without the extra overhead. So, I built SnapSentry. It is written in Go, completely free, and MIT licensed, so I thought I should share it with the community. Key Features: Metadata-Driven: No central database or config files; just tag your volumes with metadata and it works. (Helper command takes care of metadata updates) Atomic-ish VM Snapshots: Automatically identifies all volumes attached to a specific VM and snapshots them in parallel to minimize consistency gaps. Smart Concurrency: Uses a hybrid model (Parallel for attached volumes, Sequential for unattached) to prevent API throttling. Resilient: Handles transient OpenStack errors (500s) and cleans up orphaned "zombie" snapshots automatically. Secure: Supports restricted Application Credentials for least-privilege operation. Here is the repo: https://github.com/aravindh-murugesan/openstack-snapsentry-go Cheers, and feedback is welcome! Note: I do use AI assistant for docs, but the logic or the app itself is not vibe-coded. I'm not sure if this is the right place to post this, if it's not, I apologize. Just trying to contribute to the openstack ecosystem :)

2 1

[tacker] Cancelling weekly IRC meeting
by Yasufumi Ogawa 05 Jan '26

05 Jan '26

Hi team, Sorry for the late notice. I'd like to cancel the IRC meeting today as we agreed in the previous meeting. Regards, Yasufumi

1 0

[Opensource Tool] Cinder snapshot lifecycle management
by Aravindh M 03 Jan '26

03 Jan '26

Hello folks, We have been using OpenStack for a while and needed a reliable way to keep snapshots on hot storage for compliance and quick recovery. While Cinder provides the mechanism to create snapshots, the actual scheduling and rotation are largely left for the operator to figure out. I know there are robust commercial tools like Trilio (awesome tool, by the way), but I wanted a lightweight, open-source alternative to manage the snapshot lifecycle without the extra overhead. So, I built *SnapSentry*. It is written in Go, completely free, and MIT licensed, so I thought I should share it with the community. *Key Features:* - *Metadata-Driven:* No central database or config files; just tag your volumes with metadata and it works. (Helper command takes care of metadata updates) - *Atomic-ish VM Snapshots:* Automatically identifies all volumes attached to a specific VM and snapshots them in parallel to minimize consistency gaps. - *Smart Concurrency:* Uses a hybrid model (Parallel for attached volumes, Sequential for unattached) to prevent API throttling. - *Resilient:* Handles transient OpenStack errors (500s) and cleans up orphaned "zombie" snapshots automatically. - *Secure:* Supports restricted Application Credentials for least-privilege operation. Here is the repo: https://github.com/aravindh-murugesan/openstack-snapsentry-go Cheers, and feedback is welcome! Note: I do use AI assistant for docs, but the logic or the app itself is not vibe-coded. I'm not sure if this is the right place to post this, if it's not, I apologize. Just trying to contribute to the openstack ecosystem :)

1 0

[neutron] bug deputy report for week of 2025-12-15
by Bence Romsics 02 Jan '26

02 Jan '26

Hi Team, Here's the deputy report for the week of 2025-12-15. Sorry for being so slow! High: * https://bugs.launchpad.net/neutron/+bug/2136827 Functional tests using SqlFixture are extremely slow fix in progress: https://review.opendev.org/c/openstack/neutron/+/971472 * https://bugs.launchpad.net/neutron/+bug/2136733 The highest priority chassis gateway port fails to bind after chassis was restarted/crashed wip fix: https://review.opendev.org/c/openstack/neutron/+/971876 Medium: * https://bugs.launchpad.net/neutron/+bug/2136747 [FT] "ResourceWarning: unclosed file" errors in the FT execution unassigned, but Jakub investigated a bit * https://bugs.launchpad.net/neutron/+bug/2136147 test_two_vms_fips test has very specific expectations from availability zones fix in progress: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/970865 * https://bugs.launchpad.net/neutron/+bug/2136864 [ovn-db-sync] sync_hostname_and_physical_networks is expecting to find Chassis among agents fix in progress: https://review.opendev.org/c/openstack/neutron/+/971527 Incomplete: * https://bugs.launchpad.net/neutron/+bug/2136466 [rbac] Unexpected behaviour on floating ip port forwarding list Regards, Bence

1 0