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

fix: add deployment steps for updating glados' trin node #1119

Closed
wants to merge 1 commit into from

Conversation

mrferris
Copy link
Collaborator

What was wrong?

Trin deployment steps leave glados's trin node un-updated

To-Do

@mrferris mrferris requested a review from njgheorghita January 26, 2024 20:35
Copy link
Member

@KolbyML KolbyML left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Trin on glados hasen't been updated in 6 weeks. These instructions don't work to pull the latest image of Trin. I found the fix and will make a PR on the cluster repo.

I think instead of sshing in we should just use anisble like we do for trin.
For

  • consistency
  • reproducibility
  • etc

@KolbyML
Copy link
Member

KolbyML commented Jan 28, 2024

Here is a PR to supercede this one #1120

I believe it is best practice to do glados deploys through ansible instead of sshing and running commands. Also keeping our deployment structure consistent is important as well. Excluding the issue in the ansible and in this PR's instructions here which won't update the trin node. Which is a seperate issue introduced when we added fluffy support to glados's docker compose file

@mrferris mrferris closed this Jan 29, 2024
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.

2 participants