Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

  1. 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

  2. New component capabilities for Dublin, i.e. the functional enhancements

    1. a generic parser
      • 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.

  3. New or modified interfaces

    • Generic tosca parser APIs

  4. Interface naming

    1. 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 :

        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}

  5. Reference to the interfaces

    1. Generic Parser API

  6. What are the system limits

    1. Generic Parser  

      1.   Only support tosca data model parsing in Dublin release
      2.   Focus on UUI, VNFSDK ,VF-C requirements to do POC n Dublin release 

  7. Involved use cases, architectural capabilities or functional requirements

    1. CCVPN

  8. Listing of new or impacted models used by the project (for information only)

    1. None.

  • No labels