Support for GPFS immutable filesets #9159
Description
Is your feature request related to a problem? Please describe.
We are using Nooba to store users' files in the bucket with GPFS and migrate some of them to the tape when needed. Our GPFS fileset runs with immutability and in Noncompliant Mode, to prevent users from modifying file stubs, that are replacing actual files, that were being sent to the tape storage. When user access to the S3 storage, he can list and download the files, upload will fail with error 403 not Permitted. We have followed the logs and found out that nooba-core, when uploads file to the filesystem, creates a hard link. Probably to continue upload in case of interruption. And these hard links are prohibited in GPFS in any mode, except for Regular mode. But it does not support file immutability properly.
Describe the solution you'd like
When S3 bucket is created on the gpfs fileset with immutability, users can upload files to it. Maybe create a config option to upload files directly, without creating a hard link as an intermediate step.
Describe alternatives you've considered
This issue can be also solved by the IBM, or we can try to rewrite the nooba-core code, implementing the feature and send it upstream, but both will take much more time.