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
Solution:
A TES task can be submitted to a TES server (with a backend parameter of platform set to the value windows) and the task will run on a windows server host. For backward compatibility purposes, the default value of platform will be linux.
Describe alternatives you've considered
Possibly use the docker image to select the platform and not require the backend parameter.
Code dependencies
Will this require code changes in:
CoA, for new and/or existing deployments? no
TES standalone, for new and/or existing deployments? yes
Terra, for new and/or existing deployments? no?
Build pipeline? yes
Integration tests? yes
Additional context
TBD
The text was updated successfully, but these errors were encountered:
Publish Tes.Runner project for windows in addition to linux in the build.
Modify the two current filenames related to the tes-runner in the TesApi.Web project to be four (two for each runner binary) and update BatchScheduler to upload both binaries as needed as well as change the content of IBatchScheduler.PoolMetadata.RunnerMD5 to include both runner binary hashes.
Create config-disks.cmd, config-docker.cmd, config-x-gpu.cmd (where x = a and/or n), & config-nvme.cmd scripts in the scripts folder (n is nvidia and a is amd).
Add the platform backend parameter as described above. Possibly detect windows docker images and set it accordingly (when not explicitly set).
Format the Path property of both FileInput and FileOutput per Windows conventions.
Generate Batch Environment Variable Names as appropriate for Windows (there are some differences).
Investigate automatically injecting both 32-bit and 64-bit Program Files system folders into the containers based on the docker image specified.
Investigate the ability to restrict IMDS from containers running in Windows.
Problem:
Running tasks in Windows® is needed.
Solution:
A TES task can be submitted to a TES server (with a backend parameter of
platform
set to the valuewindows
) and the task will run on a windows server host. For backward compatibility purposes, the default value ofplatform
will belinux
.Describe alternatives you've considered
Possibly use the docker image to select the platform and not require the backend parameter.
Code dependencies
Will this require code changes in:
CoA, for new and/or existing deployments?
noTES standalone, for new and/or existing deployments?
yesTerra, for new and/or existing deployments?
no?Build pipeline?
yesIntegration tests?
yesAdditional context
TBD
The text was updated successfully, but these errors were encountered: