We have a situation where an enormous set of template files (several tens of gigabytes) is required by multiple pieces of software, from multiple vendors. The applications want to open these template files the same way they opens any project file, i.e. read-write.
- It's a burden on the network infrastructure to have users copy the template hive locally to their Linux workstations (RHEL6 and RHEL7 only)
- The software does not make changes to the template files
- If the files are write-protected on the server, the software throws an error
- If the NFS volume is mounted read-only and the files are given write permission, the software throws an error
- If we give write permissions on files on a writable NFS volume we can no longer trust the template files to be pristine
Short of eating that infrastructure burden, I'm looking for a way to fake out the software by making the NFS volume appear writable, giving the files write permissions, but not actually committing the changes.
I'm reminded of "journal rewind" tools like Deepfreeze on Windows NTFS volumes. Is there a similar hack for NFS mounts? When giving this question tags, "unionfs" popped up as a match for "nfs". That's also a method for allowing "fake writes" to Live CDs. I'm heading that direction now, but I hope someone's already done this.
Another constraint is that users are often required to use legacy versions of the software, from multiple vendors; which means a bugfix from the vendors is only going to help the newest version(s).