From 490acb9eb2699d6b1d5e6b37cbd9a9392cd22e43 Mon Sep 17 00:00:00 2001 From: Dean Roehrich Date: Fri, 5 Jul 2024 11:06:50 -0500 Subject: [PATCH] Refer to RequiredDaemons from the data-movement doc Signed-off-by: Dean Roehrich --- docs/guides/data-movement/readme.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/guides/data-movement/readme.md b/docs/guides/data-movement/readme.md index cf6c345..6381ff3 100644 --- a/docs/guides/data-movement/readme.md +++ b/docs/guides/data-movement/readme.md @@ -90,6 +90,8 @@ The `CreateRequest` API call that is used to create Data Movement with the Copy options to allow a user to specify some options for that particular Data Movement. These settings are on a per-request basis. +The Copy Offload API requires the `nnf-dm` daemon to be running on the compute node. This daemon may be configured to run full-time, or it may left in a disabled state if the WLM is expected to run it only when a user requests it. See [Compute Daemons](../compute-daemons/readme.md) for the systemd service configuration of the daemon. See `RequiredDaemons` in [Directive Breakdown](../directive-breakdown/readme.md) for a description of how the user may request the daemon, in the case where the WLM will run it only on demand. + See the [DataMovementCreateRequest API](copy-offload-api.html#datamovement.DataMovementCreateRequest) definition for what can be configured.