From c5cf5be90bf9189dd17a6ef0508f68044c9b063d Mon Sep 17 00:00:00 2001 From: Kevin Scaggs Date: Fri, 15 Mar 2019 16:49:28 -0500 Subject: Updates to Ves Changed associations between event and domain classes from composition to generalization. Also renamed Event to VesEvent. Issue-ID: MODELING-104 Change-Id: Ie8bc9e0e934485a35f9477bf0c1c5f1037d586ec Signed-off-by: Kevin Scaggs --- ONAP Information Model/Ves.notation | 603 ++++++++++-------------------------- ONAP Information Model/Ves.uml | 184 +---------- 2 files changed, 181 insertions(+), 606 deletions(-) diff --git a/ONAP Information Model/Ves.notation b/ONAP Information Model/Ves.notation index fab733f..ae3600a 100644 --- a/ONAP Information Model/Ves.notation +++ b/ONAP Information Model/Ves.notation @@ -897,10 +897,10 @@ - - + + - + @@ -936,13 +936,13 @@ - - + + - + - + @@ -975,13 +975,13 @@ - - + + - + - + @@ -1014,13 +1014,13 @@ - - + + - + - + @@ -1053,10 +1053,10 @@ - - + + - + @@ -1098,7 +1098,7 @@ - + @@ -1137,7 +1137,7 @@ - + @@ -1176,7 +1176,7 @@ - + @@ -1215,7 +1215,7 @@ - + @@ -1254,7 +1254,7 @@ - + @@ -1293,7 +1293,7 @@ - + @@ -1332,7 +1332,7 @@ - + @@ -1371,7 +1371,7 @@ - + @@ -1410,7 +1410,7 @@ - + @@ -1449,7 +1449,7 @@ - + @@ -1485,40 +1485,6 @@ - - - - - - - -

- - - - - - - - - - - - - - - - - - - - - - - - - - @@ -1539,37 +1505,6 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -1611,37 +1546,6 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -1732,288 +1636,6 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -2024,36 +1646,145 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/ONAP Information Model/Ves.uml b/ONAP Information Model/Ves.uml index 057fb80..92be0ea 100644 --- a/ONAP Information Model/Ves.uml +++ b/ONAP Information Model/Ves.uml @@ -1,7 +1,7 @@ - + An ONAP event is an aggregation of a header and a message. Event messages may be published to a message broker by service instances, resource instances, or ONAP platform components. Service or resource instances may be in support of network infrastructure or customer services. Interested platforms may subscribe to events on the message broker (e.g. Centralized Testing Platform CTP) may see an event on a service VNF instance and perform an automated test as part of a closed loop management policy. Events are unique and distinguishable from one another. @@ -11,90 +11,6 @@ ONAP event messages are serialized as a unicode ASCII character string which may - - - Fields specific to fault events - - - - - - - Fields specific to heartbeat events - - - - - - - Fields specific to measurement events - - - - - - - Fields specific to mobility flow events - - - - - - - Fields specific to notification events - - - - - - - Fields specific to other types of events - - - - - - - Fields specific to pnfRegistration events - - - - - - - Fields specific to sipSignaling events - - - - - - - Fields specific to state change events - - - - - - - Fields specific to syslog events - - - - - - - Fields specific to threshold crossing alert events - - - - - - - Fields specific to voiceQuality events - - - - Fields common to all events @@ -102,15 +18,12 @@ ONAP event messages are serialized as a unicode ASCII character string which may - - - - Fields specific to fault events + Additional alarm information. @@ -177,6 +90,7 @@ Could contain managed object instance as separate key:value; could add probable The heartbeatFields datatype is an optional field block for fields specific to heartbeat events. + Additional expansion fields if needed. @@ -378,6 +292,7 @@ For fault events, startEpochMicrosec is the timestamp of the initial alarm; if t Fields specific to measurement events + Additional measurement fields if needed. @@ -562,6 +477,7 @@ For fault events, startEpochMicrosec is the timestamp of the initial alarm; if t Fields specific to mobility flow events + additionalFields - Additional mobileFlow fields if needed. @@ -865,6 +781,7 @@ Note: current data type (String) may be changed to Common Resource Datatype L3Ad Fields specific to notification events + Additional notification fields if needed. @@ -942,6 +859,7 @@ For example: "inService", "outOfService", "maintenance& The otherFields datatype defines fields for events belonging to the 'other' domain of the commonEventHeader domain enumeration. + Array of named hashMaps @@ -976,6 +894,7 @@ For example: "inService", "outOfService", "maintenance& The pnfRegistrationFields datatype defines fields for events belonging to the 'pnfRegistration' domain of the commonEventHeader domain enumeration; it consists of the following fields: + Additional pnfRegistration fields if needed @@ -1085,6 +1004,7 @@ For example: "inService", "outOfService", "maintenance& sipSignalingFields - The sipSignalingFields datatype communicates information about SIP signaling messages, parameters and signaling state. + zdditionalInformation - Additional sipSignalling fields. @@ -1171,6 +1091,7 @@ Note: current data type (String) may be changed to Common Resource Datatype L3Ad Fields specific to state change events. + Additional stateChange fields if needed @@ -1209,6 +1130,7 @@ Note: current data type (String) may be changed to Common Resource Datatype L3Ad VES supports both classes of syslog, however VES is only recommended for control logs or for lower volume session logs, less than 60k per hour. High volume session logging should use a file-based transport solution. + Additional syslog fields if needed Ex: {“name1”: ”value1”, “name2: “value2” … } @@ -1893,6 +1815,7 @@ Debug 7 debug-level messages The thresholdCrossingAlertFields datatype consists of the following fields: + additionalFields - Additional pnfRegistration fields if needed. @@ -2008,6 +1931,7 @@ Debug 7 debug-level messages The voiceQuality class provides statistics related to customer facing voice products; consists of the following fields: + Additional voice quality fields @@ -3892,6 +3816,7 @@ Field Type Required? Description + Additional key-value pairs if needed @@ -4687,84 +4612,12 @@ Debug 7 debug-level messages - - -

- - - - - -

- - -

- - - - - -

- - -

@@ -4927,15 +4780,6 @@ Debug 7 debug-level messages - - -

- - - Fields specific to 3gpp types of events - - -

-- cgit 1.2.3-korg