Versions Compared

Key

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

...

  • The goal of the project is to build reference VNFs that can be used to show how the ONAP platform manages VNFs installation and lifetime management. Reference VNFs can also be used as a means to test the platform itself, e.g. verify whether VNFs on-boarding, deployment, and ONAP closed-loop operations work. Two basic VNFs, namely a virtual firewall and a virtual load balancer (with virtual DNSs), have been provided. One of the The objectives of the project is are to extend the features of the improve and maintain the vFirewall and vLoadBalancer . New reference VNFs will be built that show new functionalities that will be added to the ONAP platform in the next releases.

Scope:

  • List of features and functionalities that will be developed:
    • vFirewall
      • Allow ONAP to change vFirewall rules during execution
      • Filter out traffic based on predefined policies (currently, only port 8080 can receive traffic)
      • Report to the DCAE collector per-service/per-port metrics about the traffic going through
    • vLoadBalancer
      • vDNS health checking and vDNS failure reporting to ONAP
    • Common aspects to vFirewall and vLoadBalancer
      • Platform independence (Rackspace, vanilla Openstack, Azure, ...)
      • Visualization tools that allow users to monitor the behavior of the reference VNFs as well as the effect of ONAP closed-loop operations against the VNFs
      • Tools that allow users to interact with the reference VNFs (e.g. alter the behavior of a VNF so as to violate predefined policies, in order to trigger ONAP closed-loop operations)
    • New reference VNFs will be built that demonstrate new use cases defined for ONAP
  • Out of scope:
    • Password management
    • API securing
    • Disaster recovery
    • High availability

...