Fix spacing issues in YAML files in tosca/
[demo.git] / tosca / pNF / Files / Events / MyPnf_Pnf_v1.yaml
1 ---
2 event:
3     presence: required
4     structure:
5         commonEventHeader:
6             presence: required
7             structure:
8                 domain: {presence: required, value: notification}
9                 eventName: {presence: required, value: Noti_MyPnf-Acme_FileReady}
10                 priority: {presence: required, value: Normal}
11                 eventId: {presence: required}
12                 reportingEntityId: {presence: required}
13                 reportingEntityName: {presence: required}
14                 sequence: {presence: required, value: 0}
15                 sourceId: {presence: required}
16                 sourceName: {presence: required}
17                 version: {presence: required, value: 4.0.1}
18                 vesEventListenerVersion: {presence: required, value: 7.0.1}
19                 startEpochMicrosec: {presence: required}
20                 lastEpochMicrosec: {presence: required}
21         notificationFields:
22             presence: required
23             structure:
24                 changeIdentifier: {presence: required, value: PM_MEAS_FILES}
25                 changeType: {presence: required, value: fileReady}
26                 notificationFieldsVersion: {presence: required, value: 2.0}
27                 arrayOfNamedHashMap:
28                     presence: required
29                     array:
30                         - name: {presence: required}
31                           hashMap: {presence: required, structure: {
32                               keyValuePair: {presence: required, structure: {key: {presence: required, value: location}, value: {presence: required}}},
33                               keyValuePair: {presence: required, structure: {key: {presence: required, value: compression}, value: {presence: required, value: gzip}}},
34                               keyValuePair: {presence: required, structure: {key: {presence: required, value: fileFormatType}, value: {presence: required, value: org.3GPP.32.435}}},
35                               keyValuePair: {presence: required, structure: {key: {presence: required, value: fileFormatVersion}, value: {presence: required, value: V10}}}}
36                           }
37 ...
38 ---
39 event:
40     presence: required
41     structure:
42         commonEventHeader:
43             presence: required
44             structure:
45                 domain: {presence: required, value: pnfRegistration}
46                 eventId: {presence: required}
47                 eventName: {presence: required, value: PnfReg_MyPnf-Acme_pnfRegistration}
48                 lastEpochMicrosec: {presence: required}
49                 priority: {presence: required, value: Normal}
50                 reportingEntityName: {presence: required}
51                 sequence: {presence: required, value: 0}
52                 sourceName: {presence: required}
53                 startEpochMicrosec: {presence: required}
54                 timeZoneOffset: {presence: required}
55                 version: {presence: required, value: 4.0.1}
56                 vesEventListenerVersion: {presence: required, value: 7.0.1}
57         pnfRegistrationFields:
58             presence: required
59             structure:
60                 modelNumber: {presence: required}
61                 oamV4IpAddress: {presence: optional}
62                 oamV6IpAddress: {presence: optional}
63                 pnfRegistrationFieldsVersion: {presence: required, value: 2.0}
64                 serialNumber: {presence: required}
65                 softwareVersion: {presence: required}
66                 unitFamily: {presence: required, value: BBU}
67                 unitType: {presence: required}
68                 vendorName: {presence: required, value: Acme}
69 ...
70 ---
71 event:
72     presence: required
73     action: [ any, any, null, null, null ]
74     comment: "
75         ALARM NAME: CertMAutomaticEnrollmentFailed,
76         ALARM DESCRIPTION: ‘See alarm OPI x/1111-ABC 123 4567/1 Uen’,
77         ALARM EFFECT: 'See alarm OPI x/2222-ABC 123 4567/1 Uen',
78         MANAGED OBJECT CLASSES: NodeCredential,
79         EVENT TYPE: 'PROCESSINGERRORALARM',
80         PROBABLE CAUSE: 'ConfigurationOrCustomizationError',
81         PROPOSED REPAIR ACTIONS: 'See alarm OPI x/3333-ABC 123 4567/1 Uen',
82         CLEARING TYPE: Automatic
83     "
84     structure:
85         commonEventHeader:
86             presence: required
87             structure:
88                 version: {presence: required, value: 4.0.1}
89                 vesEventListenerVersion: {presence: required, value: 7.0.1}
90                 domain: {presence: required, value: fault}
91                 eventName: {presence: required, value: Fault_MyPnf-Acme_CertMAutomaticEnrollmentFailed}
92                 eventId: {presence: required}
93                 sequence: {presence: required}
94                 priority: {presence: required, value: Normal}
95                 reportingEntityName: {presence: required}
96                 sourceName: {presence: required}
97                 nfVendorName: {presence: required, value: Acme}
98                 startEpochMicrosec: {presence: required}
99                 lastEpochMicrosec: {presence: required}
100                 timeZoneOffset: {presence: required}
101         faultFields:
102             presence: required
103             structure:
104                 faultFieldsVersion: {presence: required, value: 4.0}
105                 alarmCondition: {presence: required, value: 'CertMAutomaticEnrollmentFailed'}
106                 eventCategory: {presence: required, value: 'PROCESSINGERRORALARM'}
107                 eventSourceType: {presence: required}
108                 specificProblem: {presence: required, value: 'Certificate Management Automatic Enrollment Failed'}
109                 eventSeverity: {presence: required}
110                 vfStatus: {presence: required, value: Active}
111                 alarmAdditionalInformation: {presence: required, structure: {
112                     keyValuePair: {presence: required, structure: {key: {presence: required, value: source}, value: {presence: required}}},
113                     keyValuePair: {presence: required, structure: {key: {presence: required, value: probableCause}, value: {presence: required, value: 'ConfigurationOrCustomizationError'}}},
114                     keyValuePair: {presence: required, structure: {key: {presence: required, value: additionalText}, value: {presence: optional}}},
115                     keyValuePair: {presence: required, structure: {key: {presence: required, value: additionalInfo}, value: {presence: optional}}}}
116                 }
117 ...
118 ---
119 event:
120     presence: required
121     action: [ any, any, null, null, null ]
122     comment: "
123         ALARM NAME: PowerLoss,
124         ALARM DESCRIPTION: 'PNF is losing power',
125         ALARM EFFECT: 'PNF will shutdown if battery is drained',
126         MANAGED OBJECT CLASSES: 'BatteryBackup;BatteryUnit',
127         EVENT TYPE: 'EQUIPMENTALARM',
128         PROBABLE CAUSE: 'Power Supply Failure',
129         PROPOSED REPAIR ACTIONS: 'Repair Power Supply',
130         CLEARING TYPE: Automatic
131     "
132     structure:
133         commonEventHeader:
134             presence: required
135             structure:
136                 version: {presence: required, value: 4.0.1}
137                 vesEventListenerVersion: {presence: required, value: 7.0.1}
138                 domain: {presence: required, value: fault}
139                 eventName: {presence: required, value: Fault_MyPnf-Acme_PowerLoss}
140                 eventId: {presence: required}
141                 sequence: {presence: required}
142                 priority: {presence: required, value: Normal}
143                 reportingEntityName: {presence: required}
144                 sourceName: {presence: required}
145                 nfVendorName: {presence: required, value: Acme}
146                 startEpochMicrosec: {presence: required}
147                 lastEpochMicrosec: {presence: required}
148                 timeZoneOffset: {presence: required}
149         faultFields:
150             presence: required
151             structure:
152                 faultFieldsVersion: {presence: required, value: 4.0}
153                 alarmCondition: {presence: required, value: 'PowerLoss'}
154                 eventCategory: {presence: required, value: 'EQUIPMENTALARM'}
155                 eventSourceType: {presence: required}
156                 specificProblem: {presence: required, value: 'Power Supply Failure'}
157                 eventSeverity: {presence: required}
158                 vfStatus: {presence: required, value: Active}
159                 alarmAdditionalInformation: {presence: required, structure: {
160                     keyValuePair: {presence: required, structure: {key: {presence: required, value: source}, value: {presence: required}}},
161                     keyValuePair: {presence: required, structure: {key: {presence: required, value: probableCause}, value: {presence: required, value: 'Power Supply Failure'}}},
162                     keyValuePair: {presence: required, structure: {key: {presence: required, value: additionalText}, value: {presence: optional}}},
163                     keyValuePair: {presence: required, structure: {key: {presence: required, value: additionalInfo}, value: {presence: optional}}}}
164                 }
165 ...
166 ---
167 event:
168     presence: required
169     action: [ any, any, null, null, null ]
170     comment: "
171         ALARM NAME: LogHasReachedFullCapacity,
172         ALARM DESCRIPTION: 'Log Has Reached Full Capacity',
173         ALARM EFFECT: 'See alarm OPI x/2223-ABC 123 4567/1 Uen',
174         MANAGED OBJECT CLASSES: Log,
175         EVENT TYPE: 'PROCESSINGERRORALARM',
176         PROBABLE CAUSE: 'FileError',
177         PROPOSED REPAIR ACTIONS: 'See alarm OPI x/3334-ABC 123 4567/1 Uen',
178         CLEARING TYPE: Automatic
179     "
180     structure:
181         commonEventHeader:
182             presence: required
183             structure:
184                 version: {presence: required, value: 4.0.1}
185                 vesEventListenerVersion: {presence: required, value: 7.0.1}
186                 domain: {presence: required, value: fault}
187                 eventName: {presence: required, value: Fault_MyPnf-Acme_LogHasReachedFullCapacity}
188                 eventId: {presence: required}
189                 sequence: {presence: required}
190                 priority: {presence: required, value: Normal}
191                 reportingEntityName: {presence: required}
192                 sourceName: {presence: required}
193                 nfVendorName: {presence: required, value: Acme}
194                 startEpochMicrosec: {presence: required}
195                 lastEpochMicrosec: {presence: required}
196                 timeZoneOffset: {presence: required}
197         faultFields:
198             presence: required
199             structure:
200                 faultFieldsVersion: {presence: required, value: 4.0}
201                 alarmCondition: {presence: required, value: 'LogHasReachedFullCapacity'}
202                 eventCategory: {presence: required, value: 'PROCESSINGERRORALARM'}
203                 eventSourceType: {presence: required}
204                 specificProblem: {presence: required, value: 'Log Has Reached Full Capacity'}
205                 eventSeverity: {presence: required}
206                 vfStatus: {presence: required, value: Active}
207                 alarmAdditionalInformation: {presence: required, structure: {
208                     keyValuePair: {presence: required, structure: {key: {presence: required, value: source}, value: {presence: required}}},
209                     keyValuePair: {presence: required, structure: {key: {presence: required, value: probableCause}, value: {presence: required, value: 'FileError'}}},
210                     keyValuePair: {presence: required, structure: {key: {presence: required, value: additionalText}, value: {presence: optional}}},
211                     keyValuePair: {presence: required, structure: {key: {presence: required, value: additionalInfo}, value: {presence: optional}}}}
212                 }
213 ...