What makes a `JuselessProject`? #2

New issue

Open

opened 2025-01-17 06:58:22 +00:00 by mih · 4 comments

mih commented

2025-01-17 06:58:22 +00:00

(Migrated from github.com)

It is not clear to me what all the semantics are that are loaded onto a project on juseless.

This is certainly a storage location, i.e. a place to find things.

Is it also related to a DUA, i.e. members of a project also get special permissions to access particular resources?

If both aspects are part of the semantics, we likely should separate them in data models. IOW, there needs to be a project-project which covers the organizational aspects (i.e. has members), and the place on the cluster we project data can be put.

It is not clear to me what all the semantics are that are loaded onto a project on juseless. This is certainly a storage location, i.e. a place to find things. Is it also related to a DUA, i.e. members of a project also get special permissions to access particular resources? If both aspects are part of the semantics, we likely should separate them in data models. IOW, there needs to be a project-project which covers the organizational aspects (i.e. has members), and the place on the cluster we project data can be put.

aqw commented

2025-04-01 13:26:55 +00:00

Owner

I asked Data and Platforms, and this was the initial response:

project name
storage location
quota
owner
juseless group name

Pulling from Ansible, this is an example of the information we have for each user account on Juseless:

  - name: archive_staging
    owner: root
    group: BnB
    mode: "1770"
    refquota: 2T
    compression: gzip-9

I asked Data and Platforms, and this was the initial response: - project name - storage location - quota - owner - juseless group name Pulling from Ansible, this is an example of the information we have for each user account on Juseless: ``` - name: archive_staging owner: root group: BnB mode: "1770" refquota: 2T compression: gzip-9 ```