-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
Detach monitor functionality to other container with separate supervisor #51
Comments
Service discovery tool: https://www.consul.io/discovery.html |
And the Github repo: https://github.com/hashicorp/consul |
The service manager communicates with a DNS-based service discovery module (consul) to register the microservices for the different containers. The discovery happens on microservice boot time. Then it (the manager) can be instructed by the frontend or other modules to control (start/stop/restart) the disaggregated microservices by addressing their Supervisor Endpoints via XMLRPC. Note that the user does not change anything in its custom supervisor configuration; simply the 5 detectors (for example) will run in their own separate container. If this is fine as an approach, we can start thinking of disaggregating more and more microservices in stages (e.g., detection, then db, etc.). |
Note that since with this arch we will have a supervisor running per container, we need to break down the initial sup conf into several files and map them to the different containers. So we will need a parser and conf generator for sup confs. |
After discussion with @slowr @pgigis , the following steps need to be made:
Note that the hash from @slowr if possible check if you can create a prototype of this discussed workflow for a single container (e.g., by isolating/detaching detection or monitor; you can start with monitor). |
@slowr Since the first part is done, but the redis queries are pending, I am moving this to 1.4.0 for completion. |
I am going to close this ticket as the first iteration already happened. The split of the services to a separate container needs a bigger core change. |
Is your feature request related to a problem? Please describe.
The taps on the backend compete for resources with the detection and database. We need to check if we can separate them in a different container for scalability reasons.
Describe the solution you'd like
Without changing anything in the configuration logic and control mechanisms (e.g., UI monitor on/off), need to check if we can detach and monitor.py taps from backend
and clone listener.py and supervisor in a new "taps" container
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: