This repository has been archived by the owner on Sep 12, 2022. It is now read-only.
Run monitor_machines once each night rather than every 30 mins #625
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
cdosborn
force-pushed
the
celery-periodic-task-timing
branch
from
afc91e0
to
d6320dc
Compare
|
Just moved this branch onto v33 so that it'll be in the next release. |
cdosborn
approved these changes
Jun 15, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
This task is taking >1 hour to run in production for each provider, doesn't make sense to run every 30 mins. Image import via this method is rare, and
monitor_machinescan always be run on-demand if needed. See #atmosphere_issues channel in Jetstream Slack from morning of 2018-06-15.Checklist before merging Pull Requests
New test(s) included to reproduce the bug/verify the featureDocumentation created/updated (include links)If creating/modifying DB models which will contain secrets or sensitive information, PR to clank updating sanitation queries inroles/sanitary-sql-access/templates/sanitize-dump.sh.j2New variables supported in ClankNew variables committed to secrets repos