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
For multiple deployments to be possible by the same Service (e.g., separate client and server VM deployments), we need to be able to pass a different deploymentName to each.
To do this, we should move deploymentName into an Environment arg rather than part of the Service config.
Additionally, deploymentName and other deploymentParameters should be templateable via globals (e.g., "deploymentName": "$experiment_id-server")
The text was updated successfully, but these errors were encountered:
#614 also should help with this since then we can make the vmName part of the deploymentName.
Related will be adding support for multiple worker instances (e.g., for parallel execution - #380)
bpkroth
added a commit
to bpkroth/MLOS
that referenced
this issue
Nov 30, 2023
For multiple deployments to be possible by the same Service (e.g., separate client and server VM deployments), we need to be able to pass a different
deploymentName
to each.To do this, we should move
deploymentName
into anEnvironment
arg rather than part of the Service config.Additionally,
deploymentName
and otherdeploymentParameters
should be templateable viaglobals
(e.g.,"deploymentName": "$experiment_id-server"
)The text was updated successfully, but these errors were encountered: