[gw] Store publisher hostname as part of lease #3130
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
|
@cernvm-bot unittest |
|
@cernvm-bot cloudtest |
|
building for cloudtests finished: SUCCESS |
|
cloudtests finished: FAILURE |
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.
The publisher transmits its own hostname when asking for a new lease, which gets stored in the lease db. When the lease db is queried, available hostnames are returned.
This requires a schema upgrade of the lease db from v2 to v3. The gateway will do this automatically when opening a v2 db. Old publishers won't transmit a hostname, in which case the remote IP address from the HTTP request is used as a fallback. Old leases will not have a hostname set, in which case none is returned in the lease listing. Old gateways speaking to new publishers will ignore the transmitted hostname.