Pods status benchmarking #809
Open
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
AndriiPovsten
force-pushed
the
Pods-status-benchmarking
branch
2 times, most recently
from
23df409
to
5ec0474
Compare
…_workflow function
AndriiPovsten
force-pushed
the
Pods-status-benchmarking
branch
from
5ec0474
to
f6273ba
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.
The current script allows the user to see the status of all the pods in the submitted workflow.
Theoretically, this script should also be able to check if a pod belongs to the same workflow by using
reana-client logs -w name of current workflow, but this needs further development and testing.In this script, the user needs to provide the collected live logs created using
kubectland then the necessary data will be taken from the file and plotted for a better understanding of the time taken for each pod state. Which is outside the user's eyes.