keystone and supervisor config modify#445
Open
like-inspur wants to merge 2 commits intomonasca:masterfrom
Open
keystone and supervisor config modify#445like-inspur wants to merge 2 commits intomonasca:masterfrom
like-inspur wants to merge 2 commits intomonasca:masterfrom
Conversation
…recreated, keystone pod ip will change, and data stored in mysql will not match real keystone pod. So it should use keystone service name
…pervisor deployment yaml
This file contains hidden or 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
1 participant
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.
So far keystone init mysql user keystone pod ip, when pod restart or recreated, keystone pod ip will change, and data stored in mysql will not match real keystone pod. So it should use keystone service name
These variables are initd by thresh job, so they are not needed in supervisor deployment yaml