Mounting a filesystem using the stateless clients feature

Content Software for File CLI Reference

Version
4.2.x
Audience
anonymous
Part Number
MK-HCSF001-03

The Stateless Clients feature defers the process of joining the cluster until the mount is performed. Simplifying and improving the management of clients in the cluster. It removes tedious client management procedures, which is particularly beneficial in AWS installations where clients may join and leave at high frequency.

Furthermore, it unifies all security aspects in the mount command, eliminating the search for separate credentials at cluster join and mount.

To use the Stateless Clients feature, a Content Software for File agent must be installed. Once this is complete, mounts can be created and configured using the mount command and can be easily removed from the cluster using the unmount command.

Note: To allow only Content Software for File authenticated users to mount a filesystem, set the filesystem auth-required flag to yes. For more information about mount authentication for organization filesystems, see Hitachi Content Software for File User Guide.

Assuming the Content Software for File cluster is using the backend IP of 1.2.3.4, running the following command as root on a client will install the agent:

curl http://1.2.3.4:14000/dist/v1/install | sh

On completion, the agent is installed on the client machine.

Run the mount command

Command:

mount -t wekafs

Use one of the following command lines to invoke the mount command (note, the delimiter between the server and filesystem can be either :/ or / ):

mount -t wekafs -o <options> <backend0>[,<backend1>,...,<backendN>]/<fs> <mount-point>
mount -t wekafs -o <options> <backend0>[,<backend1>,...,<backendN>]:/<fs> <mount-point>

Parameters

Name Type Value Limitations Mandatory Default
Options   See additional mount options below      
backend String IP/hostname of a backend host Must be a valid name Yes  
fs String Filesystem name Must be a valid name Yes  
mount-point String Path to mount on the local machine Must be a valid path-name Yes