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

Add information on "recommended knowledge" for managing data within LTS allocations. #671

Open
wwarriner opened this issue Feb 5, 2024 · 0 comments · May be fixed by #832
Open

Add information on "recommended knowledge" for managing data within LTS allocations. #671

wwarriner opened this issue Feb 5, 2024 · 0 comments · May be fixed by #832
Assignees
Labels
fabric: storage Docs related to storage feat: article New article or section request
Milestone

Comments

@wwarriner
Copy link
Contributor

What would you like to see added?

This is a first attempt and it probably needs to be finessed. The intent is to make it clear that (1) LTS requires a greater understanding of technology details than most aspects of our system, and definitely more than GPFS; (2) the allocation owner doesn't need to manage the space alone and can add "Data Stewards"; (3) "Data Stewards" should be tech-savvy; (4) "Data Stewards" should be trustworthy due to having full control of the allocation.

This is taken from a service request I responded to recently.

Permission management and access control for LTS works differently than for GPFS (Cheaha filesystem). With GPFS, we give individuals permission to access the space at the top level, hence the need for the list of people. With LTS, data is stored as objects (like files) within buckets (like directories/folders), and access is controlled by policies applied to buckets. Buckets may only be created by people with full control of the allocation. By default, the only person with the ability to create and delete buckets is the owner. However, we can grant "Data Steward" permissions to additional people. These stewards will also have full control of the allocation, allowing them to manage buckets, potentially easing day-to-day operations. At this time, managing LTS buckets and policies requires an understanding of the terminal, a couple of command-line applications, and a willingness to learn JSON and parts of the Amazon AWS S3 API.

So, if you do not wish to manage the LTS space yourself, we recommend granting Data Steward permissions to someone who is both trustworthy and has knowledge of, or willingness to learn, the above technologies. Here are the choices summarized:

  1. The owner, $owner, can manage buckets themselves.
    -- OR --
  2. $owner can grant full control of the allocation to one or more other people to allow them to manage buckets.

Which is preferred?

@wwarriner wwarriner added fabric: storage Docs related to storage feat: article New article or section request labels Feb 5, 2024
@bdu-birhanu bdu-birhanu added this to the Sprint 25-01 milestone Oct 9, 2024
@bdu-birhanu bdu-birhanu linked a pull request Oct 9, 2024 that will close this issue
@bdu-birhanu bdu-birhanu self-assigned this Oct 9, 2024
@wwarriner wwarriner modified the milestones: Sprint 25-01, Sprint 25-02 Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fabric: storage Docs related to storage feat: article New article or section request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants