| Table of Contents | ||
|---|---|---|
|
...
Docker or proxy use — Gateway can now be configured for use either within a Docker environment or behind a proxy. The Gateway configuration has two new settings available (
externalHTTPPort, externalHTTPSPort) per protocol: [scsp] and [cluster_admin], the Service Proxy. They only take effect when X-Forwarded-Proto is found on the request; Gateway uses X-Forwarded-Proto to determine which port to use. (CLOUD-3055)Metadata Translation — Gateway seamlessly moves custom metadata between SCSP and S3. It translates the metadata formatting between the protocols. It provides S3 and SCSP applications the ability to access each other's metadata. See Metadata Translation between SCSP and S3. (CLOUD-2919)
Quota stability — Quota implementation has been significantly hardened, resolving general problems with frozen usage status/data and excessive emails from state changes. (CLOUD-3045)
Fixed issues:
There were are issues when enabling versioning or quotas through the Content UI. The fix prevents creation of duplicate (conflicting) domains in the storage cluster. (CLOUD-3019)
Updating certain Swarm configuration settings through the Gateway services proxy (port 91) sometimes required the sptid query argument value. (CLOUD-2999)
Gateway validates on startup that [storage_cluster] managementPassword is set when the ServiceProxy ([cluster_admin]) is enabled. (CLOUD-2617)
New in 5.4.1:
Content Gateway adds support so it can be used with Swarm UI 2.3. Note: 2.3 includes a new feed type, S3 Backup feed, which requires Swarm 11.
Several fixes were are made related to S3 multipart uploads. (CLOUD-2994, CLOUD-3074)
Upgrade Impacts
Swarm Storage Requirements — Gateway 5.4 requires a minimum back-end storage cluster version of 9.6. The storage cluster must be upgraded prior to installing this version of Gateway.
Releases of Gateway 5.1.3 and earlier are not compatible with Storage versions 9.2 or higher. For historic compatibility details, refer to the releases included with those distributions.
RHEL/CentOS 6 Deprecation — Support for RHEL/CentOS 6 is removed in the near future. Completing the transition to RHEL/CentOS 7 now assures a smooth upgrade path to future Gateway versions.
Automatic service start must be re-enabled — After the upgrade, the service may not automatically start after a system reboot. To re-enable the service, run:
"chkconfig --add cloudgateway" for RHEL/CentOS 6, or
"systemctl enable cloudgateway" for RHEL/CentOS 7. (CLOUD-2819)ExpanDrive — ExpanDrive users must upgrade to ExpanDrive 6.1.0 with this version of Gateway; earlier versions report 403 Signature errors when creating a folder or uploading a large object. (CLOUD-2746)
...