All notable changes to LINSTOR Gateway will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
- Change the
scsi_sn
andproduct_id
calculations so that they are both unique per volume. (0d144af9)
1.6.0 - 2024-07-18
- Correct a statement about multiple exports in the "nfs create" help text. (ba82ed58)
1.6.0-rc.1 - 2024-07-04
- Add a sensible User-Agent when sending http requests via the client. (fc34f086)
- NFS: Let LINSTOR set the file system owner of the export's root directory. This allows XFS file systems to be used with NFS exports. (01161bfc)
- NFS: Add a --filesystem option when creating an NFS export. (86b70a58)
- Fix some Go API client functions so that they actually return data. (34f68fc3)
1.5.0 - 2024-04-17
- Added hints to some health check outputs to help users resolve potential issues. (09e0860)
- New health check for NVMe-oF resource agents. (d3441f5)
- New health check for SCST kernel modules and user space utilities. (138c1f6)
- The drbd-reactor health check now also checks that if the
drbd-reactor-reload.{path,service}
files are up-to-date. (2c40ff0) - When creating a resource, linstor-gateway now waits a few seconds to ensure that the resource is actually running. This prevents situations where the resource fails to start, but linstor-gateway still reports it as "running". (2c40ff0)
- Various improvements to the end-to-end tests.
1.4.0 - 2024-03-04
- No changes over rc1
1.4.0-rc.1 - 2024-02-20
- The
nfs create
command now supports creating multiple NFS exports in the same cluster. (6244defb) - The
delete
command now prompts for confirmation before deleting a resource. (7c6d7833) - drbd-reactor configuration files generated by LINSTOR Gateway are now versioned and can be migrated to new versions automatically. (87230226, f72c2c39)
- The
nfs upgrade
command now actually respects the--dry-run
flag. (e760b419) - drbd-reactor configuration files no longer include the deprecated
id
field. (878d53f4) - In the NFS configuration file, the
IPaddr2
andnfsserver
resource agent entries were switched. These are now in the correct order. (2337e327)
1.3.0 - 2023-10-24
- No changes over rc1
1.3.0-rc.1 - 2023-10-16
- The
status
command will now show what node a resource is running on. (106dfc88) - The
check-health
command now differentiates between "agent", "server", and "client" mode, checking the requirements for the respective mode of operation. (e0b25072) - All
create
commands now use-r
as the shorthand flag for resource groups. Previously, iSCSI used-g
instead -- this shorthand is now deprecated. (5b0eb9ab) - When creating an iSCSI target, the
--implementation
flag can now be used to specify what iSCSI target implementation should be used by the underlying resource agent. (e6bcc14f) - When a step in the creation of a resource fails, the resources created in previous steps will now be cleaned up. This avoids "resource already exists" errors. (434d2d13)
- When installing LINSTOR Gateway via rpm, the drbd-reactor auto-reload files will now be copied to the appropriate place automatically. (736cd2ae)
- The
check-health
command now finds the correct path to the drbd-reactor documentation directory more reliably. (bc4747ac)
1.2.0 - 2023-03-14
- When creating a resource (iSCSI, NVMe-oF, or NFS), LINSTOR Gateway will now do a basic check for IP collisions. If the provided service IP is already in use by another resource, an error will be thrown. (48ac8502)
- The CLI will no longer print the usage information whenever an error happens. (4e2cc19c)
- When listing resources, degraded resources could previously be displayed twice. This was changed so that every resource only gets reported once. (a4b56ceb)
- Remove a check that verifies a resource is stopped before adding a volume. Adding volumes works just as well on running resources. (8426c36e)
1.1.1 - 2023-03-06
- Fix NFS healthcheck on older systemd versions (53bbd671)
- Ignore and overwrite an existing promoter config if its corresponding LINSTOR resource does not exist (137f7560)
- Fix a
nil
dereference when listing resources with a broken LINSTOR state (df53d0b3)
1.1.0 - 2023-02-24
- Extend the health check for NFS: it is now verified that the
nfs-server
package is actually installed.
- Update Go dependencies
1.0.0 - 2022-11-21
- No changes over rc1
1.0.0-rc.1 - 2022-11-04
- Properly support CORS on the API endpoints
- Fix a nil dereference when one or more nodes are offline
- Add an
upgrade
command which can be used to migrate existing targets to newer versions of LINSTOR Gateway
- Improve packaging process
- Update Go dependencies
0.13.1 - 2022-07-26
- Fix a bug that occurs when creating a volume with number zero
- Update Go dependencies
0.13.0 - 2022-06-27
- Add a
--gross
option, which makes the "size" specify the actual space that the volume will occupy on disk instead of the usable net size
0.12.1 - 2022-05-03
- Make sure
iscsi create
respects the--resource-group
argument - Work around a size calculation bug for LINSTOR affecting thick LVM volumes
- Update Go dependencies
0.12.0 - 2022-04-03
- Set the SCSI serial number to a value that is guaranteed to be (reasonably) unique
0.12.0-rc.1 - 2022-03-17
- Add a new endpoint,
/v2/status
, to query the status of the server - Support CORS for the REST API
- Generate more readable toml files (
start
entries are on separate lines) - Mark LINSTOR resources as degraded if the actual place count is lower than desired
- Point users to
linstor advise resource
if any resources are degraded
- Healthcheck: fix the path of the LINSTOR Satellite systemd override directory
- Update Go dependencies
0.11.0 - 2022-02-14
- No changes over rc2
0.11.0-rc.2 - 2022-02-08
- Also add a cluster private volume for direct REST API calls
- Disallow underscores ("_") in iSCSI IQNs
- Add missing
--allowed-initiators
flag to iSCSI create command
0.11.0-rc.1 - 2022-01-31
- Add a new
check-health
command that checks whether all dependencies and requirements are met for LINSTOR Gateway - Implement best practices for NFS and for failover scenarios
- Change architecture: the CLI is now exclusively a client for the server
- REST API v2.0.0
0.10.0 - 2021-11-24
- No changes over rc1
0.10.0-rc.1 - 2021-11-17
- Change quorum options of created resource to be appropriate for drbd-reactor
- iSCSI: support supplying multiple service IPs for iSCSI-level multipathing
- Improvements to the documentation
- Change drbd-reactor configuration format to be compatible with drbd-reactor 0.5.0 (
on-stop-failure
->on-drbd-demote-failure
)
0.9.0 - 2021-09-28
- Minor fixes over rc3
0.9.0-rc.3 - 2021-09-23
- Minor fixes over rc2
0.9.0-rc.2 - 2021-09-15
- Some minor fixes over rc1
- The list of controllers is now parsed from a config file (additionally to the command line flag)
0.9.0-rc.1 - 2021-09-01
- Change high-availability backend from Pacemaker to LINBIT's own drbd-reactor
- Add support for NVME-oF targets
- Remove requirement for symlinking the binary: use "linstor-gateway iscsi" instead of "linstor-iscsi"
- Improve CI testing (integration tests)
0.8.0 - 2021-03-23
- Fix a bug related to Pacemaker 2 (use the "kind" attribute for order constraints instead of "score")
- Implement pipe detection; disable colors when not writing to a TTY
- Do not send back the iSCSI credentials over the REST API
0.7.0 - 2020-12-04
- Add ability to manage NFS exports
- Rename to linstor-gateway
0.6.2 - 2020-10-14
- Remove drbd-pacemaker depencency to fix packaging
0.6.1 - 2020-10-09
- Pacemaker now uses the drbd-attr resource agent to access drbd promotion scores
0.6.0 - 2020-04-29
- REST API version 1.1.0
- New command
linstor-iscsi version
displays version information - New REST endpoints
/api/v1/iscsi/{iqn}/{lunid}/start
and/stop
to start/stop targets linstor-iscsi start
/stop
now accepts the--iqn
and--lun
flags, making it actually work- Fixes to the recent LUN size change
0.5.0 - 2020-03-31
- Size information was removed from LUN; it only belongs to LINSTOR
0.4.2 - 2020-03-09
- Improved process to find the LINSTOR controller
- Diskless LINSTOR resources are now considered "Good" instead of "Down"
0.4.1 - 2020-01-31
- Follow-up fixes to the service IP netmask problem
0.4.0 - 2020-01-31
- Fix service IP netmask (it was always 24 before)
- Status now includes information about what node the target is running on
0.3.1 - 2020-01-28
- Bump of gopacemaker
0.3.0 - 2020-01-20
- Service IP is now displayed when listing targets
- Low-level pacemaker API factored out to gopacemaker library
0.2.0 - 2019-12-03
- rpm packaging
- Bugfixes
0.1.0 - 2019-08-29
- First released version
- REST API version 1.0.0