Skip to content

README.md

Latest commit

 

History

History
71 lines (50 loc) · 2.84 KB

README.md

File metadata and controls

71 lines (50 loc) · 2.84 KB
Raw

On-demand sandbox activities sample

This sample shows how to run selected Durable Task activities in DTS-managed on-demand sandboxes.

The sample is intentionally split into two projects:

Path Purpose
shared/ Defines activity identity constants shared by the main app and remote worker.
main-app/ Runs locally or in a normal app host. It declares the on-demand sandbox activity and starts one hello orchestration.
remote-worker/ Builds the container image that DTS starts inside a sandbox. It contains the remote hello activity.

Build

dotnet build .\samples\on-demand-sandbox\main-app\main-app.csproj
dotnet build .\samples\on-demand-sandbox\remote-worker\remote-worker.csproj

Build the remote worker image

Run from the repository root:

$image = "<acr-name>.azurecr.io/dts-ondemand-sandbox-sample:<tag>"
docker build -f .\samples\on-demand-sandbox\remote-worker\Containerfile -t $image .
docker push $image

Run a hello orchestration

After pushing the remote worker image, set these environment variables:

$env:DURABLE_TASK_SCHEDULER_CONNECTION_STRING = "Endpoint=https://<scheduler-endpoint>;TaskHub=<task-hub-name>;Authentication=DefaultAzure"
$env:DTS_SANDBOX_CONTAINER_IMAGE = "<container image reference>"
$env:DTS_SANDBOX_IMAGE_PULL_UMI_CLIENT_ID = "<image-pull UMI client ID>"
$env:DTS_SANDBOX_SCHEDULER_UMI_CLIENT_ID = "<scheduler UMI client ID>"

For Authentication=DefaultAzure, sign in with Azure CLI or configure another supported Azure identity before running the main app.

The worker profile class declares the image, CPU, memory, max concurrency, and on-demand sandbox activity identities with options.AddActivity(name, version). The main app and remote worker both use the shared/SandboxActivities.cs constants so the workerProfile and worker registration stay in sync.

You can also set the scheduler connection string in main-app/appsettings.json:

{
  "DURABLE_TASK_SCHEDULER_CONNECTION_STRING": "Endpoint=https://<scheduler-endpoint>;TaskHub=<task-hub-name>;Authentication=DefaultAzure"
}

Then run the main app:

dotnet run --project .\samples\on-demand-sandbox\main-app\main-app.csproj

Expected output includes the on-demand sandbox activity result:

Runtime status: Completed
Output: "hello locally: on-demand-sandbox-sample; hello remotely from <sandbox> pid=<pid>: on-demand-sandbox-sample"

Use the Durable Task Scheduler dashboard's On-demand sandbox preview tab to inspect sandboxes and stream runtime logs.

The remote worker image does not need customer-provided DTS runtime settings. DTS injects the scheduler endpoint, task hub, worker profile, capacity, sandbox provider, and sandbox identifier when it starts the sandbox. The worker reports the activity identities registered in the image when it connects.