Assign Execution Server to Domains

Hello,

Will this feature be released soon?

We need to restrict jobs scheduled to run via CloudShell portal to be executed on specific execution server by domain, i.e., each domain should have specific execution server(s) which can be used to run the scheduled jobs.

Hi @Alona.G,

Thanks for your prompt response.

We've done exactly what you suggested. However, it will be useful to have the ability to assign specific Execution Server(s) to specific domain so that when "Any" is chosen, one of execution servers assigned to the domain of this test suite will run this job.

@alona.G your suggestion here is for TestShell, which wouldn't apply for Sandbox Orchestration or for asset Shells.

Still the advantage of being able to assign (or limit) execution servers to a specific domain is that it's a one time set up, just for the execution server. Vs. setting that value to each and every inventory item in that domain. In addition, by assigning it at the server level, you could allow for a pool of execution servers in the the domain.

Being able to assign it on a resource level is also useful, especially if there is some other software that is going to co-locate on the execution server that it might need. Just generally I would find the server level assignment easier to manage over the long run.

"If the idea of a domain is a group/set of resources, many times they share a specific network or network zone."

This is our exact usecase. We have Cloudshell Orchestration and shell scripts that need to run on specific execution servers due to network limitations. Happily, these limitations are also tied to Cloudshell domains, and so we would like to create a pool of execution servers for Domain X.

"the advantage of being able to assign (or limit) execution servers to a specific domain is that it's a one time set up, just for the execution server. Vs. setting that value to each and every inventory item in that domain"

I agree whole-heartedly with @ksaper@tsieda.com 's comments above. Having to set and maintain an execution selector attribute on every resource within a domain is challenging.

Hopefully, there is also a method that I'm not aware off for directing orchestration script execution to particular execution servers. Having 2 different solutions for directing script execution is non ideal; again arguing for the solution proposed here.

also see https://community.quali.com/idea/233/automatic-selection-for-execution-servers

Hi Kimo,

We are planning to allow Test Execution Servers to be associated with Domains in our future versions.

Thanks,

Shaul

Hi, I'm happy to update that we are planning to support associating test execution servers with domains in the near future. However, associating execution servers to domains won't be supported for the use case of running resources and sandbox commands .

@Alona Getzler - Asking for some additional clarity on this feature.

What exactly gets run by the 'Test Execution Servers'? Is that just TestShell Tests (and is that based on what blueprint a Job Suite is assigned to or from the Advanced/Domain option).

When you say 'running resources and sandbox commands' are not covered - Is that Shells? The majority of what is being handled now are generated by Python venv, created for shells and sandbox orchestration. Is that what is excluded here?