Disable selection of backend in recipe compute configuration

Support_user
Level 1
Disable selection of backend in recipe compute configuration

How to set containerized environment as the only option available for the user?
We wanted to disable the selection of backend from the options so that none of the jobs submitted will go to server backed.

Container_Selection.jpg


Operating system used: Linux RHEL

0 Kudos
3 Replies
Turribeach

I don’t think restricting this is currently possible but I will be glad to be proved wrong as we may want to do this in the very near future. The best alternatives I can think of are:

  1. Use the Python API to programmatically and regularly move recipes to execute in containers 
  2. Implement cgroups with a very low CPU allowance so users are forced to select containers as cgroups won’t allow them to run any recipe locally 

Makes sense?

0 Kudos
Support_user
Level 1
Author

We already kept a lower configuration for cgroups to control the backend server access. But this was needed when environment is getting more and more users added. Eg : offload every ones compute to AKS so that backend servers & application performance/availability not impacted. 

0 Kudos

Well as I said I don't you can restrict the list. However you are able to set a default cluster and execution config in Settings > Compute & Scaling > Containerized Execution. This will basically be applied by default to all projects and recipes unless the user customises the settings since the default project setting for cluster selection is "Use DSS global cluster settings" and for exec config "Inherit instance default". Feel free to raise a Product Idea to be able to restrict the execution of recipes in the DSS backend server.

0 Kudos