Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Replace APScheduler with Celery+Redis to decouple execution from the local eNMS #123

Open
shorton3 opened this issue Jan 25, 2019 · 1 comment
Open

Replace APScheduler with Celery+Redis to decouple execution from the local eNMS #123

shorton3 opened this issue Jan 25, 2019 · 1 comment
Assignees
@afourmy
Labels
enhancement status: accepted type: major feature
Milestone
eNMS 4.0

Comments

@shorton3
Copy link
Contributor

Currently, APScheduler couples the execution of services with the eNMS node, since APScheduler is only capable of managing local executions on a single instance. Celery+Redis would decouple the execution of services and create its own cluster of execution nodes. These would act as a load balanced pool and would be immune to a single node failure. This fixes the issue of what to do with scheduled tasks on a node that has failed.
@afourmy afourmy self-assigned this Jan 26, 2019
@afourmy afourmy added this to the eNMS 4.0 milestone Jan 26, 2019
@blackstrip
Copy link

But Celery has so many issues not resolve. Maybe you can try the Dramatiq(https://github.com/Bogdanp/dramatiq)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@afourmy afourmy

Labels
enhancement status: accepted type: major feature
Projects
None yet
Milestone
eNMS 4.0
Development

No branches or pull requests
3 participants
@blackstrip @afourmy @shorton3