CirrusGrid PaaS allows sharing data over the NFS protocol between the NFS server (where the files are physically located) and clients (gain access to the remote data as if it was kept locally). Herewith, the configurations required to set up a share varied based on the following condition:
both instances are inside of the same CirrusGrid account – either export data from storage or mount data on the clients (the platform automatically handles the second operation)
one instance is outside of the platform – export data from external storage (described in this guide) and mount external data on the clients
Below, we’ll consider the configurations required to export data from the CirrusGrid Shared Storage Container to the external instance. The described flow is suitable for any NFS-based storage server.
First of all, to share data over the Internet, it’s required to attach a public IP address to your server:
Next, you need to declare the list of directories you’d like to share within the corresponding etc/exports file. In CirrusGrid PaaS, it can be easily accessed with the Configuration button in the Exports section of the built-in Configuration File Manager.
Here, the following format should be used:
{directory} {server}([option],[option],..)
where:
Note: In case your Jelastic instance does not have an external address attached, you can alternatively use the IP of the appropriate host. It could be obtained by connecting to the container via SSH and executing the following command:
curl ifconfig.co
[option] – some additional parameters to describe the access permissions, where the main ones are:
Tip: For additional security, you can configure the corresponding etc/hosts.allow and etc/hosts.deny files to manage a list of hosts that NFS server can work with.
Also, an additional fsid option should be obligatory added to the export configuration string. For example, the value of this parameter can be randomly generated with the next command:
systemctl restart nfs-server
As a result, the export string would be similar to the following one:
Don’t forget to Save the changes you’ve made.
exportfs -ra
Tip: This can be done through the console as well:
iptables -I INPUT -p tcp -m multiport --dports 111,2049 -s {NFS_client} -j ACCEPT iptables -I INPUT -p udp -m multiport --dports 111,2049 -s {NFS_client} -j ACCEPT
So, if needed, execute the following command on your storage server to adjust the rights:
chown {uid}:{gid} {path}
Here:
That’s all! Your data storage server is ready, so you can return to the client instance and start mounting.
Powered by BetterDocs
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.