Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NSFS | NC | Allow Users to Choose fs_backend With Case Insensitive #7819

Open
shirady opened this issue Feb 14, 2024 · 2 comments
Open

NSFS | NC | Allow Users to Choose fs_backend With Case Insensitive #7819

shirady opened this issue Feb 14, 2024 · 2 comments
Labels
Non Containerized Non containerized NS-FS Type:Enhancement New suggestions for behaviours

Comments

@shirady
Copy link
Contributor

shirady commented Feb 14, 2024

Environment info

  • NooBaa Version: master
  • Platform: NC

Actual behavior

  1. Currently users must type the fs_backend with sensitive strings, for example: GPFS.

Expected behavior

  1. Allow users to type with case insensitive, for example gpfs.

Steps to reproduce

  1. Create an account with --fs_backend with gpfs (not GPFS): sudo node src/cmd/manage_nsfs account add --name <account-name> --new_buckets_path <path> --uid <uid> --gid <gid> --fs_backend gpfs
    Output:
{
  "error": {
    "code": "InvalidFSBackend",
    "message": "FS backend supported types are GPFS, CEPH_FS, NFSv4 default is POSIX"
  }
}

More information - Screenshots / Logs / Other output

none

@shirady shirady added Type:Enhancement New suggestions for behaviours NS-FS Non Containerized Non containerized labels Feb 14, 2024
@nimrod-becker
Copy link
Contributor

@shirady why is it needed? its like a well known name, in which case, case can be set to a specific one

@shirady
Copy link
Contributor Author

shirady commented Mar 11, 2024

@nimrod-becker Currently when a user types the fs_backend case insensitive he will get an error, for example:
sudo node src/cmd/manage_nsfs account update --name <account-name> --fs_backend gpfs (gpfs instead of GPFS).

{ "error": { "code": "InvalidFSBackend", "message": "FS backend supported types are GPFS, CEPH_FS, NFSv4 default is POSIX" } }
It's supposed to be a minor fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Non Containerized Non containerized NS-FS Type:Enhancement New suggestions for behaviours
Projects
None yet
Development

No branches or pull requests

2 participants