This section lists the most important features from each release.
Qumulo Core 7.4.0 (Quarterly)
The majority of functionality and stability improvements in this Qumulo Core release are internal.
Improved UID and GID sorting in the Web UI.
Qumulo Core 7.3.2.1
- Removed the limit from the number of floating IP addresses per cluster
- Added support for sharing S3 objects with presigned URLs to additional S3 API actions
Qumulo Core 7.3.1.2
Important
- For clusters that were created in 2016 (or earlier), this release resolves an issue identified in Qumulo Core 7.3.1.1 where, under certain conditions, the cluster was unable to start after being upgraded to 7.3.1.1, resulting in the cluster going offline.
- For clusters that have only tagged VLANs but no untagged networks, this release resolves an issue in Qumulo Core 7.3.1 where it was possible for the default gateways to be copied incorrectly during the upgrade process, resulting in a potential cluster outage.
- Made it easier to authorize hub portals from the hub portal host cluster by adding information to REST APIs and
qqCLI commands - Improved the behavior of NFSv3 and NFSv4.1
ACCESScommands - Increased the S3 connection limit
- Configured Qumulo Core to permit (but ignore) out-of-spec query parameters for S3 API actions
- Reverted floating IP assignment to Qumulo Core functionality prior to version 7.1.0
- Added a REST API and a
qqCLI command for querying the current fault tolerance of an object-backed cluster - Resolved an issue with NLM connections
- Resolved an issue with tree deletion operations
Qumulo Core 7.3.0 (Quarterly)
- Added the self-service permission model to Qumulo REST API access tokens and made changes to corresponding
qqCLI commands - Made it possible for a user to perform operations on their own access keys without having RBAC privileges
- Resolved issues concerning cached data on a spoke portal host cluster, directory metadata block updates made by S3 API actions, and the
GetObjectS3 API action with the Veeam client
Qumulo Core 7.2.3.2
Important
- This release resolves an issue with Global Namespace functionality in Qumulo Core 7.2.3.1 that could cause files to become unavailable temporarily.
- If your Qumulo cluster's nodes haven't been configured to use static routes, it isn't necessary to upgrade from Qumulo Core 7.2.3 to 7.2.3.1. To determine whether your cluster's nodes use static routes, SSH into the node and run the
ip route showcommand. Typically, static routes do not have tags such asproto dhcporproto kernel. For further help, contact the Qumulo Care team. - If your Qumulo cluster's nodes use static routes, this release resolves an issue in Qumulo Core 7.2.3 that, under certain conditions, caused the system to lose its static route configurations after a quorum event.
- Made CNQ on Azure available on Qumulo Nexus.
- Added support for read-only Global Namespace functionality between two or more Qumulo clusters.
- Added support for three-node clusters to CNQ on Azure and CNQ on AWS.
- Added support for CNQ clusters that adjust to multi-AZ configurations automatically.
- Improved S3 Object Lock functionality and made changes to corresponding S3 API actions.
- Made improvements in S3 Versioning API actions and the
CopyObjectS3 API action. - Allowed users without administrative role-based access control (RBAC) roles to modify S3 access keys and made changes to corresponding
qqCLI commands. - Updated some of the error types and HTTP status codes that appear during cluster membership operations.
- Added REST API resources and
qqCLI commands for creation and membership change of CNQ clusters. - Resolved an issue with an SSL configuration change while the S3 server is in plaintext mode.
Qumulo Core 7.2.2
- Configured Qumulo Core to permit more than 10 floating IP addresses for each node
- Added support for floating IP addresses to Cloud Native Qumulo on AWS
- Made improvements to the S3 API
- Added two REST API resources for controlling SSL ciphers
Qumulo Core 7.2.1.1
Important
This release resolves an issue in Qumulo Core 7.2.0, 7.2.0.1, and 7.2.1 that could cause a cluster to become unresponsive due to incorrectly closed LDAP connections.
This release resolves an issue in Qumulo Core 7.2.0, 7.2.0.1, and 7.2.1 that could cause a cluster to become unresponsive due to incorrectly closed LDAP connections.
- Released the Qumulo Core Product Package in
.deband.rpmformats - Allowed Object Lock to be enabled to for newly created S3 buckets
- Added support for resuming TLS sessions over FTP
- Made improvements in SMB session handling
- Made improvements in audit logging
Qumulo Core 7.2.0.2 (Quarterly)
Important
- This release resolves an issue in Qumulo Core 7.2.0 and 7.2.0.1 that could cause a cluster to become unresponsive due to incorrectly closed LDAP connections.
- This release resolves an issue on HPE platforms by maximizing the reuse of existing REST client connections and by restarting the iLO monitor regularly. Previously, REST connections within the iLO monitor consumed all available memory after running for approximately longer than one week.
- The majority of functionality and stability improvements in this Qumulo Core release are internal.
- Made CNQ on AWS available on Qumulo Nexus.
- Resolved an issue with the APIs & Tools page in the Qumulo Core Web UI not showing certain REST endpoints correctly