Project Overview
Both Python and Java based Parser will not be updated in R4, the R4 release will use the same as previous release.
New proposal to work on the generic parser which is micro service based. and it is treated as POC for Dublin release
New component capabilities for Dublin, i.e. the functional enhancements
- a generic parser
- Impact on Functional Menu for the usecase flows to different components
- VNF/PNF/Service Tosca Data model parsing APIs
- Pkg management APIs. In order to provide more granular APIs,the generic parser own its pkg storage,the consumer can also leverage this pkg management capability for pkg storage.
New or modified interfaces
- PGeneric tosca parser APIs
Interface naming
API List:
Generic tosca parser APIs- parser APIs., such as:
POST /api/parser/v1/parser
POST /api/parser/v1/parsernsd
POST /api/parser/v1/parserpnfd
POST /api/parser/v1/parservnfd - PKG management APIs, such as :
- GET /Gets
POST /api/parser/v1/service_packages
GET /api/parser/v1/service_packages
GET /api/parser/v1/service_packages/{csarId}
DELETE /api/parser/v1/service_packages/{csarId} Reference to the interfaces
What are the system limits
ONAP
n.Generic Parser
- Only support tosca data model parsing in Dublin release
- Focus on UUI, VNFSDK ,VF-C requirements to do POC n Dublin release
Involved use cases, architectural capabilities or functional requirements
5G usel.CCVPN, vCPE
Listing of new or impacted models used by the project (for information only)
None.
Page Comparison
General
Content
Integrations