Releases: LINBIT/linstor-server
Releases · LINBIT/linstor-server
v1.4.0-rc1
linstor-server 1.4.0-rc1
- Added new layer: writecache (needs property
Writecache/PoolName = <nameOfStoragePool>
set on volume-definition or above)
Additional properties are available. Seelinstor resource-definition set-property --help
- Deprecated
--diskless
flag (use--drbd-diskless
or--nvme-initiator
instead) - needs clientv1.0.8
or higher - Allow DRBD on top of NVMe layer
v1.3.1
linstor-server 1.3.1
- Fixed incorrect PUT return codes
- Fixed deletion of storage pools
- Fixed missing deletion of net-interfaces if node was deleted
- Added DB migration for orphaned drbd layer data
- Added missing ETCD data migrations
- SPKD: fixed creation of nvme namespaces
v1.3.0
linstor-server 1.3.0
- Support SPDK 19.07
- REST-access log can be configured in the linstor.toml
- Property setter are now synchronous
- Fixed auto-selector with replicas-on-different
- Fixed typo in client_key_pkcs8_pem variable
- Added missing http ports for linstor-controller firewalld service file
- Added startup check for database support, can be disabled with --disable-db-version-check
v1.2.1
linstor-server 1.2.1
- Allow configuration of etcd with tls
- Use more environment variables to configure Controller or Satellite:
LS_REST_BIND_ADDRESS
LS_REST_BIND_ADDRESS_SECURE
LS_CONFIG_DIRECTORY
LS_LOG_DIRECTORY
LS_LOG_LEVEL
LS_KEEP_RES - DRBD resource files will now be backuped
- Delete old snapshot-restore properties that were never deleted
- Always skip initial sync on ZFS
- Fix query-max-volume-size REST call, expected incorrect POST data
- REST-API at version 1.0.10
v1.2.0
linstor-server 1.2.0
- Add auto-tiebreaker feature
- Fix possible deadlock on closeConnection event
- Better volume error reporting
- Fix a race condition on deleting peers
- Fixes to snapshot restoring
- Most client list filter now on the Controller
- NVME allow multiple NVMe initiators * REST-API at version 1.0.10
v1.1.2
v1.1.1
linstor-server 1.1.1
- Node reconnect now also reconnect failed nodes
- Fixed dmstats command calling
- Reduced classpath for better process view
- Added exception handling for device handler (killing satellite in some cases)
- Correctly cleanup(remove from database) on retry-task operations
- NVME fixed ArrayIndexOutOfBoundsException if there are external NVME resources
- Added user name to log entries
- Fixed incomplete migration for external names
v1.1.0
ETCD support
There are some limitations regarding the ETCD support:
- There is no migration from SQL -> ETCD
- Linstor requires the ETCD server to increase its limit for requests per transactions [1]
Our tests were running well with 1024, but some linstor-actions are depending on how many objects you already have (i.e. auto-place)
you might want to increase that value if necessary.
example: etcd --max-txn-ops 1024
To use ETCD simply change your linstor.toml to contain
[db]
connection_url = "etcd://127.0.0.1:2379"
Some more release details:
linstor-server 1.1.0
- Add truststore to config and HTTPS rest-api
- StorPoolData: correclty set snaphot supported field
- IntAuthResponse: Fixed version mismatch impl error
- satellite: parse satellite settings from toml file
- Satellite nodes don't need anymore to have matching hostnames for DRBD to work
v1.0.1
v1.0.0
- Resource groups
A resource group is a parent object of a resource definition and all property changes
made on a resource group will be inherited by its resource definition children.
The resource group also stores settings for auto-place rules and can spawn a resource definition depending on the stored rules.
Here is a example:
linstor resource-group create my_group --place-count 3
linstor volume-group create my_group
linstor resource-group spawn-resources my_group myresource 2G
Some more release details:
linstor-server 1.0.0
- Added resource groups/volume groups
- REST-API version 1.0.8
- Fixed incorrect HTTP initialization if rest bind address was given by cli
- Fixed rollback in props container
- Fixed sysfs throttling with nvme diskless
- Allow log level to be set in linstor.toml or cli
- External command timeout is now configurable