From 03e9821638791ad44f2efa78a2c222c8d2383998 Mon Sep 17 00:00:00 2001 From: Kevin Scaggs Date: Mon, 24 Sep 2018 07:22:10 -0500 Subject: Updates to Common, Vnf, and Service submodels Common updates include refinements to ThresholdCrossingAlertFields and related enums and corrections per internal review. Service updates include updates to ServiceOrder & relationship between Service and AllottedResource. Vnf updates include slight updates to AllottedResource and updates to Vnf and Vnfc classes from faulty to experimental. Issue-ID: MODELING-104 Change-Id: I193ad63cdae024e938f2cb9d7bd0d27ac1bcf78c Change-Id: I193ad63cdae024e938f2cb9d7bd0d27ac1bcf78c Signed-off-by: Kevin Scaggs --- papyrus/ONAP Information Model/Common.uml | 140 ++++++++++++++++++++++++------ 1 file changed, 112 insertions(+), 28 deletions(-) (limited to 'papyrus/ONAP Information Model/Common.uml') diff --git a/papyrus/ONAP Information Model/Common.uml b/papyrus/ONAP Information Model/Common.uml index c4b1134..4f7685e 100644 --- a/papyrus/ONAP Information Model/Common.uml +++ b/papyrus/ONAP Information Model/Common.uml @@ -757,18 +757,12 @@ Shall be present when the addressType is IP address. ONAP event messages are serialized as a unicode ASCII character string which may be formatted as JSON, XML, etc... Appropriate schemas will be supplied. - - - commonEventHeader - Fields common to all events. - - - - commonEventBody - Heartbeat is an event header only with no event body [0..1] + fields which consisiute the 'root level' of the common event format - + @@ -1002,7 +996,7 @@ Note: For heardbeat events, an event body is not required. - otherFields - Fields specific to other types of events. + Fields specific to other types of events. @@ -1010,7 +1004,7 @@ Note: For heardbeat events, an event body is not required. - pnfRegistrationFields - Fields specific to pnfRegistration events. + Fields specific to pnfRegistration events. @@ -1018,7 +1012,7 @@ Note: For heardbeat events, an event body is not required. - sipSignalingFields - Fields specific to sipSignaling events. + Fields specific to sipSignaling events. @@ -1054,6 +1048,11 @@ Note: For heardbeat events, an event body is not required. + + + Fields common to all events + + @@ -1158,7 +1157,7 @@ Could contain managed object instance as separate key:value; could add probable - + @@ -1176,7 +1175,7 @@ Could contain managed object instance as separate key:value; could add probable - measurementFields - Fields specific to measurement events + Fields specific to measurement events @@ -1186,15 +1185,15 @@ Could contain managed object instance as separate key:value; could add probable - + - + Array of named hashMap if needed. - + @@ -1202,7 +1201,7 @@ Could contain managed object instance as separate key:value; could add probable - + @@ -1699,7 +1698,7 @@ Note: in ATTServiceSpecification - VesEventListener v5.4.1 type = field []. - + @@ -2008,7 +2007,7 @@ Note: current data type (String) may be changed to Common Resource Datatype L3Ad Additional stateChange fields if needed - + @@ -2042,7 +2041,7 @@ Note: current data type (String) may be changed to Common Resource Datatype L3Ad Additional syslog fields if needed Ex: {“name1”: ”value1”, “name2: “value2” … } - + @@ -2213,37 +2212,105 @@ Debug 7 debug-level messages + + Array of performance counters + - + + + Enumeration: ‘SET’, ‘CONT’, ‘CLEAR’ + + + + Unique short alert description (e.g., NE-CPUMEM) + + + + + + Enumeration: ‘CARD-ANOMALY’, ‘INTERFACE-ANOMALY’, ELEMENT-ANOMALY’, ‘SERVICE-ANOMALY’ + + + + + Calculated API value (if applicable) + - - + + List of eventIds associated with the event being reported + + + + + + + + Time when the performance collector picked up the data; with RFC 2822 compliant format: ‘Sat, 13 Mar 2010 11:29:05 -0800’ + - + + Specific performance collector instance used + + + + + Type of network element (internal AT&T field) + + + + + + + + Event severity or priority enumeration: ‘CRITICAL’, ‘MAJOR’, ‘MINOR’, ‘WARNING’, ‘NORMAL’ + + + + + Time closest to when the measurement was made; with RFC 2822 compliant format: ‘Sat, 13 Mar 2010 11:29:05 -0800’ + - - + + Physical or logical port or card (if applicable + + + + + Network name (internal AT&T field) + + + + + Reserved for future use + + + + + + + + Version of the thresholdCrossingAlertFields block as “#.#” where # is a digit; see section 1 for the correct digits to use. + - @@ -3961,6 +4028,23 @@ Percentage of time spent handling soft irq interrupts + + + Possible alertActions within thresholdCrossingAlertFields + + + + + + + + Possible values for ThresholdCrossingAlertFIelds alertType attribute. + + + + + + @@ -3997,7 +4081,6 @@ Percentage of time spent handling soft irq interrupts - @@ -4478,4 +4561,5 @@ Percentage of time spent handling soft irq interrupts + -- cgit 1.2.3-korg