The NCI Global Filesystems (commonly known as gdata) can be accessed from the Nirin cloud by way of NFS gateways, which mount the gdata filesystems and provide NFS exports which are accessible from the cloud. Projects with gdata resource allocations can request access via the helpdesk.
Please note that NCI requires written approval by a project CI before NFS access to that project's gdata directories can be granted, and when any changes are made to the export.
NFS exports can be either read-only (the preferred approach whenever possible) or read-write. In either case all access to the underlying gdata filesystem will be squashed to a single user
gdata NFS export requests should be made via the NCI helpdesk. Requests should indicate what project the request relates to, what kind of access is required, and who the approving CI is. The CI should provide their written approval in a comment in the ticket.
The ticket will be processed in two steps: firstly, the cloud team will configure the project network to support gdata NFS access; once that is done the ticket will be forwarded to the storage team to create the actual NFS exports, and the ticket will be resolved. Once the ticket is resolved the NFS export should be accessible.
Once the exports are in place, mounting the exported filesystem can be done using a command like the following:
# mount -t nfs gdata4.cloud.nci.org.au:/mnt/gdata4/ab12 /mnt/ab12
Here the project is ab12, and the export is from the the gdata4 filesystem. The general form is:
# mount -t nfs <gdata-filesystem>.cloud.nci.org.au:/mnt/<gdata-filesystem>/<project>/<optional-subdirectory> <local-mountpoint>
In order to configure an instance so that the NFS exports are mounted automatically you can add a line for each mount to the /etc/fstab
file:
<gdata-filesystem>.cloud.nci.org.au:/mnt/<gdata-filesystem>/<project>/<optional-subdir> <local-mountpoint> nfs defaults
Note: mount options can also be specified, both on the command line and in the fstab
entry, however they are generally unnecessary - the NFS client and server will negotiate options during the mount process, and generally the result will be the optimal set of options. Tuning mount options is possible, but without some care this can lead to performance degradation.
Note: Unless specifically instructed only the round-robin name should be used for mounting an NFS export.
Filesystem | Server | IP Address | Round-robin Entry Name |
---|---|---|---|
gdata1a | gdata1a-nfs01.cloud.nci.org.au | 10.2.0.2 | gdata1a.cloud.nci.org.au |
gdata1a | gdata1a-nfs02.cloud.nci.org.au | 10.2.0.3 | gdata1a.cloud.nci.org.au |
gdata1a | gdata1a-nfs03.cloud.nci.org.au | 10.2.0.4 | gdata1a.cloud.nci.org.au |
gdata1b | gdata1b-nfs01.cloud.nci.org.au | 10.2.0.5 | gdata1b.cloud.nci.org.au |
gdata1b | gdata1b-nfs02.cloud.nci.org.au | 10.2.0.6 | gdata1b.cloud.nci.org.au |
gdata1b | gdata1b-nfs03.cloud.nci.org.au | 10.2.0.7 | gdata1b.cloud.nci.org.au |
gdata3 | gdata3-nfs01.cloud.nci.org.au | 10.2.0.11 | gdata3.cloud.nci.org.au |
gdata3 | gdata3-nfs02.cloud.nci.org.au | 10.2.0.12 | gdata3.cloud.nci.org.au |
gdata4 | gdata4-nfs01.cloud.nci.org.au | 10.2.0.14 | gdata4.cloud.nci.org.au |
gdata4 | gdata4-nfs02.cloud.nci.org.au | 10.2.0.15 | gdata4.cloud.nci.org.au |
gdata4 | gdata4-nfs03.cloud.nci.org.au | 10.2.0.16 | gdata4.cloud.nci.org.au |
gdata5 | 10.2.0.17 10.2.0.18 10.2.0.19 | gdata5.cloud.nci.org.au | |
gdata6 | 10.2.0.20 10.2.0.21 10.2.0.22 | gdata6.cloud.nci.org.au |