Comment 4 for bug 2002394

Hello, Carlos. First of all, many thanks for looking into this bug.

The solution you proposed based on extra specs wouldn't fix the issue in our deployment. We don't enforce a cephfs volume module for all the shares of our users. Depending on their use case, they might need to define different modes. These different use cases is not something we isolate per share types.

Our ideal scenario would be:
* Manila creates a share with a default mode (a global default or default per share type, it doesn't matter).
* Once the share is created, Manila shouldn't touch the mode again.

This should avoid situations such as:
* user creates the share, modifies the mode (maybe he's not even aware of an enforced default for the mode) to his needs and the application is running perfectly. Then, we restart the services few months later for a configuration change and modes are reset, applications stop working... etc.

This is a similar situation with the share gid/uid. Manila doesn't currently worry about those settings and it doesn't set them during the life-cycle of the share. I think it should be the same for the mode.

What do you think?

Finally, if for whatever reason you decide to go ahead with the per-type mode enforcement, it would be good if this feature is optional and operators we can chose if Manila enforces the share mode or not.

Cheers,
Luis