Background :
- Proposal for Release 2 / Beijing from Vodafone on Centralization of Parser / Parser As A Service
- Various projects in ONAP are using different Parsers for either model design (en-coding) or model de-coding
- The same function is being performed at many places and there is no consistency in Parser Approach across projects
- Vodafone's proposal is to centralize the Parser as part of Common Services Layer and expose that As-A-Service
- Which will bring consistency in Parsing function within ONAP and paves the way for an ultimate model driven stack
- This also opens up the platform implementation approach for Parsers and provide a placeholder within ONAP for a "Parser Surgery"
- This common placeholder can be used to on-board multiple parsers while retaining the parser exposure to consumers (design / runtime components) via an abstracted API
- Another proposal from ZTE on the same concept, "Parser As A Service" was received with a proposal for taking this up in R2 with OPNFV parser
- Almost the same Paerser idea was received from ZTE along with another proposal for a centralized / platform based Run Time Catalogue by ZTE
- ZTE has given even greater details of the proposed architecture and how the common / central parser as a service would look like
- SDC team presented with an idea of exposing SDC parser as a service, proposal was to do a pilot / PoC in R2 for exposing SDC Parser As A Service from SDC project itself
Proposal As Part of 9th January 2018 Modelling Subcommitte Call : Atul.Purohit1@vodafone.com to conduct a series of calls with different stakeholders to identify the right approach and put up a proposal for R2/R3 PoC / trial / adoption and bring to modelling sub-committe for consideration. The same was noted here : Modeling sub-committee meetings#committeemeetings-20180109MeetingAgenda&Minutes
Meeting / Call notes for 16th Janury 2018 :