[To decide] Remove CONTROL_CONSTRUCT (live/cache) validation

[kmohr-soprasteria]

• Prathiba's proposal: remove the CONTROL_CONSTRUCT(cache/live) validation.
• Reason: If we miss to identify any discrepancy between the CoreModel of Microwave Devices and the CONTROL_CONSTRUCT schema of MWDI , then that will lead to a problem during operations. We have to update MWDI whenever there is a new module included in the Microwave devices. Maintaining the CONTROL_CONSTRUCT schema would be little difficult.

In the currently specified schema, we only included a top-level specification of the CC schema, as the MWDI shall just take what it gets from the Controller. It shall not have to check everything in detail.

Next step: discuss with Thorsten, if we want to disable the validation (this will only be for the cache/live CC, not for other validation parts).

[kmohr-soprasteria]

Thorsten's feedback:

what is meant by “rest would continue to be validated”? All other resource paths (LTP, equipment, etc.) work, only CC fails?

In this case, I would perhaps try to reduce the validation of the CC to key points and not switch it off completely.

When testing the CC, it could be relevant to check whether the MWDI forms the overall structure correctly again, even if subareas (e.g. individual changed LTPs) are updated separately.