...
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 DM | 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 DM | ETSI NFV SOL001 v2.5.1 | VNFD - the ONAP internal data model should be able to reflect ETSI SOL001 VNFDs provided for onboarding | SDC, VFC | CCVPN, vCPE | |||||
| Resource DM | 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 | |||||
| Resource IM | ETSI NFV IFA011 v2.5.1 | Update the VNFD IM to align with IFA011 v2.5.1 | SDC, VFC | N/A related to DM SOL001 progress | |||||
| Resource IM | PNFD | Create onboarding PNFD IM | SDC, SO, VFC | N/A | |||||
| Resource IM | VNFD | SDC, VFC | VoLTE | N/A impact R4 DM? | |||||
| Service DM | ETSI NFV SOL001 v2.5.1 | NSD - the ONAP internal data model should be able to reflect ETSI SOL001 NSD provided for onboarding | SDC, SO, VFC | CCVPN | |||||
| Service IM | ETSI NFV IFA014 v2.5.1 | Nested Service | SDC, SO, VFC | CCVPN | TBA | High | guochuyi |
...