Releases: simplyblock/sbcli
Releases · simplyblock/sbcli
Release list
26.2.8-PRE
- feat: quorum-based device exclusion on repeated remote IO errors + latency-deviation warning
- Cluster activation bug fix
- Bug fixes and security enhancements
26.2.7-PRE
What's Changed
- Increase QPAIR_COUNT from 32 to 64 for enhanced performance
- Fix FoundationDB server definitions with updated volume mappings
Full Changelog: 26.2.6-PRE...26.2.7-PRE
26.2.6-PRE
What's Changed
- Fix security scan CVEs
- Hugepages: preserve user's pre-existing reservation per NUMA node
- Add-node: add --spdk-sys-mem option to override minimum system memory
- Improve LVol cloning speed
- Fix issues related to lvol cloning
Full Changelog: 26.2.5-PRE...26.2.6-PRE
26.2.5-PRE
What's Changed
- Fix LVol delete related issues
- Implementation of cli command parameter deprecation
- Promoted
cluster graceful-shutdownandcluster graceful-startup - fix security scan CVEs
- pip python kubernetes client version to 35.0.0
- feat: add --pool option to list snapshots by pool id or name
- Enhamce lvol clone speed
Full Changelog: 26.2.3-PRE...26.2.5-PRE
26.2.4-PRE
26.2.3-PRE
What's Changed
- Adds --namespaced to lvol add/ and snapshot clone
- reject duplicate pool name only in the current cluster
- Bug fixes and security enhancments
Full Changelog: 26.2.2-PRE...26.2.3-PRE
26.2.2-PRE
26.2-PRE
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
What's Changed
- R25.10 hotfix fix cpu topology by @wmousa in #939
- R25.10 hotfix lvol clone by @Hamdy-khader in #934
Full Changelog: 26.1.1...26.1.2
26.1.1
R25.10-Hotfix: pin 26.1.1 and fix clone path regression.