On an AEN 4.x.x installation, you can choose the PATH for the /projects directory on the compute node to access user projects, content and environments. In a standard setup, each Compute node have its own /projects directory on the same server. The content can only be accessed through the corresponding compute node.
You can mount the NFS server as the /projects directory to store all of its contents.
Requirements:
AEN version 4 requires ACL directories to mount the file system with Posix ACL support. For AEN to run setfacl commands the filesystem needs to be mounted with nfsv3.
NOTE: AENv4 does not support NFSv4 with ACls.
If you need to setup your NFSv3 server, you can mount it on the compute nodes:
mount -t nfs -o nfsvers=3 nfs_server_url:/nfs/directory /projects
Additonal considerations:
You can change the path of the /projects directory by editing the/opt/wakari/wakari-compute/etc/wakari/wk-compute-launcher-config.json file and changing the "projectRoot" key to the full path of the directory. You must restart the wakari-compute service for the changes to take effect:
sudo service wakari-compute restart
Using Active Directory/LDAP for user management:
To use multiple compute nodes, you need a common identity management source such as Active Directory or LDAP rather than letting AEN manage the user accounts.
You also need configure AD/LDAP to use the same UIDs across all of the systems so that users have correct permissions to access their projects on different nodes.