...
| PROJECT | PTL | User Story / Epic | Requirement | ||||||||
| A&AI | NO IMPACT | ||||||||||
| AAF | NO IMPACT | ||||||||||
| APPC | NO IMPACT | ||||||||||
| CLAMP | NO IMPACT | ||||||||||
| CC-SDK | NO IMPACT | ||||||||||
| DCAE | Epic 1:Standards Defined VES Event -Update VES Event Listener -Extend DCAE to use contents of the new stndDefinedNamespace field to route -DCAE-SDK to execute validations of JSON objects to stnds schemas -DCAE-SDK to perform Stage 2 validation -DCAE-CBS to support the schemaBroker function -new initContainer in DCAE to load schema information -CBS API to load the schema info to the CBS/schemaBroker
| ||||||||||
| DMaaP | NO IMPACT | ||||||||||
| External API | NO IMPACT | ||||||||||
| MODELING | Epic 2: VES Data Model and Requirements Update -Update VES Data Model with new domain enum and field see VES 7.1
| ||||||||||
Multi-VIM / Cloud | NO IMPACT | ||||||||||
| OOF | NO IMPACT | ||||||||||
| POLICY | NO IMPACT | ||||||||||
| PORTAL | NO IMPACT | ||||||||||
| SDN-C | NO IMPACT | ||||||||||
| SDC | NO IMPACT | ||||||||||
| SO | NO IMPACT | ||||||||||
| VID | NO IMPACT | ||||||||||
| VNFRQTS | Epic 2: VES Data Model and Requirements Update -Add a new domain field enumeration value stndDefined -Add a new field in the common header, stndDefinedNamespace -Add a new field structure, stndDefinedFields
| ||||||||||
| VNF-SDK | NO IMPACT | ||||||||||
| CDS | NO IMPACT |
List of PTLs:Approved Projects
*Each Requirement should be tracked by its own User Story in JIRA
...
Information Element Name | VES Information Model | ||||||||
| Points of Contact | Information Element Main Contact - marge.hillis Oskar Malm Information Modeling Contact - marge.hillis Schema Definition Contact - damian.nowak | ||||||||
| Related Use Cases | C&PS Configuration & Persistency Service (for the CM notifications) | ||||||||
Participating ONAP Components | DCAE (DCAE VES Event Listener) | ||||||||
| Related JIRA |
| ||||||||
Description | VES Information Model Adding a new valid enum for the domain and new field for the namespace only populated if the domain is stndDefined. | ||||||||
Related Standards & Industry Activities | 3GPP Standards TS28.532 | ||||||||
Attributes | Domain (Existing Attribute), adding a new enum value "stndDefined" stndDefinedNamespace (NEW Attribute); type: (string) / enum ?? stndDefined field added to VES common schema. | ||||||||
Relationships | VES Information Model Does not change the VES Object class or Object class relationships in the Information Model. | ||||||||
Originator | The xNF sends the stndDefined Event, and is the "owner" (source of truth) of the data. The payload (e.g. CM information) is owned by the xNF and originates sending the VES event to ONAP. | ||||||||
| Consumers | DCAE receives this information through VES event listener How DCAE uses it: it routes it to the proper DMaAP topic based on the stndDefined domain and namespace. Micro-services (future) could subscribe to these events listening for these topics. How would micro-services use it (future): Depends on the event (type of namespace events), depends what purpose of the micro-services. Nothing outside of ONAP will access this information. | ||||||||
Producers | The namespace may be updated if additional standards bodies join in on the definition for the emission of events supported by ONAP. For example IETF, broadband forum etc. It allows ONAP to process general events from various standards bodies. Condition when they update - New category of action, (CM, PM, FM) needs to be added. | ||||||||
Steward | Where will this information stored and maintained in ONAP? Valid model - in the VES event listener specification. | ||||||||
| Impacted APIs & Schemas | VES Schema (loaded and defined in design time) in the xNF onboarded artifacts. API/Swaggers - DCAE API for DMaaP. DCAE to VES header (modified) DCAE to SDK API (modified) DCAE to CBD API (modified) | ||||||||
Information Modeling Status | This is scheduled in the R7 Modeling planning page. The Wiki page: ONAP R7 Modeling High Level Requirements It is being tracked by the Modeling-370 Jira which can be found here:
Status: It is active for the current release, this use case has been accepted. The model is being developed. | ||||||||
Schema Definition Status | A schema was provided is located in the architecture presentationpresentation (on this page): https://wiki.onap.org/download/attachments/84640792/Arch%20Presentation%20STD%20Defined%20Event%20in%20ONAP%20May%2019%202020.pptx?version=1&modificationDate=1589918847000&api=v2 | ||||||||
ONAP Release Priority | R7 Guilin - Model work has been approved to proceed. In the R7 planning page: Guilin Release Requirements , the Modeling-370 is under REQ-327 and TSC Priority 0 "Go" |
...