Versions Compared

Old Version 12

changes.mady.by.user Reuben Klein

Saved on

compared with

New Version 13

changes.mady.by.user Reuben Klein

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

APPC provides a VNF configuration repository with the latest working configuration for each managed VNF instance it is responsible for.

Scope

      • Support for complex ONAP use cases including vVOLTE (with vEPC)  and vCPE
      • Provide Generic VNF LCM commands for Northbound consumers (SO, Policy, CMO, DCAE, etc.) 
        • The implementation of LCM commands will use an uploaded VNF Yang model to infer an execution protocol and drive workflows. 
        • Design-time ability to attach recipes (specified by Directed Graphs, aka DGs) to specific VNF LCM  commands, or "Actions" received via the Northbound APIs.
      • Provide a model driven configuration API composed from a Yang-based VNF configuration model and set of templates to map payloads to the VNF configuration protocol.
        • Provide configuration repository APIs getLatestConfig, configAudit etc.
      • Manage the VNF operational state including Blocking, Sequencing and  Session Throttling
      • Provide conflict resolution for multiple LCM requests
      • Provide flexible deployment options such as HA, single node or geo-distributed deployment

      • Adaptation of additional NBI definitions established by ETSI-MANO using NFV-O to leverage existing APP-C functions which already exist, including:

        • Scale VNF
        • Terminate VNF
        • Query VNF
        • Operate VNF
        • Modify VNF Information
        • Get Operation Status 

      • Adaptation of NBI definition at the orchestration level by invoking existing

    • orchestration

      • orchestrator functions, including:

        • Create VNF Identifier

    • (Orchestrator function)

        • Delete VNF Identifier

    • (Orchestrator function)

      • Instantiate VNF

    • (Orchestrator function)

    • Build addition DGs to implement new ETSI defined NB APIs not currently supported by APP-C

      • Scale VNF to Level

      • Change VNF Flavour

      • Heal VNF

    • Support for GVNFM functionality through additional SB adapters to support: 
        •  bridging
          • Bridging to a compliant S-VFNM when this functionality is provided by the VNF
          • Utilize ETSI VNFD acquired from a VNF to define the configuration and management data model of the VNF.

      Proposed Architecture:

      Architecture Alignment:

      ...