| Table of Contents |
|---|
...
| Microservices of Openness Infrastructure mode | Description | Deployment method | Deployment of the component | Propose to integrate |
|---|---|---|---|---|
| eaa | application/service registration, authentication etc | deployment | edge node | yes |
| edgedns | for client to access microservices in edge node | daemonset (propose to change to deployment) | edge node | yes |
| interfaceservice | similar with providernet implemented in ovn4nfv-k8s-plugin | daemonset | edge node | no, will use ovn4nfv-k8s-plugin's provider network |
| cnca | Core Network Configuration: Configure the access network (e.g., LTE/CUPS, 5G) control plane | deployment | controller | no |
| syslog | log service for openness | daemonset | controller & edge node | no |
| multus | enabling attaching multiple network interfaces to pods | daemonset | controller & edge node | Already covered by ONAP4K8s - KUD |
| nfd | node feature discovery | daemonset | controller & edge node | Already covered by ONAP4K8s - KUD |
| sriov | sriov network device plugin & sriov cni | daemonset | controller & edge node | Already covered by ONAP4K8s - KUD |
| topology manager | kubernetes topology manager | Kubelet component | controller & edge node | Work in Progress to upgrade the K8s v16.0 integrate into ONAP4K8s - KUD |
| CMK | CPU Manager | part of kubelet | controller & edge node | Work in Progress - Integrate into ONAP4K8s - KUD |
| bios | Used for change BIOS and firmware configuration: CPU configuration, Cache and Memory configuration, PCIe Configuration, Power and Performance configuration, etc | privileged Pod | controller & edge node | Required for ICN? Already in ICN Metal3, could be enabled part of it |
| fpga | Open Programmable Acceleration Engine (OPAE) package consisting of a kernel driver and user space FPGA utils package that enables programming of the FPGA is used. sriov is used to configure the FPGA resources such as Virtual Functions and queues | pod | controller & edge node | Need to integrate into ONAP4K8s - KUD with FPGA device |
...
- If creating one EAA for every tenant (logical cluster): micro-services on different edge clouds which are kubernetes clusters should be able to communicate with each other by registering the services to the EAA and consuming the services from the EAA on different edge clouds. For example: μs2 is stateful and needs to communicate with other μs2 on different edge clouds to synchronize the states.
- If creating one EAA for every kubernetes cluster, EAAs need to synchronize the states because EAAs are stateful: The certs of EAAs on different edge clouds has are signed by different Root CACAs which are generated by Openness ansible scripts. What’s more, producing application and consuming application will get certs from EAA and those certs are signed by EAA’s certcerts. And this will cause the producing application and consuming application on different edge cloud can’t communicate with each other because their certs are on different certificate chains. To solve this issue, the certs of EAAs should be signed by the same orchestrator. For example, ICN DCM (Distributed Cloud Manager) can take this role:
https://wiki.onap.org/pages/viewpage.action?pageId=76875956