Open
Conversation
Adding a celery task manager that will become the basis for much of the future POCS operation. Maybe. ;) For now the simple command line utilities will start and stop the messaging and results backend using the python docker sdk.
Codecov ReportBase: 83.08% // Head: 73.04% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## develop #1167 +/- ##
============================================
- Coverage 83.08% 73.04% -10.05%
============================================
Files 86 96 +10
Lines 7425 8072 +647
Branches 635 896 +261
============================================
- Hits 6169 5896 -273
- Misses 1083 2036 +953
+ Partials 173 140 -33
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
…int. The `name` of the service is auto-created.
…her than a dict.
* Use `redis` for both messaging and results to make things simple. * Adding a `start-worker` command to the cli that will start a celery work with either full namespace or relative to `panoptes.pocs.utils.service`.
…ostly used by the cli.
Adding POCS specific errors
* Use the `SiteDetails` dataclass.
… method that takes entire observation in one call.
* config server * power monitor * weather reader.
* Use `htpdate` instead of `ntpdate`. Use `google.com`. Run for all installs, not just RPi. * auto discover the router ip address and use that to set the NFS share for the host. * Install `supervisor` (config file coming). Remove systemd services. * Remove old docker pulls.
This was referenced Aug 19, 2022
Merged
Merged
Merged
This was referenced Aug 20, 2022
Merged
* Rename `task` to `controller`. Add the `worker`, which is a copy of what comes from `pocs-camera`.
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.
Adding a celery task manager that will become the basis for much of the future POCS operation. Maybe. ;)
For now the simple command line utilities will start and stop the messaging (rabbitmq) and results backend (redis) using the python docker sdk.
Description
The
celerydistributed task manager will allow for a number of tasks to be run in a distributed manner. For the POCS core this can include things that need knowledge of the time (e.g. startup at sunset rather than issue a sleep timer at sundown), but can also start to serve as the basis for distributed hardware control (e.g. the forth-coming task-based gphto2 camera class).