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

Project Name:

  • Proposed name for the project: Reference VNFs
  • Proposed name for the repository: demo

Project description:

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

Resources:

  • Primary Contact Person
  • Names, gerrit IDs, and company affiliations of the committers
  • Names and affiliations of any other contributors
  • Project Roles (include RACI chart, if applicable)

Other Information:

  • link to seed code (if applicable)
  • Vendor Neutral
    • if the proposal is coming from an existing proprietary codebase, have you ensured that all proprietary trademarks, logos, product names, etc., have been removed?
  • Meets Board policy (including IPR)

Use the above information to create a key project facts section on your project page

Key Project Facts

Project Name:

  • JIRA project name:
  • JIRA project prefix:

Repo name:
Lifecycle State:
Primary Contact:
Project Lead:
mailing list tag [Should match Jira Project Prefix] 
Committers:
foo@bar.com
baz@qux.com
*Link to TSC approval: 
Link to approval of additional submitters: 

  • No labels