You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, name of our Dask components Dask cluster, Dask autoscaler, dashboard ingress and are hardcoded in the code. For example the code snippet at the end of this paragraph is taken from reana_workflow_controller.consumer.py. We should probably have a function (e.g def get_dask_cluster_name(worklow_id)) in reana-commons to get the name for these components and make it configurable to cluster admins. Then we can use it where necessary. (reana-server, reana-workflow-controller etc.). Besides, we may consider changing the names of Dask components since some of them are quite verbose and not easy to read. (e.g an ingress component dask-dashboard-ingress-reana-run-dask-acd35ec0-3b81-4eda-b252-dd0d6b180869)
Currently, name of our Dask components
Dask cluster, Dask autoscaler, dashboard ingress and
are hardcoded in the code. For example the code snippet at the end of this paragraph is taken fromreana_workflow_controller.consumer.py
. We should probably have a function (e.gdef get_dask_cluster_name(worklow_id)
) in reana-commons to get the name for these components and make it configurable to cluster admins. Then we can use it where necessary. (reana-server, reana-workflow-controller
etc.). Besides, we may consider changing the names of Dask components since some of them are quite verbose and not easy to read. (e.g an ingress componentdask-dashboard-ingress-reana-run-dask-acd35ec0-3b81-4eda-b252-dd0d6b180869
)The text was updated successfully, but these errors were encountered: