Page Comparison

...

• Swarm Storage cluster implemented with Storage settings needed by Gateway

• Elasticsearch cluster installed (if using metering data for critical functions such as billing, deploy at least 3 Elasticsearch servers and set up snapshot backups of that data)

• Search feed defined and enabled

• An authentication backend, such as LDAP or PAM

• Network time protocol (NTP) server reachable by both Gateway server(s) and Swarm storage nodes

• At least one server on which to install the Content Gateway software

...

• Gateway server software:

  • 64-bit Linux operating system, RHEL 7/Rocky Linux 8 or RHEL/CentOS 7 or Rocky 8

• Gateway server hardware:

  • Virtual or physical machine

  • 2+ CPU cores

  • 2+ GB RAM

  • 3+ GB /tmp space

  • 2+ GB available disk storage after OS installation (see Space Requirements below)

• For high availability and capacity scaling, add the following:

  • Two or more additional Gateways 

  • A load-balancing mechanism

• Prevent Gateway clients from making storage requests directly to the back-end storage cluster using one of these methods:

  • (most common) Make the Gateway servers dual-homed on the front-end client network and the back-end storage network. 

  • Use network filtering to prevent direct user access to the storage cluster and to deploy Gateway servers and storage servers on one subnet. 

  • Use VLAN tagging on the Gateway server's network interface to allow one physical interface to carry both front-end and back-end traffic.

...