-
Notifications
You must be signed in to change notification settings - Fork 1
Release/v2.19.0 #577
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release/v2.19.0 #577
Changes from all commits
78d5f0d
a22d635
e0b432d
ba6407b
2a68874
6fa7142
b6b9576
195cff9
3feb555
8a9eab2
7f82001
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -51,11 +51,19 @@ We will configure the | |
| [delegated operators](./configuring-delegated-operators.md) | ||
| with GPUs. | ||
|
|
||
| In your `compose.delegated-operators.yaml`, under `.services.teams-do`, | ||
| add the `deploy.resource.reservation.devices` configuration. | ||
|
|
||
| The below will deploy a CPU-based delegated operator (`teams-do`) as well | ||
| as a GPU-based delegated operator (`teams-do-with-gpu`): | ||
| For most deployments, use the shipped GPU overlay | ||
| `compose.delegated-operators.gpu.yaml`, which includes the GPU | ||
| worker and its paired telemetry sidecar. Activate it alongside the CPU | ||
| worker profile (e.g. `COMPOSE_PROFILES=do-1,gpu`); see | ||
| [Configuring Telemetry](./configuring-telemetry.md#scaling-teams-do-with-telemetry) | ||
|
Comment on lines
+57
to
+58
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Fix profile example to match delegated-operator profile semantics. Line 57 uses 🤖 Prompt for AI Agents |
||
| for the full profile reference. | ||
|
|
||
| The snippet below contains custom inline example of | ||
| how to add a GPU-based delegated operator (`teams-do-with-gpu`) | ||
| alongside the standard `teams-do`. Pair it with telemetry by | ||
| adding a matching `teams-do-with-gpu-telemetry` sidecar. See | ||
| `docker/<auth-dir>/compose.delegated-operators.gpu.yaml` for an | ||
| example. | ||
|
|
||
| ```yaml | ||
| services: | ||
|
|
@@ -65,7 +73,7 @@ services: | |
| service: teams-do-common | ||
|
|
||
| teams-do-with-gpu: | ||
| image: voxel51/fiftyone-teams-cv-full:v2.18.1 | ||
| image: voxel51/fiftyone-teams-cv-full:v2.19.0 | ||
| command: > | ||
| /bin/sh -c "fiftyone delegated launch -t remote -n 'teams-do-with-gpu' -m" | ||
| environment: | ||
|
|
@@ -81,7 +89,7 @@ services: | |
| volumes: | ||
| - plugins-vol:/opt/plugins:ro | ||
| deploy: | ||
| replicas: ${FIFTYONE_DELEGATED_OPERATOR_WORKER_REPLICAS:-3} | ||
| replicas: 1 | ||
| resources: | ||
| reservations: | ||
| devices: | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fix typo in upgrade guidance sentence.
Line 43 reads awkwardly (
If you used on the <2.19 default...). Suggested wording:If you were using the pre-2.19 default of 3 workers, set COMPOSE_PROFILES=do-3.🤖 Prompt for AI Agents