According to ONAP R10 R11(Kohn) Release requirement input LINK Release Planning: Kohn
Reporting on the R10 R11 release to the TSC will begin on DATE, so the deadline for the input of high level requirement will be M0: DATE 2021.
...
1) Will be implemented in R10 R11 by code commitment to different impacted different impacted projects/components.
2) Will document only for only for the R10 R11 release.
3) Documentation after implemented in prior release
...
Category 1) will be implemented in the R10 R11 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 | Use Case Owner | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| resource IM |
| Create CNF Object in AAI associated with vf-module/generic-vnf/cloud-region that holds basic information about ANY CNF's k8s resource | AAI, SO, Multicloud (Implementation already present) | CNFO (
| Konrad Bańka , Lukasz Rajewski | Konrad Bańka , Lukasz Rajewski | TBD | TBD | Konrad Bańka , Lukasz Rajewski | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| resource IM |
| Create ASD onboarding information model | SDC |
| resource IM |
| Create ASD onboarding data model | SDC |
| resource IM |
| Create ASD onboarding package model | SDC |
| resource IM |
| NSD requirements for ASD deployment | SDC | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Jira Legacy | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| server | System Jira | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 | key | REQ-993||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Category 2) Will document
...
only for the
...
R11 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 | Use Case Contact | resource/service IM/DM | ETSI CNF model | update CNF IM to align with latest ETSI IFA011 and IFA014 v4.2.1 specs, and document the DM aligned with SOL001 v4.2.1 | SDC, SO | ETSI alignment | Fernando Oliveira | NA | resource IM | Abstract Topology Model | Create a Topology Information Model jointly with O-RAN and harmonize interworking among ONAP components | N/A | Tony Finnerty | resource IM |
| Design and implement high level AAI model for CNF resources. | AAI, SO, Multicloud (Implementation already present) | CNFO (
| N/A (in this release) | TBD | TBD | Seshu Kumar Mudiganti , Lukasz Rajewski | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Category 3) Documentation Only after implemented in prior release
...