Supply a name, which is a description, when adding a Server Group; the unique identifier is the count (such as /2, above) at the end of the Configuration URL.

The new group appears at or near the end of the listing, ready to be configured with exports.

Each NFS Server Group has a unique Configuration URL, which can be clicked to view the current export definitions. These are the auto-generated and auto-maintained JSON settings being stored by Swarm for the group.

The configuration is empty until one or more exports is added.

Unique name for the export, to distinguish it from the others in Swarm UI listings.

The IP address(es) or DNS-resolvable hostname(s) for one or more Swarm Gateways.

(For backwards compatibility) Optional as of version 3.0. The IP addresses or DNS-resolvable hostnames for one or more Swarm Elasticsearch servers.

Note: Both Gateway and SwarmFS use the Primary (default) search feed. If a new feed is made Primary, these servers must be restarted.

(For backwards compatibility) Optional as of version 3.0. The unique alias name of the Primary (default) search feed. Locate this value as the Alias field in the primary search feed's definition. 

Case-sensitive. Unique pseudo filesystem path for the NFS export. 

Cannot be set to a single slash ("/"), which is reserved.

Domain
Bucket

Specifies where the data written via the export is associated: which domain and bucket to use.

Important: Verify the existence of the domain and bucket specified here.

Token Admin Credentials by Login

Token Admin Credentials by Token

User, Password, Expiration

Token, Expiration

Authenticate by Login

Authenticate by Token

User, Password

Token

N/A

Defaults to full read/write access. These other access restrictions are available:

• All operations (RW) - default

• No access (None)

• Read-only (RO)

• No read/write (MDONLY) - allows listing and metadata updates without access to file contents

• No read/write/modify (MDONLY_RO) - allows listing but no metadata updates and no access to file contents

Defaults to no squashing (allows all user IDs).

• None - default

• Root - squashes the remote superuser (root, uid=0) when using identity authentication (local user is the same as remote user)

• All - squashes every remote user, including root.

User ID and Group ID can be set when the NFS server is authenticating users from a different authentication sources and/or it is desired all files have a consistent user/group.

Typical situations:

• All clients are configured to use local password/group files, but SwarmFS through the Content Gateway is configured to use LDAP.

• All clients have local password/group files, but some users may not exist on all clients systems or may differ on each client.

• All clients have the same users and groups, but they are created in a different order.

• All clients authenticate using individual logins/accounts, but it is desired all files have the same consistent owner and group regardless of the user reading or writing the files.

• A client mounts the NFS exports as anonymous, but it is desired to have the files presented over the share to all NFS clients to have a consistent UID and GID.

As needed, customize the access for one or more specific clients.

Performance logging for SwarmFS, which reduces the noise in the ganesha log file. When enabled, logs PERF warnings to Elasticsearch query result dumps.

Performance logging for Elasticsearch, for use while troubleshooting issues such as partial listings. When enabled, sends the Elasticsearch query results to the debug log file. 

TCP

Supported transport protocol (TCP/UDP | TCP | UDP)

80

Required. Network port for traffic to Swarm Storage nodes

9200

Required. Network port for traffic to Swarm Search nodes

sys 

Remote Procedure Call (RPC) security type (sys | krb5 | krb5i | krb5p)

100

Maximum number of open connections to Swarm Storage. (v2.0)

5

(positive integer) How many times SwarmFS retries unsuccessful requests to Swarm and Swarm Search before giving up.

90

(seconds) How long SwarmFS waits before timing out Swarm retries.

90

(seconds) How long SwarmFS waits before timing out Swarm requests.

For best results, set this timeout to at least twice the value of the Storage setting scsp.keepAliveInterval.

300

(seconds) How long discovered Swarm storage nodes are remembered.

90

(seconds) How long SwarmFS waits for a write to Swarm to complete before retrying.

128000000

(bytes) Defaults to 128 MB, for general workloads. The amount of data to be read each time from Swarm. If the read size buffer is greater than the client request size, then the difference is cached by SwarmFS, and the next client read request is served directly from cache, if possible. Set to 0 to disable read-ahead buffering.

Improving performance - Set each export's Read Buffer Size to match the workload expected on that share. 

• Lower the read-ahead buffer size if most reads are small and non-sequential.

• Increase the read-ahead buffer size if most reads are large and sequential.

4

(positive integer) Adjust to tune the performance of large object reads; the default of 4 reflects the optimal number of threads, per performance testing. (v2.3)

64000000

(bytes) How large each part of erasure-coded (EC) objects may be. Increase (such as to 200 MB, or 200000000) to create smaller EC sets for large objects and so increase throughput for high volumes of large files. (v2.3)

1000

(milliseconds) Increase to minimize object consolidation time by directing SwarmFS to collect more data before pushing it to Swarm, at the expense of both RAM and read performance, as SwarmFS slows clients when running out of cache. Increase this value if the implementation is sensitive to how quickly the Swarm health processor consolidates objects, which cannot be guaranteed. (v2.3)

2000000000

(bytes) Defaults to 2 GB. Maximum limit that can be allocated for the export's export buffer pool. Once exceeded, client requests are temporary blocked until total buffers falls back below this number. (v2.0)

1500000000

(bytes) Once the allocated export buffers reach this watermark, SwarmFS starts to free buffers in an attempt to stay below “Maximum Memory Buffers”. During this time, client requests may be delayed. (v2.0)

"relatime"

Policy for when to update a file's access time stamp (atime). (v2.0)

• “noatime”: Disables atime updates.

• “relatime”: Updates atime if it is earlier than last modified time, so it updates once after each write.

• “strictatime”: Updates atime on every read and close.

60

(seconds) How rapidly non-SwarmFS object updates are reflected in SwarmFS listings. Lower to reduce the wait for consistency, at the cost of increased load on Elasticsearch. (v2.3)