Release Notes for Content Gateway 5.1

New Features

  • Quota Policies - You can now define comprehensive quota policies to enforce usage limits for specific tenants, storage domains, and buckets. Through the Content Portal, navigate to the Properties of a tenant, domain, or bucket and set limits for storage usage and/or network bandwidth metrics, selecting which action to occur when the limit is exceeded and who to notify. The actions (consequences) for overages range from notification only, read and delete only, read only, to complete lockout of access. Both storage and bandwidth limits include override options, which allows creating temporary grace periods with lesser restrictions. Setup and customization of quotas occurs through the new [quota] section of the Gateway Configuration.
    See Setting Quotas.

  • CloudScaler Renamed - The product known as CloudScaler is now referred to as the Content Gateway (inclusive of the Content Portal and Metering). The name change reflects the current and continuing integration of all products into Swarm 9. Note the new RPM names: caringo-gateway-{version}.rpm, caringo-gateway-webui-{version}.rpm

  • RHEL/CentOS 7 Support - This release is tested and certified with RHEL/CentOS 7. While you can continue to use RHEL/CentOS 6 for Content Gateway, it is recommended that customers migrate to the version 7 platform as soon as practical.

  • Viewing Versioned Objects - When multiple versions of an object exist, the Content Portal provides a drop-down list so the metadata details for each version can be viewed.

  • Service Proxy - The new Service Proxy (ServiceProxyServlet) works as a special instance of Gateway configured with additions and overrides to its configuration. The Service Proxy provides a proxy to a Swarm cluster, leveraging the same IDSYS authorization and authentication as your Content Gateway. With the Service Proxy, you can host the Swarm Storage UI and API from a server that is accessible to your administrators and have the Service Proxy manage communication with the Swarm cluster. Performing this provides a single access point for managing and monitoring an entire Swarm cluster. (5.1.2:  CLOUD-2602)
    See Service Proxy

Upgrade Impacts

  • Swarm Storage 9.1.2 - Swarm 9.1.2 is the minimum required version of the back-end storage cluster. The storage cluster must be upgraded prior to installing this version of Gateway.

  • Elasticsearch 2.3 - Swarm 9 includes significant enhancements to its use of Elasticsearch and Gateway now depends upon features from Elasticsearch 2.3. Prior to upgrading Gateway, you must complete the migration to Elasticsearch 2.3. See the Swarm 9 storage cluster release notes for details regarding this migration.

  • The HTTP response code from Content Gateway has been changed to HTTP 503 upon encountering a root IDSYS with an invalid syntax. It previously returned HTTP 403 (Unauthorized) which leads to confusion with debugging configuration issues.

Additional Changes

  • Corrects an issue with S3 multipart writes on storage clusters where parallel uploads are not performed. This resulted in listing errors when using Cyberduck version 5.0. (5.1.0: CLOUD-2398)

  • Case-insensitive metadata searching within Swarm 9 storage cluster is now compatible with the S3 protocol front-end once you complete the migration to Elasticsearch 2.3. (SWAR-5283, SWAR-6317)

  • Long metadata field names are truncated in collections display to improve readability. (5.1.0: CLOUD-1691)

  • Help links for both 'Documentation' and 'Online Support' in the Content Portal are now customizable through edits to the file _admin/portal/customLinks.json. (5.1.0: CLOUD-1987)

  • Fixed an issue that caused a failure when using SCSP APPEND through the Gateway. (5.1.2: CLOUD-2629)

  • Fixed an issue in which the loss of one Elasticsearch node in a multi-node Elasticsearch cluster resulted in failure to perform queries and perform S3 listings. (5.1.2: CLOUD-2412)

  • Fixed an issue that threw an error and prevented an object delete when the context disallowed versioning. (5.1.1: CLOUD-2611)

  • Improved the reliability of S3 multipart upload completion. (5.1.2: CLOUD-2414)

  • Improved the handling of Swarm errors during S3 multipart upload completion. (5.1.3: CLOUD-2633)

  • Fixed: Using the utility 's3cmd' v1.6.1, attempts to perform 's3cmd mv' from one filename to another and/or one bucket to another failed for large (100+ MB) files. (5.1.3: CLOUD-2659)

  • Fixed: A change in Swarm 9.1.0 caused S3 header "x-amz-delete-marker: true" to no longer be sent in response to a HEAD of a deleted object, although the header was still returned on GET. (5.1.3: CLOUD-1041)

  • Fixed: Gateway 5.0.0 - 5.1.2 S3 listings did not include any ETag for objects uploaded via SCSP parallel write or S3 multipart APIs because they had no Content-MD5. The missing XML key broke clients such as s3cmd. Gateway now includes the same generated (non-MD5) ETag in listings as is returned on a GET of the object. Gateway and Swarm Storage now generate a "composite MD5" of the parts, similar to AWS S3, and Gateway uses that as the object's ETag in S3 response headers and listings. (5.1.3: CLOUD-1496)

  • Fixed: Using V4 signatures with some S3 clients (such as rclone) may receive a 403 signature mismatch error caused by the request header "Content-type" containing a lowercase "charset". (5.1.3: CLOUD-2664)

  • Fixed: When using the S3 list multipart uploads operation, if there are multiple simultaneous uploads in progress for a single object, only one of the uploads is included in the listing. (5.1.3: CLOUD-2333)

© DataCore Software Corporation. · · All rights reserved.