Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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 that you configure 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

...