...
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.
| Openness Infrastructure mode component | Need to integrate? |
|---|---|
| eaa | no |
| edgedns | yes |
| interfaceservice | no, will use ovn4nfv-k8s-plugin's provider network |
| cnca | no |
| syslog | no |
| multus | no |
| nfd | no |
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:
| Code Block | ||||
|---|---|---|---|---|
| ||||
apiVersion: openness.akraino.org/v1alpha1
kind: Opennessdns
metadata:
name: example-dns
spec:
node: node1
dns:
- record_type: A
fqdn: openvino.openness
addresses: 10.16.0.10
- record_type: A
fqdn: www.google.com
addresses: 10.16.0.11 |
The config agent behavior
- Monitor openness edge dns CRD
- When a CRD instance is created:
- Call interfaceservice to set the dns
- When a CRD instance is deleted:
- Call interfaceservice to delete the dns