...
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 and Service | TOSCA 1.2 | ONAP onboarding data model (TOSCA) and internal data model should be based on OASIS TOSCA 1.2 core syntax and normative types | SDC, SO, VFC | ?? | ?? | |||||||||
Resource | ETSI NFV SOL001 v2.5.1 | VNFD | SDC, VFC | CCVPN | ||||||||||
| Resource | ETSI NFV | PNFD - the ONAP internal data model (AID)should be able to reflect ETSI SOL001 PNFDs provided for onboarding. (committed goal) '''''''''''''''' Could an Onboarded PNFD also be internally mapped to the second ONAP internal model (nfv tosca types) ? Could two internal descriptors coexist in the same internal SDC package ? (stretch goal) | SDC | Ericsson | ||||||||||
| Service | ETSI NFV SOL001 v2.5.1 | NSD | SDC, SO, VFC | CCVPN | ||||||||||
| Service | Nested Service | SDC, SO, VFC | CCVPN | TBA | High | Chuyi Guo |
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 |
|
| N/A |
|
|
| |||
| Onboarding NS IM | To document the onboarding NS IM as supported by the usecase |
|
|
| HighHigh | user-7acab | |||
| Resource | |||||||||
Below tables are not downgrade, but casablanca won't make it
...