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.

Sign up for GitHub

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

Jump to bottom

Create pelican user and appropriate directories in RPM packaging #1860

Open
matyasselmeci opened this issue Dec 30, 2024 · 0 comments · May be fixed by #1856
Open

Create pelican user and appropriate directories in RPM packaging #1860

matyasselmeci opened this issue Dec 30, 2024 · 0 comments · May be fixed by #1856
Labels
cache Issue relating to the cache component container director Issue relating to the director component enhancement New feature or request infrastructure GitHub Actions, Release management, and CI origin Issue relating to the origin component registry Issue relating to the registry component

Comments

@matyasselmeci
Copy link
Contributor

See #1851

  1. Tweak the pelican RPMs to generated by goreleaser to create the pelican user as a system daemon user.
  2. Tweak the ownership of directories in the created RPM. Any directory that Pelican is expected to write to during runtime must be owned by the new pelican user. Off the top of my head, this includes:
    • The Prometheus database (/var/lib/pelican/monitoring).
    • The various configuration and stateful SQLite databases (/var/lib/pelican).
    • The webconfig file. NOTE: we might want to default this into a different location since it's currently in /etc/pelican; probably will need to change to /etc/pelican/web-config/web-config.yaml. Can defer for now.
    • Shoveler queue directory, /var/spool/pelican.
@matyasselmeci matyasselmeci added enhancement New feature or request infrastructure GitHub Actions, Release management, and CI cache Issue relating to the cache component origin Issue relating to the origin component director Issue relating to the director component registry Issue relating to the registry component container labels Dec 30, 2024
@matyasselmeci matyasselmeci linked a pull request Dec 30, 2024 that will close this issue
Open
@matyasselmeci matyasselmeci linked a pull request Dec 30, 2024 that will close this issue
Packaging: create pelican user and group and some directories for it #1856
Open
@matyasselmeci matyasselmeci mentioned this issue Dec 30, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
cache Issue relating to the cache component container director Issue relating to the director component enhancement New feature or request infrastructure GitHub Actions, Release management, and CI origin Issue relating to the origin component registry Issue relating to the registry component
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Packaging: create pelican user and group and some directories for it matyasselmeci/pelican
1 participant
@matyasselmeci