...
Openness Integration Design
Openness Microserivces
We are planning to integrate Openness Infrastructure mode. The following figure shows the components microservices of Openness infrastructure mode and also lists the components microserivces that we propose to integrate.
| Components Microservices of Openness Infrastructure mode | Description | Daemonset or 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 | controller | no | |
| syslog | log service for openness | daemonset | controller & edge node | no |
| multus | enabling attaching multiple network interfaces to pods | daemonset | controller & edge node | no, will be covered by ONAP4K8S |
| nfd | node feature discovery | daemonset | controller & edge node | no, will be covered by ONAP4K8S |
| sriov | sriov network device plugin & sriov cni | daemonset | controller & edge node | no, will be covered by ONAP4K8S |
| topology manager | kubernetes topology manager | Kubelet component | controller & edge node | no, will be covered by ONAP4K8S |
| CMK | CPU Manager | part of kubelet | controller & edge node | no, will be covered by ONAP4K8S |
| bios | BIOS and Firmware Configuration using Intel® System Configuration Utility which is a command-line utility that can be used to save and restore BIOS and firmware settings to a file or to set and display individual settings | privileged Pod | controller & edge node | |
| 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 |
Openness dns config agent design
Openness extends kubectl command line to set edgedns (Described in OpenNESS 19.12 Investigation part). To integrate Openness with ICN, we will not use this but create a config agent to set edge dns. This config agent will monitor below CRD:
...
- Monitor openness edge dns CRD
- When a CRD instance is created:
- Call edgedns on the specific edge node to set the dns
- When a CRD instance is deleted:
- Call edgedns on the specific edge node to delete the dns
Task List
...
- Ansible scripts to build microservice docker images and push them to docker repository
- Use helm charts to run microservice in kubernetes