-
Notifications
You must be signed in to change notification settings - Fork 27
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
♻️ Polished and modernised agent service ⚠️ #6452
♻️ Polished and modernised agent service ⚠️ #6452
Conversation
…agent-to-handle-volumes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good from my side 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thx
…agent-to-handle-volumes
…:GitHK/osparc-simcore-forked into pr-osparc-rework-agent-to-handle-volumes
|
Volume removal is working as expected, for autoscaled nodes and classic nodes. |
Co-authored-by: Andrei Neagu <[email protected]>
Dev-ops⚠️
What do these changes do?
This service is way out of date and did not receive attention in years (2+). It currently causes a lot of pain for the platform and with the latest tools we've added it can be rewritten in a more sane and efficient manner.
This rewrite is also keeping an eye out for cost reduction, tries to avoid useless data uploads (unlike the previous version).
Highlights:
agent
nodes are targeted viaRPCNamespace
which is composed out ofdocker_node_id
+swarm_stack_name
agent
still maintains the task of backing up data that was left on the node by sidecars non terminated by director-v2agent
exposes Prometheus metrics regarding the number of volumes removed and the number of volumes that it backed up to S3dy-volrm
docker service which was created for each service for the purpose of removing it's volumesFollowup issues:
agent
service #6469Related issue/s
How to test
Dev-ops checklist⚠️