mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
34 lines
1.6 KiB
Plaintext
34 lines
1.6 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * scalability_and_performance/telco_ran_du_ref_design_specs/telco-ran-du-rds.adoc
|
|
// * scalability_and_performance/telco_ref_design_specs/telco-ref-design-specs-overview.adoc
|
|
// * scalability_and_performance/telco_ref_design_specs/telco-hubs-rds.adoc
|
|
|
|
:_mod-docs-content-type: CONCEPT
|
|
[id="telco-deviations-from-the-ref-design_{context}"]
|
|
= Deviations from the reference design
|
|
|
|
Deviating from the validated telco core, telco RAN DU, and telco hub reference design specifications (RDS) can have significant impact beyond the specific component or feature that you change.
|
|
Deviations require analysis and engineering in the context of the complete solution.
|
|
|
|
[IMPORTANT]
|
|
====
|
|
All deviations from the RDS should be analyzed and documented with clear action tracking information.
|
|
Due diligence is expected from partners to understand how to bring deviations into line with the reference design.
|
|
This might require partners to provide additional resources to engage with Red Hat to work towards enabling their use case to achieve a best in class outcome with the platform.
|
|
This is critical for the supportability of the solution and ensuring alignment across Red Hat and with partners.
|
|
====
|
|
|
|
Deviation from the RDS can have some or all of the following consequences:
|
|
|
|
* It can take longer to resolve issues.
|
|
|
|
* There is a risk of missing project service-level agreements (SLAs), project deadlines, end provider performance requirements, and so on.
|
|
|
|
* Unapproved deviations may require escalation at executive levels.
|
|
+
|
|
[NOTE]
|
|
====
|
|
Red Hat prioritizes the servicing of requests for deviations based on partner engagement priorities.
|
|
====
|