This section lists the most important features from each release.
Qumulo Core 7.2.3.1
Important
- 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.
- Added support for read-only Global Namespace functionality between two or more Qumulo clusters.
- Made CNQ on Azure available on Qumulo Nexus.
- 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.
- Resolved an issue with the APIs & Tools page in the Web UI not showing certain REST endpoints correctly