Add INSUFFICIENT_RESOURCES reply #49
Open
Conversation
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
There currently is no standardized reply when no physical nodes available, no pyshical nodes with the requested number of interfaces available or it is not possible to create an additional VM. A new reply code would be useful for these cases, where the requested resources could not be allocated. This reply code would enable clients to easily detect this case. That would allow jFed to inform the user of the reason for the failure, and would allow "fedmon", the fed4fire FLS monitor, to flag these failures as a login test warning instead of a failure. (Feedback is needed about the name of the error code, the value, and the exact cases targeted by this error. The possible overlap with INSUFFICIENT_BANDWIDTH should also be handled.)
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.
There currently is no standardized reply when no physical nodes available, no pyshical nodes with the requested number of interfaces available or it is not possible to create an additional VM.
A new reply code would be useful for these cases, where the requested resources could not be allocated.
This reply code would enable clients to easily detect this case. That would allow jFed to inform the user of the reason for the failure, and would allow "fedmon", the fed4fire FLS monitor, to flag these failures as a login test warning instead of a failure.
(Feedback is needed about the name of the error code, the value, and the exact cases targeted by this error. The possible overlap with INSUFFICIENT_BANDWIDTH should also be handled.)