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
PTP fast event notifications,xref:../../telco_ref_design_specs/ran/telco-ran-ref-du-crs.adoc#ztp-ptpoperatorconfigforevent-yaml[PtpOperatorConfigForEvent.yaml],Yes,No
@@ -24,5 +25,7 @@ One-shot time sync,xref:../../telco_ref_design_specs/ran/telco-ran-ref-du-crs.ad
24
25
One-shot time sync,xref:../../telco_ref_design_specs/ran/telco-ran-ref-du-crs.adoc#ztp-99-sync-time-once-worker-yaml[99-sync-time-once-worker.yaml],No,Yes
Set RCU normal,xref:../../telco_ref_design_specs/ran/telco-ran-ref-du-crs.adoc#ztp-08-set-rcu-normal-master-yaml[08-set-rcu-normal-master.yaml],No,No
29
+
Set RCU normal,xref:../../telco_ref_design_specs/ran/telco-ran-ref-du-crs.adoc#ztp-08-set-rcu-normal-worker-yaml[08-set-rcu-normal-worker.yaml],No,No
27
30
SR-IOV related kernel arguments,xref:../../telco_ref_design_specs/ran/telco-ran-ref-du-crs.adoc#ztp-07-sriov-related-kernel-args-master-yaml[07-sriov-related-kernel-args-master.yaml],No,Yes
Copy file name to clipboardExpand all lines: modules/telco-ran-du-application-workloads.adoc
+8-1Lines changed: 8 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ DU worker nodes must have 3rd Generation Xeon (Ice Lake) 2.20 GHz or better CPUs
10
10
11
11
5G RAN DU user applications and workloads should conform to the following best practices and application limits:
12
12
13
-
* Develop cloud-native network functions (CNFs) that conform to the latest version of the link:https://test-network-function.github.io/cnf-best-practices/[CNF best practices guide].
13
+
* Develop cloud-native network functions (CNFs) that conform to the latest version of the link:https://test-network-function.github.io/cnf-best-practices-guide/[CNF best practices guide].
14
14
15
15
* Use SR-IOV for high performance networking.
16
16
@@ -21,3 +21,10 @@ Use other probe implementations, for example, `httpGet` or `tcpSocket`.
21
21
22
22
** When you need to use exec probes, limit the exec probe frequency and quantity.
23
23
The maximum number of exec probes must be kept below 10, and frequency must not be set to less than 10 seconds.
24
+
25
+
+
26
+
[NOTE]
27
+
====
28
+
Startup probes require minimal resources during steady-state operation.
29
+
The limitation on exec probes applies primarily to liveness and readiness probes.
0 commit comments