Configuring Swarm for Platform Server

1 Swarm Storage
- - 1.1.1 NTP
- 1.2 Important
  - 1.2.1 Syslog
  - 1.2.2 Networking
2 Content Gateway

Swarm Storage

Swarm Storage nodes use a configuration file (.cfg). The file needs these minimum settings to boot Swarm:

cluster.name=CLUSTER·NAME
disk.volumes=all
cluster.enforceTenancy=true

The Platform bundle includes a basic Swarm configuration file it auto-populates and applies to each new Swarm node under management. Following are the network and management services that the Platform server handles for Swarm and the corresponding Swarm settings through which they are configured.

Verify the cluster.cfg is ready for deployment by the Platform server:

Edit the cluster.cfg file (/etc/caringo/storage/cluster.cfg)
Create entries for settings that Platform does not add (such as the proxyUri).
Create entries for any overrides made such as to use a different time server.

NTP

The Platform server contains an NTP server and automatically populates the following Swarm configuration setting to point to the Platform server, unless you override it with your own entry.

network.timeSource=PLATFORM·IP

Important

The NTP server is essential because Swarm nodes must have a shared concept of time, and they must use the same time source, for consistency. If NTP is configured but unreachable, Swarm nodes do not boot.

Syslog

The Platform server contains a Syslog server and automatically populates the following Swarm configuration setting to point to the Platform server, unless you override it with your own entry.

log.host=PLATFORM·IP

Networking

The Platform server automatically configures IP Address information for each chassis based on the IP ranges provided during installation. The Platform server automatically populates the following Swarm configuration settings, unless you override them with your own entries.

Content Gateway

Content Gateway also uses a configuration file (.cfg). If you are running Service Proxy/SwarmUI on a standalone Gateway, you must add the Platform server information to the [cluster_admin] section:

platformHost — the valid, reachable IP by which the Gateway accesses the Platform server.
platformPort — specify if you changed from using the default.

See Enabling the Service Proxy in Gateway Configuration.