Connection NFS
Purpose
Defines the connection parameters for an NFS (Network File System) endpoint.
This Asset can be used by:
| Asset type | Link |
|---|---|
| Source | NFS Source |
| Sink | NFS Sink |
Configuration
Name & Description
-
Name: Name of the Asset. Spaces are not allowed in the name. -
Description: Enter a description.
The Asset Usage box shows how many times this Asset is used and which parts are referencing it.
Click to expand and then click to follow, if any.
Required roles
In case you are deploying to a Cluster which is running (a) Reactive Engine Nodes which have (b) specific Roles
configured, then you can restrict use of this Asset to those Nodes with matching
roles.
If you want this restriction, then enter the names of the Required Roles here. Otherwise, leave empty to match all
Nodes (no restriction).
NFS Settings
Server Configuration
-
Server: Hostname or IP address of the NFS server, e.g. 'nfs.myserver.com' or '192.168.1.100'. -
Export Path: The exported directory path on the NFS server, e.g. '/exports/data'. -
Permissions:-
User id (UID): The user id (UID) of the user that should access the NFS server. -
Group id (GID): The group id (GID) of the group that should access the NFS server. You can enter multiple group ids separated by commas.
NFS and Permissions: How It Works NFS itself doesn’t authenticate users or manage user accounts—it trusts the client to provide the correct UID and GID. When a client accesses an NFS share, it sends the UID and GID of the user making the request. The NFS server then checks these IDs against the file permissions on the exported filesystem, applying the standard Linux read (r), write (w), and execute (x) permissions based on ownership and group membership.
For example:
- If a file on the NFS server is owned by UID 1000 and GID 1000 with permissions rw-r----- (owner read/write, group read, others none), a client user with UID 1000 can read and write, while a user with UID 2000 but GID 1000 can only read. The key here is consistency: the UID and GID must match between the client and server for permissions to behave as expected. NFS doesn’t inherently map usernames; it works purely with these numeric IDs.
-
-
Max. parallel NFS commands (per cluster node): The maximum number of parallel NFS commands that can be executed by each node in the cluster. Use this to limit the number of concurrent NFS operations on the server and avoid overload.
Related Topics
Internal
Please note, that the creation of the online documentation is Work-In-Progress. It is constantly being updated. should you have questions or suggestions, please don't hesitate to contact us at support@layline.io .