ONAP R6 Modeling High Level Requirements - Brainstorm v0

Owned by Hui Deng
Jul 01, 2019
1 min read



Per discussion on R3, requirements can be based on:

  • Release / project specific needs

  • Recognized 'future' needs

  •  Documenting existing models

Some concepts may be complex enough, if we wait for the release / project requirement, we will be too late to properly develop the concept.



Following are a few development areas to consider. 

  1. Resource

    1. PNF

    2. Allotted (Contribution Posted)

    3. Network Function (perhaps related to rooting descriptors and instances below)

    4. Network Slicing

    5. Pnf

  2. Service

    1. Network Service 

    2. Service Instance (Runtime)

    3. CFS reconcile (BBS Use Case)

  3. Infrastructure

    1. Multi-VIM/Clouid

    2. Cloud Region

  4. Common

    1. VES (Some Material Posted)

    2. License 

    3. Rooting Descriptors and Instances

    4. Policy

  5. Other

    1. Onboarding and Runtime Model Classes 

    2. Scaling

    3. Configuration

    4. Further HPA Modeling