Merge pull request #96702 from vashirova/OADP-6127-load-concurrency

OADP-6127: Add Load Concurrency

Author: shdeshpa07

backup_and_restore/application_backup_and_restore/installing/installing-oadp-aws.adoc

@@ -54,6 +54,7 @@ include::modules/oadp-installing-dpa-1-3.adoc[leveloffset=+1]
 include::modules/oadp-configuring-node-agents.adoc[leveloffset=+2]
 include::modules/oadp-configuring-aws-md5sum.adoc[leveloffset=+1]
 include::modules/oadp-configuring-client-burst-qps.adoc[leveloffset=+1]
+include::modules/oadp-configuring-node-agent-load-concurrency.adoc[leveloffset=+1]
 include::modules/oadp-configuring-imagepullpolicy.adoc[leveloffset=+1]
 include::modules/oadp-configuring-dpa-multiple-bsl.adoc[leveloffset=+1]
 include::modules/oadp-enabling-csi-dpa.adoc[leveloffset=+2]

backup_and_restore/application_backup_and_restore/installing/installing-oadp-azure.adoc

@@ -41,6 +41,7 @@ include::modules/oadp-using-ca-certificates-with-velero-command.adoc[leveloffset
 // include::modules/oadp-installing-dpa-1-2-and-earlier.adoc[leveloffset=+1]
 include::modules/oadp-installing-dpa-1-3.adoc[leveloffset=+1]
 include::modules/oadp-configuring-client-burst-qps.adoc[leveloffset=+1]
+include::modules/oadp-configuring-node-agent-load-concurrency.adoc[leveloffset=+1]
 include::modules/oadp-configuring-imagepullpolicy.adoc[leveloffset=+1]
 include::modules/oadp-configuring-node-agents.adoc[leveloffset=+2]
 include::modules/oadp-enabling-csi-dpa.adoc[leveloffset=+2]

backup_and_restore/application_backup_and_restore/installing/installing-oadp-gcp.adoc

@@ -42,6 +42,7 @@ include::modules/oadp-using-ca-certificates-with-velero-command.adoc[leveloffset
 include::modules/oadp-gcp-wif-cloud-authentication.adoc[leveloffset=+1]
 include::modules/oadp-installing-dpa-1-3.adoc[leveloffset=+1]
 include::modules/oadp-configuring-client-burst-qps.adoc[leveloffset=+1]
+include::modules/oadp-configuring-node-agent-load-concurrency.adoc[leveloffset=+1]
 include::modules/oadp-configuring-imagepullpolicy.adoc[leveloffset=+1]
 include::modules/oadp-configuring-node-agents.adoc[leveloffset=+2]
 include::modules/oadp-enabling-csi-dpa.adoc[leveloffset=+2]

backup_and_restore/application_backup_and_restore/installing/installing-oadp-ibm-cloud.adoc

@@ -26,6 +26,8 @@ include::modules/oadp-setting-resource-limits-and-requests.adoc[leveloffset=+1]
 include::modules/oadp-configuring-node-agents.adoc[leveloffset=+1]
 // include the module for client burst and qps config
 include::modules/oadp-configuring-client-burst-qps.adoc[leveloffset=+1]
+// include module for loadConcurrency setting
+include::modules/oadp-configuring-node-agent-load-concurrency.adoc[leveloffset=+1]
 // include module for image pull policy setting
 include::modules/oadp-configuring-imagepullpolicy.adoc[leveloffset=+1]
 // include the module for configuring multiple BSL

backup_and_restore/application_backup_and_restore/installing/installing-oadp-mcg.adoc

@@ -46,6 +46,7 @@ include::modules/oadp-using-ca-certificates-with-velero-command.adoc[leveloffset
 // include::modules/oadp-installing-dpa-1-2-and-earlier.adoc[leveloffset=+1]
 include::modules/oadp-installing-dpa-1-3.adoc[leveloffset=+1]
 include::modules/oadp-configuring-client-burst-qps.adoc[leveloffset=+1]
+include::modules/oadp-configuring-node-agent-load-concurrency.adoc[leveloffset=+1]
 include::modules/oadp-configuring-imagepullpolicy.adoc[leveloffset=+1]
 include::modules/oadp-configuring-node-agents.adoc[leveloffset=+2]
 include::modules/oadp-enabling-csi-dpa.adoc[leveloffset=+2]

backup_and_restore/application_backup_and_restore/installing/installing-oadp-ocs.adoc

@@ -51,6 +51,7 @@ include::modules/oadp-using-ca-certificates-with-velero-command.adoc[leveloffset
 // include::modules/oadp-installing-dpa-1-2-and-earlier.adoc[leveloffset=+1]
 include::modules/oadp-installing-dpa-1-3.adoc[leveloffset=+1]
 include::modules/oadp-configuring-client-burst-qps.adoc[leveloffset=+1]
+include::modules/oadp-configuring-node-agent-load-concurrency.adoc[leveloffset=+1]
 include::modules/oadp-configuring-imagepullpolicy.adoc[leveloffset=+1]
 include::modules/oadp-configuring-node-agents.adoc[leveloffset=+2]
 include::modules/oadp-creating-object-bucket-claim.adoc[leveloffset=+2]

modules/oadp-configuring-node-agent-load-concurrency.adoc

@@ -0,0 +1,49 @@
+:_mod-docs-content-type: PROCEDURE
+// Module included in the following assemblies:
+//
+// * backup_and_restore/application_backup_and_restore/installing/installing-oadp-aws.adoc
+
+
+[id="oadp-configuring-node-agent-load-concurrency_{context}"]
+= Configuring node agent load concurrency
+
+[role="_abstract"]
+You can control the maximum number of node agent operations that can run simultaneously on each node within your cluster.
+
+You can configure it using one of the following fields of the Data Protection Application (DPA):
+
+* `globalConfig`: Defines a default concurrency limit for the node agent across all nodes.
+* `perNodeConfig`: Specifies different concurrency limits for specific nodes based on `nodeSelector` labels. This provides flexibility for environments where certain nodes might have different resource capacities or roles.
+
+
+.Prerequisites
+* You must be logged in as a user with `cluster-admin` privileges.
+
+
+.Procedure
+
+. If you want to use load concurrency for specific nodes, add labels to those nodes:
++
+[source,terminal]
+----
+$ oc label node/<node_name> label.io/instance-type='large'
+----
+
+. Configure the load concurrency fields for your DPA instance:
++
+[source,yaml]
+----
+  configuration:
+    nodeAgent:
+      enable: true
+      loadConcurrency:
+        globalConfig: 1 # <1>
+        perNodeConfig:
+        - nodeSelector:
+              matchLabels:
+                 label.io/instance-type: large # <2>
+          number: 3 # <3>
+----
+<1> Global concurrent number. The default value is 1, which means there is no concurrency and only one load is allowed. The `globalConfig` value does not have a limit.
+<2> Label for per-node concurrency.
+<3> Per-node concurrent number. You can specify many per-node concurrent numbers, for example, based on the instance type and size. The range of per-node concurrent number is the same as the global concurrent number. If the configuration file contains a per-node concurrent number and a global concurrent number, the per-node concurrent number takes precedence.