| Table of Contents |
|---|
...
- grub is used to add hugepages to grub and hugepages are not useful for integration OpenNESS with ICN.
- cnca is not required for integration.
- multus has already been integrated with ICN.
- nfd will be integrated directly with ICN.
2. Centos uses yum to install packages and we need to use apt for Ubuntu.
3. Some packages which will be installed by ansible scripts should be removed or replaced:
- Some Centos packages doesn't exist on Ubuntu and these packages should be removed. For example, yum-utils, device-mapper-persistent-data.
- Some Centos packages' name are different for Ubuntu. For example, python2-pip should be replaced with python-pip, python-devel should be replaced with python-dev.
4. Selinux is not used on Ubuntu and need to remove the ansible scripts configuring selinux.
5. Epel repository is for Centos and Ubuntu doesn't need this repository.
6. Proxy will be set for yum and need to change the scripts to set proxy for apt.
7. Docker installation for Centos and Ubuntu are different. Need to change the scripts following the installation guide. For example: the docker repository is different for Centos and Ubuntu.
8. Auditd is used for Docker. Auditd is delivered with Centos by default but Ubuntu needs to install auditd.
9. Kubernetes installation for Centos and Ubuntu are different. Need to change the scripts following the installation guide. For example: gpg key is different for Centos and Ubuntu, ubuntu use deb and Centos uses repository.
10. cgroups driver is different for Centos (systemd) and Ubuntu (cgroups). By default, cgroups driver is cgroups and need to remove the ansible scripts which configures cgroups driver to systemd.
11. firewalld is used in Centos and need to change to ufw which is used by Ubuntu.
12. Packages are different for installing openvswitch and ovn. Centos uses RPMs. Ubuntu uses openvswitch-switch, ovn-common, ovn-central and ovn-host.
13. Topology manager and CPU manager is configured for edge node's kubelet. No need to use topology manager and can remove these.
Openness Integration Design
We are planning to integrate Openness Infrastructure mode. The following figure shows the components of Openness infrastructure mode and also lists the components that we want to integrate.
...
- not required for integration.
- multus has already been integrated with ICN.
- nfd will be integrated directly with ICN.
2. Centos uses yum to install packages and we need to use apt for Ubuntu.
3. Some packages which will be installed by ansible scripts should be removed or replaced:
- Some Centos packages doesn't exist on Ubuntu and these packages should be removed. For example, yum-utils, device-mapper-persistent-data.
- Some Centos packages' name are different for Ubuntu. For example, python2-pip should be replaced with python-pip, python-devel should be replaced with python-dev.
4. Selinux is not used on Ubuntu and need to remove the ansible scripts configuring selinux.
5. Epel repository is for Centos and Ubuntu doesn't need this repository.
6. Proxy will be set for yum and need to change the scripts to set proxy for apt.
7. Docker installation for Centos and Ubuntu are different. Need to change the scripts following the installation guide. For example: the docker repository is different for Centos and Ubuntu.
8. Auditd is used for Docker. Auditd is delivered with Centos by default but Ubuntu needs to install auditd.
9. Kubernetes installation for Centos and Ubuntu are different. Need to change the scripts following the installation guide. For example: gpg key is different for Centos and Ubuntu, ubuntu use deb and Centos uses repository.
10. cgroups driver is different for Centos (systemd) and Ubuntu (cgroups). By default, cgroups driver is cgroups and need to remove the ansible scripts which configures cgroups driver to systemd.
11. firewalld is used in Centos and need to change to ufw which is used by Ubuntu.
12. Packages are different for installing openvswitch and ovn. Centos uses RPMs. Ubuntu uses openvswitch-switch, ovn-common, ovn-central and ovn-host.
13. Topology manager and CPU manager is configured for edge node's kubelet. No need to use topology manager and can remove these.
Openness Integration Design
We are planning to integrate Openness Infrastructure mode. The following figure shows the components of Openness infrastructure mode and also lists the components that we propose to integrate.
| Components of Openness Infrastructure mode | Description | Daemonset or Deployment | 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 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