Qumulo Core Feature Log

This section lists the most important features from each release.

Qumulo Core 7.4.2.1

Important
This release resolves an issue that can occur while following a non-standard upgrade path.

Added support for Cloud Native Qumulo (CNQ) clusters with 1, 3, or more nodes
Made improvements to Cloud Data Fabric:
- Moved the REST APIs out of Preview status
- Removed a qq CLI command in favor of automatic clean-up of partially configured portal relationships
- Added support for FTP communications for spoke portals
- Changed the names of portal states, which indicate the stages of the spoke portal creation process and the proposal or deletion of a portal relationship
- Added new portal statuses, which indicate the accessibility of a spoke portal or a hub portal
Updated the default configuration for new NFS exports
Added a REST API and qq CLI command to facilitate deleting files from directories without constructing full paths

Important

This release resolves an issue where previously Qumulo hub portal host clusters that communicated with read-write spoke portals crashed if the portal contained files with very large file IDs.
This release resolves an issue that we identified in Qumulo Core releases 7.3.1.2 to 7.4.0, where making changes to networking configuration by using the API Tools page in the Web UI or by using the qq CLI caused the default gateway to not populate.
Global Namespace is now a core component of Qumulo Cloud Data Fabric.
To enable upgrades to this version of Qumulo Core, you must delete any existing spoke portals or hub portals from your cluster and then wait for any related tree-delete operations to complete before beginning the upgrade process.
To enable the QFSD API to distinguish between cluster-local and spoke-cached data, from this release of Qumulo Core onward, 64-bit integers can no longer represent QFSD API file identifiers. API integrations must treat them as variable-length strings, in accordance with the OpenMetrics API schema. Although this change affects all REST API endpoints the Qumulo REST API continues to accept old-style identifiers for backwards compatibility.

Made read-write spoke portals available by default
Eliminated the REST APIs for manual removal of cached data from spoke portals (no changes to automatic cached data removal)
Improved file identifiers to distinguish between cluster-local and spoke-cached data
Implemented Predictive Read Cache architecture for new cloud clusters
Renamed the designation preview (previously, beta) which marks REST APIs under development
Made public the REST API endpoints and qq CLI commands that manage a cluster’s DNS configuration

The majority of functionality and stability improvements in this Qumulo Core release are internal.

Improved UID and GID sorting in the Web UI.

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

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 qq CLI commands
Improved the behavior of NFSv3 and NFSv4.1 ACCESS commands
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 qq CLI 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

Added the self-service permission model to Qumulo REST API access tokens and made changes to corresponding qq CLI 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 GetObject S3 API action with the Veeam client

Important

This release resolves an issue with Cloud Data Fabric 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 show command. Typically, static routes do not have tags such as proto dhcp or proto 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 Cloud Data Fabric 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 CopyObject S3 API action.
Allowed users without administrative role-based access control (RBAC) roles to modify S3 access keys and made changes to corresponding qq CLI commands.
Updated some of the error types and HTTP status codes that appear during cluster membership operations.
Added REST API resources and qq CLI 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.