...
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 | |||||
| Resource | 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 | PNFD | Create onboarding PNFD IM | SDC, SO, VFC | N/A | |||||
| Resource | VNFD | New requirement for the VNFD | SDC, VFC | VoLTE | N/A impact R4 DM? | ||||
| Service | ETSI NFV SOL001 v2.5.1 | NSD | SDC, SO, VFC | CCVPN | |||||
| Service | Nested Service | SDC, SO, VFC | CCVPN | TBA | High | guochuyi |
...
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 | Former user (Deleted) | |||
| Resource | allotted resource | To document the allotted resource IM as implemented by SDC | N/A | N/A | |||||
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
Common | Policy | create policy IM, reflect current policy project implementation | Policy | N/A | ||||
| VES | create VES IM | DCAE | N/A | |||||
Infrastructure | ||||||||
4) Experimental:
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | Owner | Resource|
|---|---|---|---|---|---|---|---|---|---|
Common | License | create license IM | |||||||
| Root | create super classes for current models | SDC, AAI |
Per discussion in Paris, requirements can be based on:
...