System Architecture for a Transparent Distributed File System

Next: Support for legacy applications Up: Transparent Distributed File System Previous: Transparent Distributed File System

System Architecture for a Transparent Distributed File System

When an application starts up, a global KernelAccessAPI::FileSystem is initialized by a shim library static intitalizer section. This object is named 'CurrentFileSystem' and bound remotely based on the following conditions:

If the 'CORBA_FS_IOR' environment variable is set, then the specified IOR is used to initialize the 'CurrentFileSystem' object.
If not, the IOR found in '/proc/fs/corba_fs_ior' is used. This IOR corresponds to the local kernel's FileSystem object.

This very simple system allows great power. This allows a user to have a program transparently access a remote file system, without the application knowing what is going on at all.