Nodeum 2.1 - Release notes

About Nodeum 2.1

This latest major version features a distributed systems architecture, with each node participating as a member of a Data Management cluster. The cluster provides access to storage resources linked to various storage nodes.

The solution will appear as a unified namespace for each deployed cluster. Multiple nodes are linked through a high-performance IP network, even over long distances via reliable IP connections.

Every cluster node contributes to the global content catalog, facilitating scalable data movement across all storage.

This enhanced data management solution is designed to be faster, easier and more reliable with elastic scale-out architecture and integration to the most common end-user applications. This leads movement across posix file system and object storage (S3 and Swift). It ensures preservation of data accessibility between file level user management base and token based federation.

In this latest release, Nodeum end users gain additional integration options by utilizing hooks to run callback code either before or after data movement. Furthermore, HPC customers can now take advantage of Nodeum Data Movement with the SLURM workload manager.

Migration notes

Migration path

There is no migration path between Nodeum v1 and Nodeum v2.

How to upgrade ?

For automatic upgrade information, see How to deploy Nodeum Data Mover

Pay attention to the warnings described above.

Limitations and warning

• Retrocompatibility to CENTOS 7 or RHEL 7 is not available
  

Support removal notice

N/A

Deprecation notice

Release 2.1.0 - February 19th, 2025

Nodeum 2.1.0 is a major release.

OS

• # 54|191|202|203 : Support RHEL 9

Workflow

• #183 : Solve issue with checksum calculation

Release 2.1.1 - April 22th, 2025

Nodeum 2.1.1 is a minor release.

Console

• #206|207|212  : Layout improvement
  

S3 Plugin

• #208  : improve the usage of SSL certificate
  
  

Release 2.1.2 - May 13th, 2025

Nodeum 2.1.2 is a minor release.

Console

• #218  : Solve issue to manage SSL socket protocol
• #211 : Manage the local user access in the console
  
• #221  : Layout improvement

OS

• # 219 : Support Almalinux 8 - 9
  
  

Release 2.1.3 - May 21th, 2025

Nodeum 2.1.3 is a minor release.

Console

• #217|224  : Layout improvement
  
• #216 : solve issue - Task Listing and task history filter
• #225  : Solve issue to restore file - remove the limitation at 1000 files

Release 2.1.4 - July 31th, 2025

Nodeum 2.1.4 is a minor release.

Console

• #168 #252 : Improvement Console
• #235 : Solved Issue - angular authentication guard
  
  

Plugin

• #235 : fix log issue on dispatcher

User Management

• #241 : Add expiration date

Release 2.1.5 - September 3th, 2025

Nodeum 2.1.5 is a minor release.

Workflow

• #214 #268 : Resolved issue with folder removal
• #22 : Added support for preserving ACLs during copy operations

• #263 : Ensure the source directory cleaner completes cleaning in a single execution when multiple sources are involved.

Console

• #223 : Display the mover ID responsible for each move in task execution and history logs

• #264 : Include an authentication type column in the web user menu

• #266 #271 : Add the service id in the monitoring

Plugin

• #5 #6 #9 #248  : Plugin to retrieve the user's UID and all GIDs, verify them against the LDAP server(s), and register the information in Nodeum

Release 2.1.6 - September 3th, 2025

Nodeum 2.1.6 is a minor release.

Workflow

• #29 : Scale the dispatcher process for file discovery

• #272 : Improve calculation accuracy during task execution
  

Release 2.1.7 - November 26th, 2025

Nodeum 2.1.7 is a minor release.

Console

• #280 : Rename the option "Remove also selected folders" like : "Extend deletion to selected folders"

Ansible

• #281 : Remove hardcoded static MariaDB version

• #285 : fix Ansible update for LDAP mapper deployment

•  

Plugin

• #283 : LDAP User Mapper: Fix Logging

• #286 : LDAP User Mapper: Template Caching Bug
• #289 : add ldap user mapper log to enable only in trace/debug mode

Workflow

• #169 : Improve readability of task logs
• #279 : Resolved mover ID format in user logs

• #284 : when scanning dirs swith context for new goroutine since goroutine willn't treat main process's switch to other user when scanning parallely

Storage

• #111 : handle Glacier access errors by fetching and using object metadata
• #277 : S3 Native Object lock implementation

• #278 : add s3 native custom encryption key to db

Release 2.1.8 - January 27th, 2026

Nodeum 2.1.8 is a minor release.

 Console

• #311 : add services in table in addition to mermaid service diagram.

Workflow

• #293 : add task ownership to user during admin task creation on behalf of other user

• #302 : Nil Pointer Fix in Dispatcher.  Setting mover ID in task options caused a panic when no task options existed (e.g., no --overwrite or --recursive flags).
• #303 : Scanner workers shared a single context switcher instance, creating a potential race condition where one goroutine could switch context while another was still scanning.

• #304 : Dispatcher pipeline builder panics under high request volume

• #287 - #298 - #309 : Multi-Context GID Switching for Copy/Move Operations

• #317 : Change default behavior to set the ownership to the one who make the copy

• #326 : // mover value defined as global value.  Set parameter in configuration Ansible a global value

OS

• #301 : Remove from ansible the s3fs-fuse dependencies url (for RHEL 9)

• #322 : Solved Issue - Logrotate service is failing to start due to duplicate entries for btmp and wtmp