summaryrefslogtreecommitdiffstats
path: root/docs/Chapter8/ves_7_2/ves_event_listener_7_2.rst
AgeCommit message (Collapse)AuthorFilesLines
2020-11-19[VES spec] publishEventBatch support for stndDefineddeen19851-0/+5
publishEventBatch enhanced to support stndDefined events. All events in batch shall have teh same value of stndDefinedNamespace set. Change-Id: Ie038c000217d23965742f59e2e33c6e228260202 Signed-off-by: deen1985 <damian.nowak@nokia.com> Issue-ID: VNFRQTS-935 (cherry picked from commit 990427e6f7824fd25d9a8d77e43c7ba50b1d22d0)
2020-07-12Requirement ID Generation and RST ValidationLovett, Trevor1-101/+101
The new check.py script will now perform a variety of actions to simplify updates and ensure specific practices are followed for each update. The script has been integrated with tox and will run whenever the documentation is created. It can also be ran separately by just invoking python check.py. The script will perform a variety of automatic updates where possible, and provide a warning where auto-updates are not possible. The expecation is that all warnings are addressed before submitting for review, but given it is a new feature warnings do not block validation at this time. Here is a summary of the warnings and updates: Warnings: - Requirement missing required attributes - Invalid values for attributes - Invalid section header usage in any file - :keyword: and requirement mismatch Auto Updates: - Assigning :id: on new requirements where an ID missing - Adding :introduced: attribute on new requirements - Adding/correcting :updated: attribute on changed requirements Issue-ID: VNFRQTS-896 Signed-off-by: Lovett, Trevor <trevor.lovett@att.com> Change-Id: I283441330a139aa1c6e2e79f0c54c5979bf44642
2020-06-29stndDefined added to vesEventListener specdeen19851-15/+96
This includes (list might not be complete, as some editiorial updates have been done too): Adding a new "stndDefined" enum to VES Common Event Header "domain" property Adding a new VES Common Header property "stndDefinedNamespace" Adding stndDefinedFields structure to VES Common Event Change-Id: I8b327c850b1d6c18d252fc4f77e40df9c5672ce8 Signed-off-by: deen1985 <damian.nowak@nokia.com> Issue-ID: VNFRQTS-889 Signed-off-by: deen1985 <damian.nowak@nokia.com>
2020-06-15Splitting NF reqt from VES specLovett, Trevor1-607/+470
- Moved content in VES Event Listener spec that was specific to defining NF behavior to Monitoring requirements - Expanded requirements regarding protocol selection - Provided additional guidance for VES client configuration - Reorganized sections of Event Listener for a more logical flow - Fixed various small formatting issues in VES 7.2 spec Issue-ID: VNFRQTS-813 Signed-off-by: Lovett, Trevor <trevor.lovett@att.com> Change-Id: I4ca6fa4d846465c90520f8ebb133a1301d3509cf Signed-off-by: Lovett, Trevor <trevor.lovett@att.com>
2020-06-02Initial VES 7.2 Event Listener SpecLovett, Trevor1-0/+6220
This is just a copy of the 7.1.1 spec to enable tracking of changes Issue-ID: VNFRQTS-813 Signed-off-by: Lovett, Trevor <trevor.lovett@att.com> Change-Id: Ic09cc6da49181845ef3748d562821d01a6262906