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 3 Next »

NFVO

Functionality: Registration
Registration with MSB by using vfc-nfvo-lcm. Input format is JSON.

Functionality: NS Package
Onboarding a new NS Package by using vfc-nfvo-lcm. Input format is JSON.
Query NS Package by using vfc-nfvo-lcm.
Delete NS Package by using vfc-nfvo-lcm. 

Functionality: NF Package
Onboarding a new NF Package by using vfc-nfvo-lcm. Input format is JSON.
Query NF Package by using vfc-nfvo-lcm.
Delete NF Package by using vfc-nfvo-lcm. 

Functionality: NS Instance
Create a new NS instance by using vfc-nfvo-lcm. Input format is JSON.
Query NS instance by using vfc-nfvo-lcm.
Delete NS instance  by using vfc-nfvo-lcm. 

GVNFM

Functionality: Registration
Registration with MSB by using vfc-vnfm-vnflcm. Input format is JSON.

Registration with MSB by using vfc-vnfm-vnfres. Input format is JSON.

Registration with MSB by using vfc-vnfm-vnfmgr. Input format is JSON.

Functionality: VNF Deployment
Create a new VNF instance by using vfc-vnfm-vnflcm. Input format is JSON.
Deploy a new VNF instance by using vfc-vnfm-vnflcm. Input format is JSON.
Query  VNF instance by using vfc-vnfm-vnflcm.

Functionality: VNF Termination
Terminate VNF instance by using vfc-vnfm-vnflcm. Input format is JSON.
Delete VNF instance by using vfc-vnfm-vnflcm. Input format is JSON.


EMS Driver Use Cases Test Plan

(This is a sample EMS Driver Use Cases Document using EMS Driver functionality deliverables as an example.)

Each high level functionality area below should be implemented as a separate Test Plan in the Integration repo.

Functionality: CM/PM Data Collection

  • Driver Health check
  • Start CM/PM data collection task
  • Load strategy configuration
  • Periodically download file from EMS by EMS Driver
  • Parse data in EMS Driver
  • Generate formatted xml+csv data file and create the file ready notification in EMS      Driver.
  • Finish CM/PM data collection task

Functionality: Alarm Data Collection

  • Driver Health check
  • Start Alarm data collection task
  • Load strategy configuration and connect alarm socket interface
  • Receiving alarm data from EMS by EMS Driver
  • Parse data in EMS Driver
  • Alarm Standardization and send alarm send by EMS Driver.

Functionality: EMS Info Configuration Manager

  • Driver Health check
  • Configuration of EMS/NMS connection information and the periodic collection strategy.

Functionality: Task Scheduler

  • Driver Health check
  • Create collection task
  • Dipose collection policy
  • Stored the CM/PM data

 Functionality: Service Register

  • Driver manager registration
  • Driver Health check
  • Discover the Microservice Bus
  • Register service to the Microservice Bus 
  • Unregister service from the Microservice Bus 
  • Query service from the Microservice Bus
  • Driver manager unregistration

 Functionality: Northbound Interface

  • Driver Health check
  • CM/PM/Alarm Data queue
  • CM/PM/Alarm/Data dispatch
  • Request from Rest service interface dipose
  • CM/PM/Alarm data file ready notification and send by REST service interface


  • No labels