Refresh Nova's rolling upgrade steps #2
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
JohnGarbutt
force-pushed
the
nova-upgrade-review
branch
from
ed6c78c
to
1205031
Compare
Made it clear what bits of the upgrade process are expected to cause control plane downtime. There should be no data plane downtime. Note the addition of the SIG_HUP and the upgrade pins, to allow for a rolling restart of the nova-compute services.
JohnGarbutt
force-pushed
the
nova-upgrade-review
branch
from
1205031
to
238e236
Compare
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.
Made it clear what bits of the upgrade process are expected to cause
control plane downtime. There should be no data plane downtime.
Not the addition of the SIG_HUP and the upgrade pins, to allow for a
rolling restart of the nova-compute services.