You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »


Per discussion in Paris, 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.


the committee agreed

1) Thinh Nguyenphu will lead 1st task force working on #1,#2 recommendations:

Recommend#1: member companies prepare and submit these additional extension to ETSI NFV IFA and SOL WG toward v2.6.1 or later. (agreed) Recommend#2: ONAP adopts SOL001 Type extension method, per clause 5.6 (agreed)

2) shitao li Victor Gao will lead 2nd task  working on $4 recommendation:

Recommend #4: SDC supports SOL001 v2.5.1 type definitions (VNFD, PNFD, NSD) (agreed)

3) Thinh Nguyenphu will report NSD comparision with service csar in 2 weeks, 

All 3 work will be reported to Anatoly weekly DM conference call, Anatoly will ask final approval from Modeling subcommittee 


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
  • No labels