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.

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

Dask backend: pass labels to be set on run containers #4350

Closed
Tracked by #982 ...
sanderegg opened this issue Jun 12, 2023 · 1 comment · Fixed by #4429
Closed
Tracked by #982 ...

Dask backend: pass labels to be set on run containers #4350

sanderegg opened this issue Jun 12, 2023 · 1 comment · Fixed by #4429
Assignees
Labels
a:dask-service Any of the dask services: dask-scheduler/sidecar or worker a:director-v2 issue related with the director-v2 service
Milestone

Comments

@sanderegg
Copy link
Member

sanderegg commented Jun 12, 2023

In order to get more information on running containers and for tracking usage of resources:

  • add a free set of labels to be added on computational services containers
  • add the following labels: user_id, study_id, node_id (same as for dynamic services)
  • add product_name and simcore_user_agent
  • add cpu/ram limits
@sanderegg sanderegg transferred this issue from ITISFoundation/osparc-issues Jun 12, 2023
@sanderegg sanderegg added the a:dask-service Any of the dask services: dask-scheduler/sidecar or worker label Jun 12, 2023
@sanderegg sanderegg added this to the Watermelon milestone Jun 12, 2023
@sanderegg sanderegg added the a:director-v2 issue related with the director-v2 service label Jun 12, 2023
@sanderegg
Copy link
Member Author

sanderegg commented Jun 27, 2023

Container Labels used:

  • user_id
  • project_uuid
  • product_name
  • service_settings
    • reservation/limit for nano_cpus & memory_bytes
  • node_uuid

Also:

  • instance, id, image is used

ex. from dynamic service:

{
                "container_label_com_docker_compose_oneoff": "False",
                "container_label_com_docker_compose_project_working_dir": "/tmp/tmp_3seh6kp",
                "container_label_com_docker_compose_version": "1.29.1",
                "container_label_product_name": "osparc",
                "container_label_simcore_service_settings": '[{"name": "ports", "type": "int", "value": 8888}, {"name": "env", "type": "string", "value": ["DISPLAY=:0"]}, {"name": "env", "type": "string", "value": ["SYM_SERVER_HOSTNAME=sym-server_%service_uuid%"]}, {"name": "mount", "type": "object", "value": [{"ReadOnly": true, "Source": "/tmp/.X11-unix", "Target": "/tmp/.X11-unix", "Type": "bind"}]}, {"name": "constraints", "type": "string", "value": ["node.platform.os == linux"]}, {"name": "Resources", "type": "Resources", "value": {"Limits": {"NanoCPUs": 4000000000, "MemoryBytes": 17179869184}, "Reservations": {"NanoCPUs": 100000000, "MemoryBytes": 536870912, "GenericResources": [{"DiscreteResourceSpec": {"Kind": "VRAM", "Value": 1}}]}}}]',
                "container_label_simcore_user_agent": "puppeteer",
                "container_label_study_id": "46449cc3-7d83-4081-a44e-fc75a0c85f2c",
                "container_label_user_id": "43820",
                "container_label_uuid": "2b231c38-0ebc-5cc0-1234-1ffe573f54e9",
                "id": "/docker/58e1138d51eb5eafd737024d0df0b01ef88f2087e5a3922565c59130d57ac7a3",
                "image": "registry.osparc.io/simcore/services/dynamic/jupyter-smash:3.0.7",
                "instance": "gpu1",
                "job": "cadvisor",
                "name": "dy-sidecar-2b231c38-0ebc-5cc0-1234-1ffe573f54e9-0-jupyter-smash",
            }

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:dask-service Any of the dask services: dask-scheduler/sidecar or worker a:director-v2 issue related with the director-v2 service
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants