Versions Compared

Old Version 3

changes.mady.by.user Marco Platania

Saved on

compared with

New Version 4

changes.mady.by.user Marco Platania

Saved on

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 onboardingon-boarding, deployment, and ONAP closed-loop operations work.

Scope:

  • Describe the functionality to be provided by the project.  Please provide the full intended scope of the project; not just what is intended for the project's first release.
  • Specify any interface/API specification proposed,
  • Identity a list of features and functionality will be developed.
  • Identify what is in or out of scope. During the development phase, it helps reduce discussion.Two basic VNFs, namely a virtual firewall and a virtual load balancer (with virtual DNSs), have been provided. One of the objectives of the project is to extend the features of the vFirewall and vLoadBalancer. New reference VNFs will be built to show new functionalities that will be added to the ONAP platform in the next releases.

Scope:

  • List of features and functionality 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
    • Common aspects to vFirewall and vLoadBalancer
      • Platform independence (Rackspace, vanilla Openstack, Azure, ...)
  • 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

Architecture Alignment:

  • How does this project fit into the rest of the ONAP Architecture?
    • Please Include architecture diagram if possible
    • What other ONAP projects does this project depend on?
  • How does this align with external standards/specifications?
    • APIs/Interfaces
    • Information/data models
  • Are there dependencies with other open source projects?
    • APIs/Interfaces
    • Integration Testing
    • etc.

...