Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

min-elements shall be removed from problem-kind-severity-list #46

Closed
michbin opened this issue Oct 19, 2021 · 2 comments
Closed

min-elements shall be removed from problem-kind-severity-list #46

michbin opened this issue Oct 19, 2021 · 2 comments
Assignees
@openBackhaul
Labels
duplicate This issue or pull request already exists

Comments

@michbin
Copy link

michbin commented Oct 19, 2021

As a consequence of removing mandatory alarms from supported-alarm-list (see issue #42), the constraint for the minimum number of elements must be removed from problem-kind-severity-list in ethernet-container-configuration. That is, the multiplicity must be changed from 2..* to 0..*.
@openBackhaul
Copy link
Owner

openBackhaul commented Oct 28, 2021 •
edited

Decision on the 5G-xhaul call on 10th of November 2021:

  • EthernetContainerConfiguration::problemKindSeverityList to get [*] multiplicity.
  • Comment to be changed to "Every alarm, which is listed in EthernetContainerCapability::supportedAlarmList, shall be instantiated here for facilitating configuration of a severity level."

@openBackhaul openBackhaul self-assigned this Oct 28, 2021
@openBackhaul
Copy link
Owner

obsoleted by issue #47

@openBackhaul openBackhaul added duplicate This issue or pull request already exists and removed UML_to_be_changed labels Mar 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@openBackhaul openBackhaul

Labels
duplicate This issue or pull request already exists
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@openBackhaul @michbin