Managing MountPoints

1. Mount Point Overview

What is a Mount Point?

In the FPT File Storage – High Performance system, a Mount Point is a logical access point that allows users to connect to a specific directory (path) in the storage pool. To mount data from a Bare Metal server, you need to create a Mount Point with the following configuration details:

• Path: The specific directory path on the storage system that you want to access.
• Access Protocol: For example, NFSv3 or NFSv4.
• Access Subnet: Only servers belonging to the specified subnet are allowed to mount. If a server is not in this subnet list, the mount request will be denied.

Role of a Mount Point

Component	Role
Mount Point	Access point from the internal network to file storage via NFSv3/NFSv4/S3.
Client (server)	Mounts data from file storage, displayed as a local disk.
Storage Backend (VAST)	Storage infrastructure.
QoS Policy	Attached to the mount point to limit IOPS, throughput, etc.

Mount Point Structure

Field	Description
Name	Display name in the portal
Path	Actual path, e.g.: /ml-data
Protocol	Protocol: NFSv3 or NFSv4
Subnet	CIDR network range allowed to access
Endpoint Range	Connection endpoint
QoS Policy	Performance control policy
NFS Alias	Path Alias displayed in the OS

Relationship with other components

• VPC & Subnet: A Mount Point can be assigned to multiple subnets within the same or different VPCs. Only servers in the assigned subnet can access it.
• QoS Policy: Limits performance through:
  • Max Throughput (MB/s)
  • Max IOPS
  • Burst Limit
• NFS Protocol: Supports TCP and RDMA. In particular:
  • TCP: Common and easy to use.
  • RDMA: High performance, low latency.
  • Multi-Path RDMA: For large workloads, parallel connections.

---

2. Creating a Mount Point

Important Principles

• Bound to a specific subnet: Only servers in the assigned subnet can mount.
• Do not create at the root path ("/"): Only create in subdirectories, e.g.: /project-a, /team1/data.
• One path – one mount point: Duplicates are not allowed.
• No limit on the number of mount points: As long as paths do not overlap.
• NFSv4 requires full path export: Every parent directory in the path must also be exported.

Example: to mount /project-a/team1/data using NFSv4, /project-a and /project-a/team1 must also be exported.

Steps to Create a Mount Point on Unify Portal

1. Go to the MountPoint tab and click Create MountPoint.
2. Fill in the details:
   • Region: Select the region to use.
   • VPC / Subnet: Select the subnet containing the GPU server.
   • Mount Point Name: 3–63 characters, letters/numbers/"_", cannot start or end with a special character.
   • Protocol: NFSv3 or NFSv4.
     • If NFSv3: An NFS Alias can be added.
     • If NFSv4: Ensure all parent directories in the path also use NFSv4.
   • Path: Starts with "/", does not end with "/" or a space, must not duplicate another path.
   • Option: Check "Create new directory" if the path does not yet exist.
   • QoS Policy: Select an existing policy or create a new one.
3. Click Create to finish.

Result

• Success: The Mount Point appears in the portal and can be mounted from servers in the subnet.
• Failure: An error is displayed – review the declared information.

---

3. Deleting a Mount Point

You can delete a Mount Point when it is no longer needed, in order to:

• Revoke access.
• Safely disconnect the server from the storage system.
• Support reconfiguration or network infrastructure changes.

How to Do It

1. Go to the Resource tab on the Unify Portal.
2. For the Mount Point to delete, select Action > Delete.
3. Confirm the action when prompted.

⚠️ Note:

• Ensure all applications have unmounted before deleting.
• Deleting a Mount Point does not delete data in the directory assigned to the path.