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.
- Resource
- PNF
- Allotted (Contribution Posted)
- Network Function (perhaps related to rooting descriptors and instances below)
- Network Slicing
- Pnf
- Service
- Network Service
- Service Instance (Runtime)
- CFS reconcile (BBS Use Case)
- Infrastructure
- Multi-VIM/Clouid
- Cloud Region
- Common
- VES (Some Material Posted)
- License
- Rooting Descriptors and Instances
- Policy
- Other
- Onboarding and Runtime Model Classes
- Scaling
- Configuration
- Further HPA Modeling