Online image change: maintain status message #135
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fills in the Status.ImageChangeStatus message as we progress through the online image change. It also reworks the status message updates we do for offline image change to share the same infrastructure.
I'm also including a change to keep the ssh key in the Vertica container stable between builds. The ssh key is just used for communication between the Vertica nodes. A stable key allows Vertica nodes from a different container image to be able to communicate. This becomes an issue when doing an online image change because the Vertica pods are either running the old or new image, yet they all have to talk to each other.