-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add API to help schedule next test run #202
Comments
New idea - I think mlab-ns should return this as part of its response. Then we will have more influence over this on the server side, and can make adjustments, for example, in response to load. |
@gfr10598 and @stephen-soltesz want to talk about the right path forward here. |
This makes sense if there as also an easy way to ask for just the recommended schedule, w/o asking for current servers. Should the recommended time depend on the precise query? Please include me in the conversation. |
I'm increasingly inclined to believe that we should not add this feature to this client and that (1) we should document the best practices and (2) leverage mlab-ns as @gfr10598 suggests. Unless there are objections, I'd like to close this issue in a week or so. |
@bassosimone I've migrated this issue to the mlab-ns repo since the desire sounds like we want some mlab-ns support for scheduling. |
Related to the M-Lab six hours incident. Suggested by @mattmathis and @gfr10598.
BTW, there is code for doing that in the ndt7 spec.
Moved here from measurement-kit/engine#8
The text was updated successfully, but these errors were encountered: