Based on timeplan of modeling subcommittee, high level requirements need to be finished by M0/M1,
There are 4 categories of high level requirement,
- 1) Will be implemented and included in the release 3
- 2) Documentation after implemented, or implemented but not in the release
- 3) Lower Priority:
- 4) Experimental:
The first category is that those requirement will be implemented and commited by the impacted projects in this release
the second category will document the current implementation in those projects.
Other two categories like lower priority and experimental will not be included in the release 3, the contributor will work with best effort to influence future release.
Owners of each requirement needs to coordinate the modeling spec commitment and code commitment with PTLs of impacted project.
1) Will be implemented and included in the release 3
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | Mapping to M1 requirement | Owner |
---|---|---|---|---|---|---|---|---|---|
Resource | |||||||||
|
2) Documentation after implemented, or implemented but not in the release
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | Mapping to M1 requirement | Owner |
---|---|---|---|---|---|---|---|---|---|
Service | |||||||||
Resource | |||||||||
Below tables are not downgrade, but casablanca won't make it
3) Lower Priority:
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | Owner |
---|---|---|---|---|---|---|---|---|
Service | ||||||||
Resource | ||||||||
Infrastructure | ||||||||
4) Experimental:
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | Owner |
---|---|---|---|---|---|---|---|---|
Resource | ||||||||
Per discussion in Paris, requirements can be based on:
...
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 user-7acab Weitao Gao will lead 2nd task working on $4 recommendation:
...