Remove obsolete error message at p1CalculateUtilization (Fixes #230)

[openBackhaul]

Please, implement accordingly, merge the pull request and delete the openBackhaul/issue230 branch.
Many thanks in advance.

[latta-siae]

Hi @openBackhaul ,

i think you must decouple the PR about files

• p1IterateAiPmSlices
• p1CalculateUtilization

Why?
Because p1CalculateUtilization has been change many things:

• Business logic
• aggregation-group now is not mandatory
• uuidOfEthernetContainer new parameter to handle

So then this must be renamed as p2CalculateUtilization related of DPMDP 1.1.0
p2IterateEcPmSlices. If that is stick with p1CalculateUtilization the workflow will not work properly.

See the workflow v1.0.0 and v.1.1.0

[kmohr-soprasteria]

Hi Lorenzo,

to me it looks reasonable to have an own PR for the removal of the unneeded error message in p1IterateAiPmSlices (#228).

As for p2IterateEcPmSlices and p1CalculateUtilization - you correctly pointed out that the required inputs to calculateUtilization have changed.
We could now either have a p1CalculateUtilization 1.1.0 or a p2CalculateUtilization 1.0.0.
The logic inside the function is now a bit different, but not that much. So possibly Thorsten had in mind to implement a 1.1.0 version of it in addition to the 1.0.0 implementation.

I would suggest, you start with implementing the changes and we wait for Thorstens confirmation on what approach he would like to take.

Br
Katharina

[openBackhaul]

Changes in p1IterateAiPmSlices occured in this PR, because issue branch 230 has not been properly updated from develop.
After updating issue branch 230, p1IterateAiPmSlices is no longer listed as changed file.

Error message shall be removed as a part of the bug fix in DPMDP v1.0 (milestone v1.0.1).
The correction will be represented in a file that will be created as a part of the rectification of p1CalculateUtilization releases in newly created issue #309.

This pull-request will be merged for avoiding to lose the made changes in a function that will be named p2CalculateUtilization in future.