Fuse pricing units and service resources #4958
Labels
a:dask-service
Any of the dask services: dask-scheduler/sidecar or worker
a:director-v2
issue related with the director-v2 service
a:dynamic-sidecar
dynamic-sidecar service
a:webserver
issue related to the webserver service
We currently have a bit of duplicate functions since pricing units came in.
services (both dynamic and computational) rely on service_resources to run. they define limits and reservations in terms of CPUS, RAM, VRAM, etc... to run the services.
pricing units, on the other hand now define on which hardware these services shall run, which implicitely define service resources.
These 2 types of service limitations now live in parallel and should be fused together.
Tasks
The text was updated successfully, but these errors were encountered: