Skip to content

Releases: linux-nvme/nvme-stas

v2.2.2

07 Jun 22:28
fd07276

Choose a tag to compare

Summary

Bug fix: During a software upgrade, while migrating the previous last known configuration, an old TID object may not contain a self._cfg member. To avoid crashing the system while loading the old config, one must introspect the old TID object to see if it contains a self._cfg member before trying to access it.

What's Changed

Full Changelog: v2.2.1...v2.2.2

v2.2.1

20 Mar 20:06
435248b

Choose a tag to compare

Summary

Just a few bug fixes. See NEWS.md.

What's Changed

Full Changelog: v2.2...v2.2.1

v2.2

16 Mar 18:00
c128b8a

Choose a tag to compare

Summary

This release adds support for in-band authentication.

What's Changed

New Contributors

Full Changelog: v2.1.3...v2.2

v2.1.3

27 Feb 22:19
f13cca5

Choose a tag to compare

Summary

  • Better handling of udev events and elimination of race condition between nvme-stas and nvme-cli.
  • Code format is now enforced by black. The command make black has been added to help developers make sure their contributions follow the right format.

What's Changed

Full Changelog: v2.1.2...v2.1.3

v2.1.2

24 Jan 17:03
318302b

Choose a tag to compare

Summary

A few bug fixes:

  • Documentation: Fix Read-the-Docs generation with Sphinx. A bug was recently introduced upstream in Sphinx, which causes nvme-stas documentation generation to fail. Had to pin Sphinx version to 5.3.0 until the bug is fixed upstream (it's actually fixed, but the Read-the-Docs site hasn't picked it up yet)
  • Avahi: Add support for protocols RoCE and iWARP of mDNS TXT field.
  • Avahi: Add _nvme-disc._udp to the list of supported mDNS service types.

What's Changed

New Contributors

Full Changelog: v2.1.1...v2.1.2

v1.1.9

24 Jan 16:36
ab3716a

Choose a tag to compare

Summary

Backported changes from the main branch:

  • In avahi.py, add support for RoCE protocol
  • In conf.py, add _nvme-disc._udp to the list of supported mDNS service types (stype)

What's Changed

Full Changelog: v1.1.8...v1.1.9

v2.1.1

09 Jan 17:07
95a2589

Choose a tag to compare

Summary

This release introduces a mechanism to ensure that Connect/Disconnect operations happen in the right order. This can be an issue when a large number of connections are made (> 100) and several of those connections fail. It takes the Linux NVMe driver 3 seconds to time out on a failed connection. And since the driver serializes the creation of connections, it can take several minutes for the kernel to cycle through a large number of failing connection requests. In other words, given 100 connection requests, and if every connection request fails, it will take the kernel 300 seconds (5 minutes) to cycle through all 100 requests. If during that 5 minutes we have changes to the configuration that require that some (or all) of these connections should be removed, we can end up with a Disconnect being requested while the kernel has yet to process the corresponding Connect. This results in Connect/Disconnect being processed in the reverse order.

What's Changed

Full Changelog: v2.1...v2.1.1

v2.1

06 Dec 18:25
523ce71

Choose a tag to compare

Summary

  • A new feature was introduced to automatically remove discovery controllers discovered through zeroconf (mDNS) when they are no longer responding. See NEWS.md for details.
  • This release also provides some bug fixes.
  • Finally, a lot of changes were made to Read-the-Docs documentation format.

What's Changed

Full Changelog: v2.0...v2.1

v1.1.8

02 Dec 16:18
cfffc69

Choose a tag to compare

Summary

This release addresses SuSE's issue 1205873.

What's Changed

Full Changelog: v1.1.7...v1.1.8

v1.1.7

11 Nov 17:44
0c6d592

Choose a tag to compare

Summary

This release addresses SuSE's issue 1204975.

What's Changed

Full Changelog: v1.1.6...v1.1.7