Kubernetes clusters using ONAP Multicloud K8s Plugin Project for R4/R5 do not report hardware features to A&AI. Consequently during the CNF/VNF life cycle CNFs/VNFs that require or recommend specific hardware during instantiation cannot dynamically reach the correct cluster and node that provides the needed hardware capabilities.
...
The registrationHandler will then query the k8s cluster under registration using the Node App or Node Plugin code to get a list of nodes and the labels for each node.
- registrationHandler - onap/multicloud-k8s/src/k8splugin/api/registrationhandler.go
- Registers K8s cloud to K8s plugin using onap/multicloud-k8s/src/k8splugin/internal/connection/connection.go – check into if we need kubeconfig or ESR change
- Requires update of onap/multicloud-k8s/src/k8splugin/api/api.go
- Invokes AAI Client to K8s AAI Module to update AAI with Cloud/Tenant/Flavor information for the cluster
Node App or Node Plugin
- Node App - onap/multicloud-k8s/src/k8splugin/internal/app/node or onap/multicloud-k8s/src/k8splugin/internal/plugin/node.go
- Requests labels from nodes in K8s cluster
Requires update of onap/multicloud-k8s/src/k8splugin/internal/app/client.go extend to node Resource (helm.KubernetesResource does not have resource type)
Reporting of Cluster Info to AA&I
...
Where needed add resource limits and request to ResourceBundle charts. I.E.:
resources:
requests:
memory: "64Mi"
cpu: "250m"
limits:
memory: "128Mi"
cpu: "500m"Charts to Update
https://github.com/onap/multicloud-k8s/tree/master/kud/demo/firewall
...