Skip to content

fix(api): restart Duck Compose services as duck - #5

Open
jmbenlloch wants to merge 1 commit into
next-exp:masterfrom
jmbenlloch:fix/duck-compose-restarts
Open

jmbenlloch wants to merge 1 commit into
next-exp:masterfrom
jmbenlloch:fix/duck-compose-restarts

Conversation

@jmbenlloch

Copy link
Copy Markdown
Contributor

The API's Restart services action still connects as dateuser and invokes scripts under /home/dateuser/duck. Those commands do not reach the new NEXT100 deployment, which runs as duck in the duck-daq Compose project.

Connect as duck and restart only the requested gdc or ldc service with Docker Compose in /home/duck/duck-daq. Update the existing SSH mocks to assert the deployed user and exact commands. This is the minimal compatibility patch already deployed on the seven NEXT100 LDCs; it makes the new account and project path the restart defaults.

Validation:

  • Existing restart unit tests pass in the matching Duck HDF5/Blosc build image.
  • The deployed patch previously passed the full API, pkg, GDC and LDC test suites.
  • Live Restart services validation confirmed changed start times for all fourteen GDC/LDC containers before data taking.

The exchanger HDF5/Blosc repair changed its deployment image only; it did not change Duck/exchanger source code and is outside this PR. No credentials or host authorization files are included.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant