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

Put the dynamically-linked pelican-server binary in the pelican-server RPM #1896

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

matyasselmeci
Copy link
Contributor

Closes #1855

Also updates the SystemD files for the cache and origin to use pelican-server instead of pelican or osdf. For consistency with the current images, the director and registry .service files continue to use pelican or osdf. Note that osdf-cache and osdf-origin no longer run a program with the magic osdf prefix, so they will be getting generic config unless overridden.

…origin

Note that this changes the osdf-cache and osdf-origin to use a binary
not named "osdf*", meaning that any osdf-specific config will have to
come from a config file.

For consistency with the images, the registry and director continue to
use "pelican" or "osdf" as appropriate.
The configs we ship require config.d support, introduced in 7.11
@matyasselmeci matyasselmeci added this to the v7.13.0 milestone Jan 15, 2025
@matyasselmeci matyasselmeci added cache Issue relating to the cache component origin Issue relating to the origin component labels Jan 15, 2025
@matyasselmeci matyasselmeci modified the milestones: v7.13.0, v7.14 Jan 22, 2025
@matyasselmeci matyasselmeci modified the milestones: v7.14, v7.15 Feb 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cache Issue relating to the cache component origin Issue relating to the origin component
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Package pelican-server binary
1 participant