Gliffy Diagram | ||||
---|---|---|---|---|
|
Gliffy Diagram | ||||
---|---|---|---|---|
|
Table of Contents |
---|
The ETSI-based CNF support is conforming to IFA 011, IFA029 and IFA040. Based on the ETSI specification progresses, we plan to apply necessary changes.
...
- Mapping VNF-Descriptor to SDC AID DM?
- How to identify Pods in AAI?
- Package multiple NFs into a single CNF and manage them independent from each other. (Deployment flavors, aspects, …)
- Building an NF which spans multiple CNFs. The single CNF would not necessarily be a self-sufficient entity anymore. (Network Services)
- CI/CD based upgrades of microservices within a CNF. (ChangeVnfPackage)
ONAP ETSI-Alignment Overall Architecture (Various Options)
Gliffy Diagram macroId 51fb53a3-23cd-4be3-b8f2-f536ec8752ae name ONAP ETSI SDO for VNF-CNF pagePin 20
Model-Driven Orchestration
...
(various options)
- SO supports dual CNF support: one is the CNF direct leveraging K8S Adapter, K8S Plugin (in MultiCloud) path and one is the ETSI-Alignment path, leveraging SOL005 Adatper, NFVO, SOL003 Adapter and VNFM.
- SDC supports a common onboarding mechanism for both CNF paths
Gliffy Diagram name ONAP ETSI CNF Orchestration - Model Driven
Gliffy Diagram name ONAP ETSI CNF Orchestration - Model Driven - Honolulu pagePin 2
Gliffy Diagram macroId 818d4c33-f30e-4ef5-9369-feb7a4edbf2f name ONAP ETSI-ORAN CNF Orchestration - Honolulu pagePin 1
Configuration Sequence
2
Possible O-RAN connection Architecture (Stretch goal for Honolulu)
Gliffy Diagram macroId 818d4c33-f30e-4ef5-9369-feb7a4edbf2f name ONAP ETSI-ORAN CNF Orchestration - Honolulu pagePin 22
Generic CNF Adapter Architecture (Future Consideration)
Gliffy Diagram macroId a0ae48ef-6549-4356-ba20-7afaa80a17f3 name ONAP ETSI GCNFM Architecture pagePin 8
Pipeline Diagram
Gliffy Diagram | ||||
---|---|---|---|---|
|
Configuration Sequence
PlantUML Macro | ||
---|---|---|
| ||
@startuml
participant Service_Designer
participant SDC
participant ETSI_Catalog_Manager
participant MultiCloud
participant CDS
participant OSS_BSS
participant SO
participant SO_ | ||
PlantUML Macro | ||
| ||
@startuml
participant Service_Designer
participant SDC
participant ETSI_Catalog_Manager
participant MultiCloud
participant CDS
participant OSS_BSS
participant SO
participant SO_NFVO
participant CI
participant SDNC
participant VNFM
participant VNF
participant CNF
autonumber
group Design Time
Service_Designer -> CDS : Design CBA
Service_Designer -> SDC : Attach CBA to SDC Service CSAR
SDC -> ETSI_Catalog_Manager : Distribute ETSI packages
SDC -> SDNC : Distribute SDC Catalog
SDC -> MultiCloud : Distribute SDC Catalog
end
group Run Time - Instantiation
OSS_BSS -> SO : Request Instantiate
SO -> SDNC : Get Resource Assignment
SDNC -> CDS: Get resource assignment
SO -> SO_NFVO : Request thru SOL005 (with instantiation parameter values)
SO_NFVO -> VNFM : Request thru SOL003 (with instantiation parameter values)
VNFM -> SO_NFVO : Request Grant CNF/VNF Resources
SO_NFVO -> VNFM : Grant CNF/VNF Resources
alt CNF
VNFM -> CISM : CNF instantiation request
else VNF
VNFM -> VIM : VNF instantiation request
end
VNFM -> SO_NFVO : Instantiate Successful
SO_NFVO -> SO : Instantiate Successful
SO -> OSS_BSS : Instantiation Successful
end
group Run Time - Post Instantiation
opt Configuration A
OSS_BSS -> SO : Request Configure
SO->SO_NFVO : Request ModifyVNFInfo thru SOL005
SO_NFVO -> CDS_SS : Config-Assign action\n for saving CNF/VNF day-1 config
SO_NFVO -> CDS_BP : Config-Deploy action\n for CNF/VNF config
CDS_BP --> CDS_BP : Read config from DB
CDS_BP -> SDNC : Invoke SDNC ODL
alt CNF
SDNC -> CNF: push config
else VNF
SDNC -> VNF: push config
end
SO_NFVO -> SO : Configuration Successful
SO -> OSS_BSS : Configuration Successful
end
opt Configuration B
OSS_BSS -> SO : Request Configure
SO->SO_NFVO : Request ModifyVNFInfo\nthru SOL005
SO_NFVO -> VNFM : Request ModifyVNFInfo\nthru SOL003
alt VNF
VNFM -> VNF : Configuration Request\nthru Ve-Vnfm
else CNF
VNFM -> CNF : Configuration Request\nthru Ve-Vnfm
end
VNFM -> SO_NFVO : Configuration Response
SO_NFVO -> SO : Configuration Successful
SO -> OSS_BSS : Configuration Successful
end
opt Configuration C
OSS_BSS -> SO : Request Configure
SO -> CDS_SS : Config-Assign action\n for saving CNF/VNF day-1 config
SO -> CDS_BP : Config-Deploy action\n for CNF config
CDS_BP --> CDS_BP : Read config from DB
CDS_BP -> SDNC : Invoke SDNC ODL
alt CNF
SDNC -> CNF: push config
else VNF
SDNC -> VNF: push config
end
SO -> OSS_BSS : Configuration Successful
end
end
@enduml |
...
- The VNFD introduces a new resource template OsContainerDesc for OS containers.
- The ResourceDefinition information element used in the grant request message needs to be enabled to reference resource templates for OS containers, the same way as the other resource template
- Enhance the ResourceDefinition information element attributes with references to OS container resource definition types and resource templates.
- OsContainer Type is added
- Reference to OsContainerDesc is added
IFA 011 411 Draft Proposal addition to VipCpd
- VipCpd in SOL001 2.7.1 describes the mapping of a “virtual IP” address to connection points in a VNF.
- Either HA (Active/Standby) or Load Balancing.
Proposed for 4.1.1
- Use VipCp to model K8S service connectivity (under discussion)
- AdditionalVipData – Expose information about a port and service data
- Name of the VIP (uService)
- L4 Protocol exposed (TCP, UDP, SCTP, )
- Port exposed
- intCpd attribute is optional (changes from 1..N to 0..N)
- Service Data
- L7 info (unspecified in VNF-D)
SOL001 VNFD Mapping to SDC AID DM
- TBD
ONAP Component Requirements
SDC
- TBD
SO
- TBD
SO NFVO
- TBD
SOL003 Adapter
- TBD
ETSI Catalog Manager
- TBD
AAI
Data Modeling
VNFC
VNFC has the 1:1 relationship with MCIO requesting compute/storage resources
- TBD
CP
- CP has the 1:1 relationship with MCIO requesting networking resources
- TBD
VID
- TBD
UUI
- TBD
OOF
- TBD
CIR
...
- resource templates.
- OsContainer Type is added
- Reference to OsContainerDesc is added
IFA 011 411 Draft Proposal addition to VipCpd
- VipCpd in SOL001 2.7.1 describes the mapping of a “virtual IP” address to connection points in a VNF.
- Either HA (Active/Standby) or Load Balancing.
Proposed for 4.1.1
- Use VipCp to model K8S service connectivity (under discussion)
- AdditionalVipData – Expose information about a port and service data
- Name of the VIP (uService)
- L4 Protocol exposed (TCP, UDP, SCTP, )
- Port exposed
- intCpd attribute is optional (changes from 1..N to 0..N)
- Service Data
- L7 info (unspecified in VNF-D)
SOL001 VNFD Mapping to SDC AID DM
- TBD
ONAP Component Requirements
SDC
- TBD
SO
- TBD
SO NFVO
- TBD
SOL003 Adapter
- TBD
ETSI Catalog Manager
- TBD
AAI
Data Modeling
VNFC
VNFC has the 1:1 relationship with MCIO requesting compute/storage resources
- TBD
CP
- CP has the 1:1 relationship with MCIO requesting networking resources
- TBD
VID
- TBD
UUI
- TBD
OOF
- TBD
CIR
- TBD
To be analyzed.
CISM | Kubernetes Manager/master |
CIS | Kubernetes worker node |
MCIO | Pods, Services, Deployments, ReplicaSets, StatefulSets? |
MCIOP | Helm chart? |
container workload management service | Control Plane, workload resources |
containerized workloads | Docker container? |
Compute management service | ? |
compute infrastructure resource | ? Availability Zone |
storage management service | ? |
storage infrastructure resource | PV PVC |
network management service | ? node network |
network infrastructure resource | ? LB? |
configuration management service | ? Config Map |
MCIO configurations | ? |