doc improvements#8150
Draft
calestyo wants to merge 3 commits into
Draft
Conversation
Based on dCache#8142, but still incomplete. Signed-off-by: Christoph Anton Mitterer <mail@christoph.anton.mitterer.name>
Signed-off-by: Christoph Anton Mitterer <mail@christoph.anton.mitterer.name>
Signed-off-by: Christoph Anton Mitterer <mail@christoph.anton.mitterer.name>
Contributor
Author
|
See also #8142 |
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
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.
Hey.
As for 34827be, please check someone whether there’s really no such command - I couldn't find it, but maybe
pools refreshis simply shared by pool-info and pool-history.As for 1e51e8b, this is based on @DmitryLitvintsev’s comments and my own look at the code (though I had a hard time to actually understand which paths are affected by which timeout properties).
The problem with it is that it's incomplete:
in particular:
/pools/{name}/usagesomewhere contains a copy of the/cellsdata for that pool, but that for example does not seem to be affected byfrontend.service.cell-info.timeoutbut rather byfrontend.service.pool-info.timeout. Orfrontend.service.pool-info.timeoutmight also affect/poolgroups//pools/contains a lot, but I've only really checked thatfrontend.service.pool-info.timeoutaffects/pools/{name}/usage.frontend.service.pool-history.timeoutis complete/exact.So maybe this should rather be only a draft, but in general I think these options are less useful if it's not really clear what exactly they do.