Nodeum 2.2 - Release notes

About Nodeum 2.2

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 Data Archiving and Nodeum Data Mover

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 dm/2.2.0 - June 26th, 2026

Nodeum 2.2.0 is a major release.

Workflow

• #424 : Reactivate the option "Retrieval of glacier"

Console 

• #413 : Design a dasboard page 
• #386 : add a filter by status in the task history
• #428 : Task monitoring - add user scope when accessing task executions
• #422 : Solve issue - CSV Download
• #421 : Task Menu - Display the pool name
• #412 : add a search and sort capabilities in the services page
• #436 : Solved issue when deleting a NAS Pool

• #444 - #437 - #384 : new console layout aligned with the updated brand

  #442 - #441 - #427 - #425 - #417 - #405 - #404 - #403 - #390 - #389 - #388: Console improvement 

Ansible

• #370 : Solved issue - Installation ruby 3.1.4 - rubygems  
  #445 : add metrics config in ansible inventory options.yml

Promotheus

• #337 : Design the ability to export key metrics to Promotheus