Difference between revisions of "Orion/Terminal Administration Guide/Shared Filesystem"
|Line 1:||Line 1:|
This guide contains information on managing the filesystem shared between the Orion server and
This guide contains information on managing the filesystem shared between the Orion server and server.
= Shared Filesystem =
= Shared Filesystem =
Revision as of 14:30, 15 January 2014
This guide contains information on managing the filesystem shared between the Orion server and Docker server.
The orion.ini file in the Orion distribution specifies a value -data which determines that value of the server workspace. If you unzip Orion into /opt/orion, by default this folder will be /opt/orion/eclipse/serverworkspace.
It is expected that the Orion server process is not running as root. Usually a non root user, such as orionuser in oriongroup is used to run the Orion server.
The server workspace is where each users projects and files are located. This folder must be accessible by both the Orion server and Docker server at the same location. So if the Orion server is reading and writing to /serverworkspace as specified on it's orion.ini, then the docker server also needs to be able to read and write the same folder at /serverworkspace.
In addition, the files would be be created and owned by the same orionuser (uid 1000) and group oriongroup (gid 1000) on both servers.
It should be noted that since the Docker daemon runs as root, the /serverworkspace will need to be accessable and readable by root on the Docker server.
Normally we do not want root to be able to read and write via NFS. We limit this access by having Docker server access /serverworkspace with a special configuration.
A way to specify in /etc/exports would be as follows:
In the case above, we specify anonuid and anongid so that all access is via the same Orion orionuser (uid 1000) and group oriongroup (gid 1000). To make sure that the Docker daemon can read and write within the Orion serverworkspace, a simple test if to make sure touch /serverworkspace/newfile.txt runs successfully as root on the Docker server and the resulting file is visible as an update on the Orion server and is owned by the userid 1000.