...
Below High Level Requirements have been agreed by modeling subcommitee with code commitment promise to Dublin releaseto El Alto release, modeling subcommittee request related to projects to approve those related submission.
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 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 SOL001 v2.5.1 | Ericsson | Ericsson.||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
There are other 4 categories of high level requirement,
...
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 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 | 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 onboardingSDC, SO, VFC | CCVPN | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Service IM | ETSI NFV IFA014 v2.5.1 | 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 | Internal Service IMTo document the internal Service IM as implemented by SDC and SO to support the usecaseN/ACCVPNChuyi Guo Onboarding NS IM | To document the onboarding NS IM as supported by the usecase | N/ACCVPNChuyi Guo Resource | allotted resource | To document the allotted resource IM as implemented by SDCN/A | N/A | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Below tables are not downgrade, but casablanca won't make it
...
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | Owner | 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 | Common | License | create license IM | Root | create super classes for current models | SDC, AAI | Kevin Scaggs | |||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Per discussion in Paris, requirements can be based on:
...