Versions Compared

Key

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

...

  • Proposed name for the project: projectname
  • Proposed name for the repository: reponame

Project description:

  • Provide high level description of intended project and intended use case(s) and benefit, if needed.

Scope:

  • This project will be dedicated to determine how policy is captured and designed when designing and on-boarding VNF's and network services.
  • Specification of Policy aspects related to a VNF/service during design and on-boarding.


FROM THE DEEP DIVE:

Policy aspects related to a VNF/service needs, e.g. for lifecycle management of VNF/service, e.g. scaling, placement, security, fault response, telemetry, SLA, ... including how policies are designed/packaged/onboarded.

Policy repository for storage and lifecycle management of policy

  • Conflict Detection

Scope:

  • Deliver points of interoperability within ONAP for VNF On-boarding to capture VNF vendor specific policies
    • Classification of Policies
      • Placement
      • Resource allocation
      • Remediation Actions (eg. Scaling)
      • Compliance Checking (eg. Security)
      • Health
  • Instantiation and Day2Day OperationsDescribe 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.

...