From 30830bfb435e6ee3a1cdbf2b4be6b90464b7c90b Mon Sep 17 00:00:00 2001 From: Kevin Scaggs Date: Thu, 23 Aug 2018 19:11:40 -0500 Subject: Updates to common and vnf submodels Common updates are primarily VES related. Minor Vnf updates related to allotted resource Issue-ID: MODELING-104 Change-Id: Ia9a5192657724e300706acdbb9c936f5a312eb1c Signed-off-by: Kevin Scaggs --- papyrus/ONAP Information Model/Common.notation | 1965 ++---------------------- papyrus/ONAP Information Model/Common.uml | 385 ++--- papyrus/ONAP Information Model/Vnf.notation | 56 +- papyrus/ONAP Information Model/Vnf.uml | 71 +- 4 files changed, 415 insertions(+), 2062 deletions(-) (limited to 'papyrus/ONAP Information Model') diff --git a/papyrus/ONAP Information Model/Common.notation b/papyrus/ONAP Information Model/Common.notation index d371cb5..993d339 100644 --- a/papyrus/ONAP Information Model/Common.notation +++ b/papyrus/ONAP Information Model/Common.notation @@ -29,11 +29,6 @@ - - - - - @@ -73,11 +68,6 @@ - - - - - @@ -117,11 +107,6 @@ - - - - - @@ -240,11 +225,6 @@ - - - - - @@ -254,11 +234,6 @@ - - - - - @@ -279,9 +254,9 @@ - + - + @@ -313,9 +288,9 @@ - + - + @@ -337,13 +312,17 @@ + + + + - + @@ -352,11 +331,6 @@ - - - - - @@ -366,11 +340,6 @@ - - - - - @@ -391,7 +360,7 @@ - + @@ -400,11 +369,6 @@ - - - - - @@ -414,11 +378,6 @@ - - - - - @@ -453,11 +412,6 @@ - - - - - @@ -467,11 +421,6 @@ - - - - - @@ -481,11 +430,6 @@ - - - - - @@ -495,11 +439,6 @@ - - - - - @@ -509,11 +448,6 @@ - - - - - @@ -523,11 +457,6 @@ - - - - - @@ -537,11 +466,6 @@ - - - - - @@ -551,11 +475,6 @@ - - - - - @@ -568,23 +487,10 @@ - - - - - - - -

- - - - - @@ -599,11 +505,6 @@ - - - - - @@ -613,11 +514,6 @@ - - - - - @@ -627,11 +523,6 @@ - - - - - @@ -641,11 +532,6 @@ - - - - - @@ -655,11 +541,6 @@ - - - - - @@ -669,11 +550,6 @@ - - - - - @@ -698,11 +574,6 @@ - - - - - @@ -712,11 +583,6 @@ - - - - - @@ -726,11 +592,6 @@ - - - - - @@ -740,11 +601,6 @@ - - - - - @@ -754,11 +610,6 @@ - - - - - @@ -768,11 +619,6 @@ - - - - - @@ -782,11 +628,6 @@ - - - - - @@ -796,11 +637,6 @@ - - - - - @@ -810,11 +646,6 @@ - - - - - @@ -824,11 +655,6 @@ - - - - - @@ -838,11 +664,6 @@ - - - - - @@ -852,11 +673,6 @@ - - - - - @@ -866,11 +682,6 @@ - - - - - @@ -880,11 +691,6 @@ - - - - - @@ -894,11 +700,6 @@ - - - - - @@ -908,11 +709,6 @@ - - - - - @@ -922,11 +718,6 @@ - - - - - @@ -936,11 +727,6 @@ - - - - - @@ -950,11 +736,6 @@ - - - - - @@ -964,11 +745,6 @@ - - - - - @@ -978,11 +754,6 @@ - - - - - @@ -992,11 +763,6 @@ - - - - - @@ -1006,11 +772,6 @@ - - - - - @@ -1020,11 +781,6 @@ - - - - - @@ -1034,11 +790,6 @@ - - - - - @@ -1048,11 +799,6 @@ - - - - - @@ -1062,11 +808,6 @@ - - - - - @@ -1076,11 +817,6 @@ - - - - - @@ -1090,11 +826,6 @@ - - - - - @@ -1104,11 +835,6 @@ - - - - - @@ -1118,11 +844,6 @@ - - - - - @@ -1132,11 +853,6 @@ - - - - - @@ -1146,11 +862,6 @@ - - - - - @@ -1160,11 +871,6 @@ - - - - - @@ -1174,11 +880,6 @@ - - - - - @@ -1188,11 +889,6 @@ - - - - - @@ -1202,11 +898,6 @@ - - - - - @@ -1216,11 +907,6 @@ - - - - - @@ -1230,11 +916,6 @@ - - - - - @@ -1244,11 +925,6 @@ - - - - - @@ -1258,11 +934,6 @@ - - - - - @@ -1272,11 +943,6 @@ - - - - - @@ -1286,11 +952,6 @@ - - - - - @@ -1300,11 +961,6 @@ - - - - - @@ -1314,11 +970,6 @@ - - - - - @@ -1328,11 +979,6 @@ - - - - - @@ -1342,11 +988,6 @@ - - - - - @@ -1356,11 +997,6 @@ - - - - - @@ -1370,11 +1006,6 @@ - - - - - @@ -1384,11 +1015,6 @@ - - - - - @@ -1398,11 +1024,6 @@ - - - - - @@ -1432,11 +1053,6 @@ - - - - - @@ -1446,11 +1062,6 @@ - - - - - @@ -1460,11 +1071,6 @@ - - - - - @@ -1474,11 +1080,6 @@ - - - - - @@ -1488,11 +1089,6 @@ - - - - - @@ -1502,11 +1098,6 @@ - - - - - @@ -1516,11 +1107,6 @@ - - - - - @@ -1550,11 +1136,6 @@ - - - - - @@ -1564,11 +1145,6 @@ - - - - - @@ -1578,11 +1154,6 @@ - - - - - @@ -1592,11 +1163,6 @@ - - - - - @@ -1606,11 +1172,6 @@ - - - - - @@ -1620,11 +1181,6 @@ - - - - - @@ -1634,11 +1190,6 @@ - - - - - @@ -1659,7 +1210,7 @@ - + @@ -1668,11 +1219,6 @@ - - - - - @@ -1682,11 +1228,6 @@ - - - - - @@ -1696,11 +1237,6 @@ - - - - - @@ -1710,11 +1246,6 @@ - - - - - @@ -1724,11 +1255,6 @@ - - - - - @@ -1738,11 +1264,6 @@ - - - - - @@ -1752,11 +1273,6 @@ - - - - - @@ -1766,11 +1282,6 @@ - - - - - @@ -1780,11 +1291,6 @@ - - - - - @@ -1794,11 +1300,6 @@ - - - - - @@ -1808,11 +1309,6 @@ - - - - - @@ -1822,11 +1318,6 @@ - - - - - @@ -1836,11 +1327,6 @@ - - - - - @@ -1861,7 +1347,7 @@ - + @@ -1870,11 +1356,6 @@ - - - - - @@ -1884,11 +1365,6 @@ - - - - - @@ -1909,7 +1385,7 @@ - + @@ -1935,7 +1411,7 @@ - + @@ -1944,11 +1420,6 @@ - - - - - @@ -1978,11 +1449,6 @@ - - - - - @@ -1992,11 +1458,6 @@ - - - - - @@ -2006,11 +1467,6 @@ - - - - - @@ -2020,11 +1476,6 @@ - - - - - @@ -2034,11 +1485,6 @@ - - - - - @@ -2048,11 +1494,6 @@ - - - - - @@ -2073,7 +1514,7 @@ - + @@ -2082,11 +1523,6 @@ - - - - - @@ -2096,11 +1532,6 @@ - - - - - @@ -2110,11 +1541,6 @@ - - - - - @@ -2124,11 +1550,6 @@ - - - - - @@ -2149,7 +1570,7 @@ - + @@ -2158,11 +1579,6 @@ - - - - - @@ -2203,7 +1619,7 @@ - + @@ -2212,11 +1628,6 @@ - - - - - @@ -2226,11 +1637,6 @@ - - - - - @@ -2240,11 +1646,6 @@ - - - - - @@ -2265,7 +1666,7 @@ - + @@ -2274,11 +1675,6 @@ - - - - - @@ -2288,11 +1684,6 @@ - - - - - @@ -2302,11 +1693,6 @@ - - - - - @@ -2327,7 +1713,7 @@ - + @@ -2341,20 +1727,10 @@ - - - - - - - - - - @@ -2369,11 +1745,6 @@ - - - - - @@ -2391,6 +1762,105 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -2406,11 +1876,6 @@ - - - - - @@ -2420,11 +1885,6 @@ - - - - - @@ -2455,11 +1915,6 @@ - - - - - @@ -2471,18 +1926,13 @@ - + - - - - - @@ -2492,11 +1942,6 @@ - - - - - @@ -2506,11 +1951,6 @@ - - - - - @@ -2520,11 +1960,6 @@ - - - - - @@ -2537,11 +1972,6 @@

- - - - - @@ -2551,11 +1981,6 @@ - - - - - @@ -2565,11 +1990,6 @@ - - - - - @@ -2578,12 +1998,16 @@ - - - - - + + + + + + + + + @@ -2593,11 +2017,6 @@ - - - - - @@ -2607,11 +2026,6 @@ - - - - - @@ -2621,11 +2035,6 @@ - - - - - @@ -2635,11 +2044,6 @@ - - - - - @@ -2649,11 +2053,6 @@ - - - - - @@ -2662,12 +2061,10 @@ - - - - - - + + +

+ @@ -2677,11 +2074,6 @@ - - - - - @@ -2691,11 +2083,6 @@ - - - - - @@ -2705,6 +2092,11 @@ + + + + + @@ -2720,20 +2112,15 @@ - + - + - - - - - @@ -2743,11 +2130,6 @@ - - - - - @@ -2757,11 +2139,6 @@ - - - - - @@ -2771,11 +2148,6 @@ - - - - - @@ -2785,11 +2157,6 @@ - - - - - @@ -2799,11 +2166,6 @@ - - - - - @@ -2813,11 +2175,6 @@ - - - - - @@ -2827,11 +2184,6 @@ - - - - - @@ -2841,11 +2193,6 @@ - - - - - @@ -2855,11 +2202,6 @@ - - - - - @@ -2869,11 +2211,6 @@ - - - - - @@ -2883,11 +2220,6 @@ - - - - - @@ -2908,9 +2240,9 @@ - + - + @@ -2979,7 +2311,7 @@ - + @@ -3009,6 +2341,11 @@ + + + + + @@ -3027,206 +2364,13 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + - - - - - @@ -3236,11 +2380,6 @@ - - - - - @@ -3250,11 +2389,6 @@ - - - - - @@ -3264,11 +2398,6 @@ - - - - - @@ -3278,11 +2407,6 @@ - - - - - @@ -3292,11 +2416,6 @@ - - - - - @@ -3306,11 +2425,6 @@ - - - - - @@ -3320,11 +2434,6 @@ - - - - - @@ -3334,11 +2443,6 @@ - - - - - @@ -3359,20 +2463,15 @@ - + - + - - - - - @@ -3382,11 +2481,6 @@ - - - - - @@ -3396,11 +2490,6 @@ - - - - - @@ -3421,7 +2510,7 @@ - + @@ -3430,11 +2519,6 @@ - - - - - @@ -3444,11 +2528,6 @@ - - - - - @@ -3458,11 +2537,6 @@ - - - - - @@ -3472,11 +2546,6 @@ - - - - - @@ -3486,11 +2555,6 @@ - - - - - @@ -3500,11 +2564,6 @@ - - - - - @@ -3514,11 +2573,6 @@ - - - - - @@ -3528,11 +2582,6 @@ - - - - - @@ -3542,11 +2591,6 @@ - - - - - @@ -3556,11 +2600,6 @@ - - - - - @@ -3570,11 +2609,6 @@ - - - - - @@ -3584,11 +2618,6 @@ - - - - - @@ -3598,11 +2627,6 @@ - - - - - @@ -3612,11 +2636,6 @@ - - - - - @@ -3625,12 +2644,7 @@ - - - - - - + @@ -3640,11 +2654,6 @@ - - - - - @@ -3654,11 +2663,6 @@ - - - - - @@ -3668,11 +2672,6 @@ - - - - - @@ -3682,11 +2681,6 @@ - - - - - @@ -3696,11 +2690,6 @@ - - - - - @@ -3710,11 +2699,6 @@ - - - - - @@ -3724,11 +2708,6 @@ - - - - - @@ -3738,11 +2717,6 @@ - - - - - @@ -3752,11 +2726,6 @@ - - - - - @@ -3786,11 +2755,6 @@ - - - - - @@ -3800,11 +2764,6 @@ - - - - - @@ -3814,11 +2773,6 @@ - - - - - @@ -3828,11 +2782,6 @@ - - - - - @@ -3842,11 +2791,6 @@ - - - - - @@ -3856,11 +2800,6 @@ - - - - - @@ -3870,11 +2809,6 @@ - - - - - @@ -3884,11 +2818,6 @@ - - - - - @@ -3898,11 +2827,6 @@ - - - - - @@ -3912,11 +2836,6 @@ - - - - - @@ -3926,11 +2845,6 @@ - - - - - @@ -3940,11 +2854,6 @@ - - - - - @@ -3954,11 +2863,6 @@ - - - - - @@ -3968,11 +2872,6 @@ - - - - - @@ -3982,11 +2881,6 @@ - - - - - @@ -3996,11 +2890,6 @@ - - - - - @@ -4010,11 +2899,6 @@ - - - - - @@ -4024,11 +2908,6 @@ - - - - - @@ -4038,11 +2917,6 @@ - - - - - @@ -4052,11 +2926,6 @@ - - - - - @@ -4066,11 +2935,6 @@ - - - - - @@ -4080,11 +2944,6 @@ - - - - - @@ -4094,11 +2953,6 @@ - - - - - @@ -4108,11 +2962,6 @@ - - - - - @@ -4122,11 +2971,6 @@ - - - - - @@ -4136,11 +2980,6 @@ - - - - - @@ -4150,11 +2989,6 @@ - - - - - @@ -4164,11 +2998,6 @@ - - - - - @@ -4178,11 +3007,6 @@ - - - - - @@ -4192,11 +3016,6 @@ - - - - - @@ -4206,11 +3025,6 @@ - - - - - @@ -4220,11 +3034,6 @@ - - - - - @@ -4234,11 +3043,6 @@ - - - - - @@ -4268,11 +3072,6 @@ - - - - - @@ -4282,11 +3081,6 @@ - - - - - @@ -4296,11 +3090,6 @@ - - - - - @@ -4310,11 +3099,6 @@ - - - - - @@ -4324,11 +3108,6 @@ - - - - - @@ -4338,11 +3117,6 @@ - - - - - @@ -4352,11 +3126,6 @@ - - - - - @@ -4366,11 +3135,6 @@ - - - - - @@ -4380,11 +3144,6 @@ - - - - - @@ -4414,11 +3173,6 @@ - - - - - @@ -4428,11 +3182,6 @@ - - - - - @@ -4442,11 +3191,6 @@ - - - - - @@ -4456,11 +3200,6 @@ - - - - - @@ -4495,11 +3234,6 @@ - - - - - @@ -4509,11 +3243,6 @@ - - - - - @@ -4523,11 +3252,6 @@ - - - - - @@ -4537,11 +3261,6 @@ - - - - - @@ -4551,11 +3270,6 @@ - - - - - @@ -4565,11 +3279,6 @@ - - - - - @@ -4579,11 +3288,6 @@ - - - - - @@ -4593,11 +3297,6 @@ - - - - - @@ -4607,11 +3306,6 @@ - - - - - @@ -4621,11 +3315,6 @@ - - - - - @@ -4635,11 +3324,6 @@ - - - - - @@ -4649,11 +3333,6 @@ - - - - - @@ -4663,11 +3342,6 @@ - - - - - @@ -4692,11 +3366,6 @@ - - - - - @@ -4706,11 +3375,6 @@ - - - - - @@ -4720,11 +3384,6 @@ - - - - - @@ -4734,11 +3393,6 @@ - - - - - @@ -4748,11 +3402,6 @@ - - - - - @@ -4762,11 +3411,6 @@ - - - - - @@ -4776,11 +3420,6 @@ - - - - - @@ -4790,11 +3429,6 @@ - - - - - @@ -4804,11 +3438,6 @@ - - - - - @@ -4818,11 +3447,6 @@ - - - - - @@ -4852,11 +3476,6 @@ - - - - - @@ -4866,11 +3485,6 @@ - - - - - @@ -4880,11 +3494,6 @@ - - - - - @@ -4894,11 +3503,6 @@ - - - - - @@ -4908,11 +3512,6 @@ - - - - - @@ -4942,11 +3541,6 @@ - - - - - @@ -4956,11 +3550,6 @@ - - - - - @@ -4970,11 +3559,6 @@ - - - - - @@ -4984,11 +3568,6 @@ - - - - - @@ -4998,11 +3577,6 @@ - - - - - @@ -5012,11 +3586,6 @@ - - - - - @@ -5026,11 +3595,6 @@ - - - - - @@ -5040,11 +3604,6 @@ - - - - - @@ -5054,11 +3613,6 @@ - - - - - @@ -5068,11 +3622,6 @@ - - - - - @@ -5082,11 +3631,6 @@ - - - - - @@ -5096,11 +3640,6 @@ - - - - - @@ -5110,11 +3649,6 @@ - - - - - @@ -5124,11 +3658,6 @@ - - - - - @@ -5138,11 +3667,6 @@ - - - - - @@ -5152,11 +3676,6 @@ - - - - - @@ -5191,11 +3710,6 @@ - - - - - @@ -5205,11 +3719,6 @@ - - - - - @@ -5219,11 +3728,6 @@ - - - - - @@ -5233,11 +3737,6 @@ - - - - - @@ -5247,11 +3746,6 @@ - - - - - @@ -5261,11 +3755,6 @@ - - - - - @@ -5275,11 +3764,6 @@ - - - - - @@ -5289,11 +3773,6 @@ - - - - - @@ -5303,11 +3782,6 @@ - - - - - @@ -5317,11 +3791,6 @@ - - - - - @@ -5331,11 +3800,6 @@ - - - - - @@ -5345,11 +3809,6 @@ - - - - - @@ -5359,11 +3818,6 @@ - - - - - @@ -5373,11 +3827,6 @@ - - - - - @@ -5387,11 +3836,6 @@ - - - - - @@ -5401,11 +3845,6 @@ - - - - - @@ -5463,25 +3902,10 @@ - - - - - - - - - - - - - - - @@ -5539,11 +3963,6 @@ - - - - - @@ -5553,11 +3972,6 @@ - - - - - @@ -5567,11 +3981,6 @@ - - - - - @@ -5606,11 +4015,6 @@ - - - - - @@ -5620,11 +4024,6 @@ - - - - - @@ -5649,11 +4048,6 @@ - - - - - @@ -5668,11 +4062,6 @@ - - - - - @@ -5697,11 +4086,6 @@ - - - - - @@ -5711,11 +4095,6 @@ - - - - - @@ -5820,11 +4199,6 @@ - - - - - @@ -5834,11 +4208,6 @@ - - - - - @@ -5848,11 +4217,6 @@ - - - - - @@ -5942,11 +4306,6 @@ - - - - - @@ -5984,11 +4343,6 @@ - - - - - @@ -5998,11 +4352,6 @@ - - - - - @@ -6012,11 +4361,6 @@ - - - - - @@ -6026,11 +4370,6 @@ - - - - - diff --git a/papyrus/ONAP Information Model/Common.uml b/papyrus/ONAP Information Model/Common.uml index 6188890..278c74c 100644 --- a/papyrus/ONAP Information Model/Common.uml +++ b/papyrus/ONAP Information Model/Common.uml @@ -288,6 +288,62 @@ Note: the description of this class are different in ETSI GS NFV IFA 011 and ETS Fill in attribute defs and check attribute multiplicity + + Discuss spec event data type (no class) + + + multiplicity (0..1 or 0..*) for highend and lowend of latency bucket + + + + The latencyBucketMeasure datatype consists of the following fields which describe the number of counts falling within a defined latency bucket + + + + Number of counts falling within a defined latency bucket + + + + + High end of bucket range (typically in ms) + + + + + + + Low end of bucket range (typically in ms) + + + + + + + + The load datatype provides metrics on system cpu and io utilization obtained using /proc/loadavg + + + + number of jobs in the run queue (state R, cpu utilization) or waiting for disk I/O (state D, io utilization) averaged over 15 minutes using /proc/loadavg + + + + + + + number of jobs in the run queue (state R, cpu utilization) or waiting for disk I/O (state D, io utilization) averaged over 5 minutes using /proc/loadavg + + + + + + + number of jobs in the run queue (state R, cpu utilization) or waiting for disk I/O (state D, io utilization) averaged over 1 minute using /proc/loadavg + + + + + @@ -602,21 +658,13 @@ ONAP event messages are serialized as a unicode ASCII character string which may commonEventHeader - Fields common to all events. - - domain - Event domain enumeration: - -‘fault’, ‘heartbeat’, ‘measurementsForVfScaling’, ‘mobileFlow’, ‘other’, ‘sipSignaling’, ‘stateChange’, ‘syslog’, ‘thresholdCrossingAlert’, ‘voiceQuality’ - + + Event domain enumeration: ‘fault’, ‘heartbeat’, ‘measurement’, ‘mobileFlow’, ‘notification’, ‘other’, ‘pnfRegistration’, ‘sipSignaling’, ‘stateChange’, ‘syslog’, ‘thresholdCrossingAlert’, ‘voiceQuality’ - - eventId -Event key that is unique to the event source. - -The key must be unique within notification life cycle similar to EventId from 3GPP. It could be a sequential number, or a composite key formed from the event fields, such as domain_sequence. - -The eventId should not include whitespaces. For fault events, eventId is the eventId of the initial alarm; if the same alarm is raised again for changed, acknowledged or cleared cases, eventId must be the same as the initial alarm (along with the same startEpochMicrosec but with a different sequence number). - + + Event key that is unique to the event source. The key must be unique within notification life cycle similar to EventID from 3GPP. It could be a sequential number, or a composite key formed from the event fields, such as domain_sequence. The eventId should not include whitespace. For fault events, eventId is the eventId of the initial alarm; if the same alarm is raised again for changed, acknowledged or cleared cases, eventId must be the same as the initial alarm (along with the same startEpochMicrosec but with a different sequence number). Note: see section 1.3 for eventId use case examples. @@ -642,146 +690,137 @@ Domain abbreviations are derived from the ‘domain’ field in the commonEventH ‘VoiceQuality’ for the voiceQuality domain + + Unique event name + - - eventType - Needs to determine the source generating the event. The valid values are: ‘applicationVnf’, ‘guestOS’, ‘hostOS’, ‘platform’ - -applicationVNF: When the event is related to the VNF application. - -guestOS: When the event is related to the Operating System of the VM where the VNF is running on. - -platform: When the event is related to the platform, hardware of where a VNF might be running on (including Jericho Cisco NCS Switch) - -hostOS: When the event is related to the operating system of the hardware - + + For example: ‘applicationNf’, ‘guestOS’, ‘hostOS’, ‘platform’ - - - lastEpochMicrosec - the latest unix time aka epoch time associated with the event from any component--as microseconds elapsed since 1 Jan 1970 not including leap seconds + + + the latest unix time aka epoch time associated with the event from any component--as microseconds elapsed since 1 Jan 1970 not including leap seconds - - nfcNamingCode - Network function component type: 3 characters (aligned with vfc naming standards) - + + Network function component type: 3 characters (aligned with vfc naming standards) + + - - nfNamingCode - Network function type: 4 characters (aligned with Vnf naming standards). - + + Network function type: 4 characters (aligned with vnf and pnf naming standards) + + - - priority - Processing priority enumeration: ‘High’, ‘Medium’, ‘Normal’, ‘Low’ - + + Processing priority enumeration: ‘High’, ‘Medium’, ‘Normal’, ‘Low’ - - reportingEntityId - UUID identifying the entity reporting the event or detecting a problem in another xnf/vm or pnf which is experiencing the problem. - -Note: the AT&T internal enrichment process shall ensure that this field is populated. The reportingEntityId is an id for the reportingEntityName. See reportingEntityName for more information. - - reportingEntityId - UUID identifying the entity reporting the event or detecting a problem in another xnf/vm or pnf which is experiencing the problem. Note: the AT&T internal enrichment process shall ensure that this field is populated. The reportingEntityId is an id for the reportingEntityName. See reportingEntityName for more information. + + UUID identifying the entity reporting the event or detecting a problem in another vnf/vm or pnf which is experiencing the problem. (Note: the AT&T internal enrichment process shall ensure that this field is populated). The reportingEntityId is an id for the reportingEntityName. See ‘reportingEntityName’ for more information. + - - reportingEntityName - Name of the entity reporting the event or detecting a problem in another xnf/vm or pnf which is experiencing the problem. May be the same as the sourceName. For synthetic events generated by DCAE, it is the name of the app generating the event. - - reportingEntityName - Name of the entity reporting the event or detecting a problem in another xnf/vm or pnf which is experiencing the problem. May be the same as the sourceName. For synthetic events generated by DCAE, it is the name of the app generating the event. + + Name of the entity reporting the event or detecting a problem in another vnf/vm or pnf which is experiencing the problem. May be the same as the sourceName. For synthetic events generated by DCAE, it is the name of the app generating the event. + - - sequence - Ordering of events communicated by an event source instance (or 0 if not needed) - - sequence - Ordering of events communicated by an event source instance (or 0 if not needed) + + Ordering of events communicated by an event source instance (or 0 if not needed) + - - sourceId - UUID identifying the entity experiencing the event issue, which may be detected and reported by a separate reporting entity - -Note: the AT&T internal enrichment process shall ensure that this field is populate). The sourceId is an id for the sourceName. See sourceName for more information. - - sourceId - UUID identifying the entity experiencing the event issue, which may be detected and reported by a separate reporting entity Note: the AT&T internal enrichment process shall ensure that this field is populate). The sourceId is an id for the sourceName. See sourceName for more information. + + UUID identifying the entity experiencing the event issue, which may be detected and reported by a separate reporting entity (note: the AT&T internal enrichment process shall ensure that this field is populated). The sourceId is an id for the sourceName. See ‘sourceName’ for more information. + - - sourceName - Name of the entity experiencing the event issue, which may be detected and reported by a separate reporting entity. The sourceName identifies the device for which data is collected. A valid sourceName must be inventoried in A&AI. If sourceName is a xNFC or VM, then the event must be reporting data for that particular xNFC or VM. If the sourceName is a xNF, comprised of multiple xNFCs, the data must be reported/aggregated at the xNF leveI. Data for individual xNFC must not be included in the xNF sourceName event. - - sourceName - Name of the entity experiencing the event issue, which may be detected and reported by a separate reporting entity. The sourceName identifies the device for which data is collected. A valid sourceName must be inventoried in A&AI. If sourceName is a xNFC or VM, then the event must be reporting data for that particular xNFC or VM. If the sourceName is a xNF, comprised of multiple xNFCs, the data must be reported/aggregated at the xNF leveI. Data for individual xNFC must not be included in the xNF sourceName event. + + Name of the entity experiencing the event issue, which may be detected and reported by a separate reporting entity. The sourceName identifies the device for which data is collected. A valid sourceName must be inventoried in A&AI. If sourceName is a xNFC or VM, then the event must be reporting data for that particular xNFC or VM. If the sourceName is a xNF, comprised of multiple xNFCs, the data must be reported/aggregated at the xNF leveI. Data for individual xNFC must not be included in the xNF sourceName event. + - - - startEpochMicrosec - the earliest unix time aka epoch time associated with the event from any component--as microseconds elapsed since 1 Jan 1970 not including leap seconds. For measurements and heartbeats, where events are collected over predefined intervals, startEpochMicrosec shall be rounded to the nearest interval boundary (e.g., the epoch equivalent of 3:00PM, 3:10PM, 3:20PM, etc…). - -For fault events, startEpochMicrosec is the timestamp of the initial alarm; if the same alarm is raised again for changed, acknowledged or cleared cases, startEpochMicrosec must be the same as the initial alarm (along with the same eventId and an incremental sequence number). For devices with no timing source (clock), the default value will be 0 and DCAE collector will replace it with Collector time stamp (when event is received). - - + startEpochMicrosec - the earliest unix time aka epoch time associated with the event from any component--as microseconds elapsed since 1 Jan 1970 not including leap seconds. For measurements and heartbeats, where events are collected over predefined intervals, startEpochMicrosec shall be rounded to the nearest interval boundary (e.g., the epoch equivalent of 3:00PM, 3:10PM, 3:20PM, etc…). For fault events, startEpochMicrosec is the timestamp of the initial alarm; if the same alarm is raised again for changed, acknowledged or cleared cases, startEpochMicrosec must be the same as the initial alarm (along with the same eventId and an incremental sequence number). For devices with no timing source (clock), the default value will be 0 and DCAE collector will replace it with Collector time stamp (when event is received). + + the earliest unix time aka epoch time associated with the event from any component--as microseconds elapsed since 1 Jan 1970 not including leap seconds. For measurements and heartbeats, where events are collected over predefined intervals, startEpochMicrosec shall be rounded to the nearest interval boundary (e.g., the epoch equivalent of 3:00PM, 3:10PM, 3:20PM, etc…). For fault events, startEpochMicrosec is the timestamp of the initial alarm; if the same alarm is raised again for changed, acknowledged or cleared cases, startEpoch Microsec must be the same as the initial alarm (along with the same eventId and an incremental sequence number). For devices with no timing source (clock), the default value will be 0 and the VES collector will replace it with Collector time stamp (when the event is received) + - - timeZoneOffset - offset to/from GMT to indicate local timezone for device. - -Example: +4, -5 - + + Offset to GMT to indicate local time zone for device formatted as ‘UTC+/-hh.mm’; see https://en.wikipedia.org/wiki/List_of_time_zone_abbreviations for UTC offset examples - + + + + + + + Version of the event header as “#.#” where # is a digit; see section 1 for the correct digits to use. + + - - - version - Version of the event header + + + Version of the ves event listener api spec that this event is compliant with (as “#” or “#.#” or “#.#.#” where # is a digit; see section 1 for the correct digits to use). + + + + - @@ -802,7 +841,7 @@ Example: +4, -5 - faultFields - Fields specific to fault events. + Fields specific to fault events. @@ -816,7 +855,7 @@ Example: +4, -5 - measurementsFields - Fields specific to measurement events. + Fields specific to measurement events. @@ -824,7 +863,7 @@ Example: +4, -5 - mobileFlowFields - Fields specific to mobilityFlow events. + Fields specific to mobilityFlow events. @@ -832,7 +871,7 @@ Example: +4, -5 - notificationFields - Fields specific to notification events. + Fields specific to notification events. @@ -863,7 +902,7 @@ Example: +4, -5 - stateChangeFields - Fields specific to state change events. + Fields specific to state change events. @@ -871,7 +910,7 @@ Example: +4, -5 - syslogFields - Fields specific to syslog events. + Fields specific to syslog events. @@ -879,21 +918,21 @@ Example: +4, -5 - thresholdCrossingAlertFields - Fields specific to thresholdCrossingAlert events. + Fields specific to thresholdCrossingAlert events. - voiceQualityFields - Fields specific to voiceQuality events. + Fields specific to voiceQuality events. - + codecsInUse - the codecsInUse datatype consists of the following fields describing the number of times an identified codec was used over the measurementInterval @@ -914,101 +953,68 @@ Example: +4, -5 - faultFields - Fields specific to fault events + Fields specific to fault events - - alarmAdditionalInformation - additional Information related to Alarm, such as Repair Action, Remedy code. - -May by serialized alarm payload: varbind list, original syslog message, notification parameters, etc. when event is generated via other means, should provide raw detail out of element. + + Additional alarm information. +• Note1: for SNMP mapping to VES, for hash key use OID of varbind, for value use incoming data for that varbind). +• Note2: Alarm ID for 3GPP should be included (if applicable) in alarmAdditonalInformation as ‘alarmId’:’alarmIdValue’. +Could contain managed object instance as separate key:value; could add probable cause as separate key:value. - - alarmCondition - Short name of the alarm/problem, like trap name. Could be of SPECIFIC_PROBLEM list: -(x733_SpecificProblems). - -Should be string to avoid duplicate dictionary translation. This should be a one word. - -Indicates the Alarm Condition as reported by the device. Should be string to avoid duplicate dictionary translation. This would be a alarm description. - -Data from probableCause (3GPP and MTOSI) would be an alarm summary. - + + Short name of the alarm condition/problem, such as a trap name. Should not have white space (e.g., tpLgCgiNotInConfig, BfdSessionDown, linkDown, etc…) - - alarmInterfaceA - Provide port or channel or interface information when alarm is related with interface faults. Could be card/port, or channel, or interface name. - -Would represent the interface number the event on the sourceName is reported against, so alarm generated on the device interface could be identified against the far side (alarmInterfaceZ) based on logical or physical topology rather than having the information embedded somewhere else requiring regular expression extract. - + + Card, port, channel or interface name of the device generating the alarm. This could reflect managed object. - - eventCategory - Event category. - -For example: ‘license’, ‘link’, ‘routing’, ‘security’, ‘signaling’ - + + Event category, for example: ‘license’, ‘link’, ‘routing’, ‘security’, ‘signaling’ - - eventSeverity - Event severity enumeration. - -severity enumeration: -‘CRITICAL’, ‘MAJOR’, ‘MINOR’, ‘WARNING’, ‘NORMAL’ - + + Event severity enumeration: ‘CRITICAL’, ‘MAJOR’, ‘MINOR’, ‘WARNING’, ‘NORMAL’. NORMAL is used to represent clear. - - eventSourceType - Provide the type of element the Source might be. This can be network function specific, or application specific. - -Examples: other, router, switch, host, card, port, slotThreshold, portThreshold, virtual machine, etc… - -Could also be PCRF, MMSC, NEM, MME, ENB, etc... - + + Examples: ‘card’, ‘host’, ‘other’, ‘port’, ‘portThreshold’, ‘router’, ‘slotThreshold’, ‘switch’, ‘virtualMachine’, ‘virtualNetworkFunction’. This could be managed object class. - - faultFieldsVersion - version of the faultFields block. - + + Version of the faultFields block as “#.#” where # is a digit; see section 1 for the correct digits to use. + - - specificProblem - short name of the alarm/problem, like trap name. Could be of SPECIFIC_PROBLEM list: (x733_SpecificProblems). Should be string to avoid duplicate dictionary translation. This should be a one word. - -Example: LinkDown, BFDSessionDown, etc…. SpecificProblem (3GPP) or X733_SpecificProblem (MTOSI) - + + Description of the alarm or problem (e.g., ‘eNodeB 155197 in PLMN 310-410 with eNodeB name KYL05197 is lost’). 3GPP probable cause would be included in this field. - - vfStatus - Used to report on VF status, both to indicate success/failure of start/stop/prepare to terminate events, but also to allow VF to request termination after unrecoverable errors. - -Enumeration; valid values are -- Idle -- Active -- Preparing to terminate -- Ready to terminate -- Requesting termination - + + Virtual function status enumeration: ‘Active’, ‘Idle’, ‘Preparing to terminate’, ‘Ready to terminate’, ‘Requesting Termination’ @@ -1019,27 +1025,26 @@ Enumeration; valid values are - - additionalFields - Additional expansion fields if needed. - + + The heartbeatFields datatype is an optional field block for fields specific to heartbeat events. - additionalFields - Additional expansion fields if needed. + Additional expansion fields if needed. - - heartbeatFieldVersion - version of the heartbeatFields block. - + + Version of the heartbeatFields block as “#.#” where # is a digit; see section 1 for the correct digits to use. + - heartbeatInterval - current heartbeatInterval in seconds. + Current heartbeatInterval in seconds. @@ -1052,24 +1057,24 @@ Enumeration; valid values are - additionalFields - Additional measurement fields if needed. + Additional measurement fields if needed. - + - additionalMeasurements - Array of named hashMap if needed. + Array of named hashMap if needed. - + - additionalObjects - Array of JSON objects described by name, schema and other meta-information, if needed. + Array of JSON objects described by name, schema and other meta-information, if needed. @@ -1077,7 +1082,7 @@ Enumeration; valid values are - codecUsageArray - array of codecs in use. + Array of codecs in use. @@ -1085,14 +1090,16 @@ Enumeration; valid values are - concurrentSessions - Peak concurrent sessions for the VM or VNF (depending on the context) over the measurementInterval. + Peak concurrent sessions for the VM or VNF (depending on the context) over the measurementInterval. + + - configuredEntities - Depending on the context over the measurementInterval: peak total number of users, subscribers, devices, adjacencies, etc., for the VM, or peak total number of subscribers, devices, etc., for the VNF + Depending on the context over the measurementInterval: peak total number of users, subscribers, devices, adjacencies, etc., for the VM, or peak total number of subscribers, devices, etc., for the VNF @@ -1101,7 +1108,7 @@ Enumeration; valid values are - cpuUsageArray - Usage of an array of CPUs + Usage of an array of CPUs @@ -1109,7 +1116,7 @@ Enumeration; valid values are - diskUsageArray - Usage of an array of disks. + Usage of an array of disks. @@ -1117,41 +1124,51 @@ Enumeration; valid values are - featureUsageArray - The hashMap key should identify the feature, while the value defines the number of times the identified feature was used. + The hashMap key should identify the feature, while the value defines the number of times the identified feature was used. + + - filesystemUsageArray - Filesystem usage of the VM on which the VNFC reporting the event is running. + Filesystem usage of the VM on which the VNFC reporting the event is running. + + - hugePagesArray - Array of metrics on hugePages + Array of metrics on hugePages - + - ipmiArray - Array of intelligent platform management interface metrics. + Array of intelligent platform management interface metrics. + + - + - latencyDistribution - Array of integers representing counts of requests whose latency in milliseconds falls within per-VNF configured ranges; where latency is the duration between a service request and its fulfillment. + Array of integers representing counts of requests whose latency in milliseconds falls within per-VNF configured ranges; where latency is the duration between a service request and its fulfillment. + + - + loadArray - Array of system load metrics + + @@ -1514,7 +1531,7 @@ Note: current data type (String) may be changed to Common Resource Datatype L3Ad - + namedHashMap [ ] - The namedHashmap datatype is a hashMap which is associated with and described by a name. @@ -1682,7 +1699,10 @@ For example: "inService", "outOfService", "maintenance& - + + + Event severity enumeration: ‘CRITICAL’, ‘MAJOR’, ‘MINOR’, ‘WARNING’, ‘NORMAL’. NORMAL is used to represent clear. + @@ -1899,11 +1919,14 @@ Note: current data type (String) may be changed to Common Resource Datatype L3Ad - - - - - + + Virtual function status enumeration: ‘Active’, ‘Idle’, ‘Preparing to terminate’, ‘Ready to terminate’, ‘Requesting Termination’ + + + + + + @@ -2674,7 +2697,7 @@ Note: current data type (String) may be changed to Common Resource Datatype L3Ad - + domain - Event domain enumeration: @@ -3127,4 +3150,16 @@ Note: current data type (String) may be changed to Common Resource Datatype L3Ad + + + + + + + + + + + + diff --git a/papyrus/ONAP Information Model/Vnf.notation b/papyrus/ONAP Information Model/Vnf.notation index c1815ad..f1e0753 100644 --- a/papyrus/ONAP Information Model/Vnf.notation +++ b/papyrus/ONAP Information Model/Vnf.notation @@ -9656,11 +9656,6 @@ - - - - - @@ -9700,11 +9695,6 @@ - - - - - @@ -9744,11 +9734,6 @@ - - - - - @@ -9791,11 +9776,6 @@ - - - - - @@ -9838,11 +9818,6 @@ - - - - - @@ -9877,11 +9852,6 @@ - - - - - @@ -9926,11 +9896,6 @@ - - - - - @@ -9945,7 +9910,7 @@ - + @@ -9970,6 +9935,11 @@ + + + + + @@ -10004,6 +9974,11 @@ + + + + + @@ -10018,12 +9993,12 @@ - + - + @@ -10053,11 +10028,6 @@ - - - - - diff --git a/papyrus/ONAP Information Model/Vnf.uml b/papyrus/ONAP Information Model/Vnf.uml index 543c5bd..ec99a59 100644 --- a/papyrus/ONAP Information Model/Vnf.uml +++ b/papyrus/ONAP Information Model/Vnf.uml @@ -2029,8 +2029,8 @@ Diversity - Resources are geo-diverse ( cannot be co-located). - - A Service instance can generate virtual Network Function instances, acting as a "Network Function Provider" of sorts. These Network Functions are different from the Network Functions that comprise the "Provider Service" itself. (E.g., a virtual PE Service comprised of a "vPERouter" and a "vPEForwarder" VNF can collectively provide a "VRF" Network Function, which includes both routing and forwarding functionality.) We distinguish the Network Functions that are provided by a Service instance from the Network Functions that comprise a Service Instance by using the term "Allotted Resource" for the former. + + An Allotted Resource is a generic resource which could never be considered a network function and thus is not derived from the network function class. This “non-network function” based resource is provided (or allotted) by some service to be used or consumed by some other service. The consuming service does not need to know that the resource is “allotted”. @@ -2039,9 +2039,15 @@ Diversity - Resources are geo-diverse ( cannot be co-located). + + An Anfd (Allotted Network Function) is a network function provided (or allotted) by some service instance. The allotted network function may be incorporated into the topology of some consuming service like other network functions. The consuming service does not need to know that the resource is “allotted”. + + + A NetworkFunction is a functional block within a network infrastructure that has well-defined external interfaces and well-defined functional behaviour. + @@ -3229,91 +3235,94 @@ NOTE: The MANO or NFVI may not support the recommended collectionPeriod based on - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + + + + -- cgit 1.2.3-korg