Skip to content

Releases: simplyblock/sbcli

26.2-PRE

30 Apr 12:44

Choose a tag to compare

Release Notes:

  • Full FTT2 support: We support now three instead of two paths from the initiator (NVMe-oF) volume to the targets. There is a primary, secondary and now also tertiary target with identical subsystems able to process IO. This allows the loss or maintainance of any two nodes in the cluster, regardless of the combination, at a point in time.
  • Support for NVMe-oF-dhchap: dhchap can now be configured on pool-level; allowed host NQNs need to managed on the pool; the autentication used is bi-directional. Encryption is based on FIPS-140-3 certified library.
    Support for TLS in Openshift: All management communication within the simplyblock cluster and to the cluster endpoints uses encryption with Openshift-managed certificates.
  • Image upgrade and CVE clean-up: Images have been upgraded to python 3.12 and RHEL10 and cleared from any CVEs.
  • Volume Backup/Restore: Mechanisms to take backups of snapshots and snapshot-chains to an S3-compatible storage; We support backup retention and merge policies and auto-backup schedules on the operator. Snapshots can be restored into volumes (PVCs) on the same cluster or into a different cluster. Backup is storage-efficient (delta-only, compressed).
  • Remote Snapshot Replication: Snapshots can be asynchronously replicated btw. nodes and sites in a network-efficient manner.
  • Asynchronous Replication: Support for automatically failing-over and failing-back of selected volumes across sites with a certain time-gap/backlog (e.g. 5 minutes). This is useful for slow links and provides significantly better RTO (zero) and RPO (minimum: 1 minute) than traditional backups.
  • Namespace Volumes: In k8s, we auto-create subystems and namespaces within those subsystems automatically in a pre-defined ratio (e.g. 8 or 16 namespaces per subsystem). The user only has to set the ratio.
  • Multipathing-Support: We support now multipathing within the cluster and from initiators (clients) to the same node in the cluster. This means that clients can have four (FTT=1) or six (FTT=2) connections, two to each node, via separate VLANs using separate networking paths. This feature is also used for all cluster-internal communications. It has advantages over bond and MLAG.

26.1.2

31 Mar 15:13

Choose a tag to compare

What's Changed

Full Changelog: 26.1.1...26.1.2

26.1.1

22 Mar 19:50

Choose a tag to compare

R25.10-Hotfix: pin 26.1.1 and fix clone path regression.

25.10.5

28 Feb 11:11

Choose a tag to compare

What's Changed

Full Changelog: 25.10.3...25.10.5

25.10.4.2

19 Jan 13:12

Choose a tag to compare

25.10.4.1

16 Jan 17:21

Choose a tag to compare

What's Changed

Full Changelog: 25.10.3...25.10.4.1

25.10.4

25 Nov 12:37

Choose a tag to compare

What's Changed

Full Changelog: 25.10.3...25.10.4

25.10.3

13 Nov 18:27

Choose a tag to compare

What's Changed

  • 🐛 Optimise Storage node monitor
  • 🐛 Fix fdb value exceed limit
  • 🐛 Other miner bug fixes, see more in the Full Changelog

Full Changelog: 25.10.2...25.10.3

25.10.2

05 Nov 11:21

Choose a tag to compare

New Features

  • Control Plane: Can alternatively deploy into existing Kubernetes clusters and co-locate on workers with storage nodes.
  • Kubernetes Support Matrix: Added OpenShift starting from version XX.XX.
  • OpenStack Driver: Now available. Supports most optional features and tested from OpenStack 25.1 (Epoxy). (Older OpenStack versions may be supported on request.)
  • Lower Memory Footprint: Required memory on storage nodes reduced from 0.2% of storage capacity to 0.05%.
  • QoS (Pool-level): Added pool-level QoS controls.
  • QoS Service Classes: Assign a service class to a volume; service classes provide full performance isolation within the cluster.
  • Flexible Erasure Coding: Support for flexible erasure-coding schemas within a cluster.
  • Fabrics: Support for RDMA fabric and mixed fabrics (RDMA, TCP).
  • Write Performance: Improvements during first write to volume and during node outage.
  • Namespace Volumes: A single NVMe-oF subsystem can now expose up to 32 namespace volumes.

Fixes

  • Control Plane: Fixed an issue that could lead to stuck deletes.

Upgrade Considerations

  • Upgrades are supported from 25.7.6 and 25.7.7.
  • It’s possible to add RDMA support to the fabric during an online upgrade.

Known Issues

  • Using different erasure-coding schemas per cluster is available but experimental (not GA) and, in some tests, can cause I/O interrupt issues.

25.7.7

17 Sep 11:34

Choose a tag to compare

What's changed:

  • 🐛 Bug fix: QOS setting between lvol and pool must be consistent and not accept negative values
  • 🐛 Bug fix: On bare metal, node auto restart was not triggered after container crash but node is made online
  • 🐛 Bug fix: Crypto LVOL delete: first delete crypto, then Lvol

Full Changelog: 25.7.6...25.7.7