OSDF systemd services: use pelican-server everywhere#2478
Conversation
This avoids reliance on the magic config from the `osdf` binary. Fixes PelicanPlatform#2464.
|
Does this mean we're using the |
|
@jhiemstrawisc we're already doing so for the origin:
Is there a reason we shouldn't? |
|
Roping in @h2zh on this -- we just merged a change that enables CGO in the I don't have a full grasp of potential consequences here, but I think enabling CGO means we lose having a static binary (haven't confirmed this) and need to worry more about distribution. |
|
I'll follow up with a note that we do eventually want |
|
One concern I have for this change is - now with |
|
Following up Howard's comment: |
|
@jhiemstrawisc @h2zh can we just change the origin + director + registry services to use the pelican binary until you guys are ready? I checked the Dockerfile and that looked fine. Separately, we should probably move the |
|
I second this plan. Now we should make |
|
That sounds like a good plan to me. I'm guessing we should hold the 7.18 release for this? |
|
Noting here that the CGO broke build infrastructure so that change is being rolled back. The change in this PR is now clear to go through with the 7.18 release |
This avoids reliance on the magic config from the
osdfbinary.