Versions Compared

Old Version 29

changes.mady.by.user Haibin Huang

Saved on

compared with

New Version Current

changes.mady.by.user damian.nowak

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.

This Frankfurt Release epic (

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyMULTICLOUD-729
) adds the ability to discover, report and use hardware features during CNF/VNF life cycle to accelerate use cases using ONAP.

Overall Flow Diagram for HPA for K8s

Image RemovedImage Added

Discovery and Labeling of Node Features

...

below table is example how to convert node feature label to flavor properties

node feature labelOpenstack flavor properties

feature.node.kubernetes.io/network-sriov.capable=True

feature.node.kubernetes.io/network-sriov.configured=True

feature.node.kubernetes.io/pci-1200_8086.present=True


Comments: The other parameter we can set default because node feature label can not provide.

Image Modified

We can get the latest mapping table in HPA Policies and Mappings + K8s

...

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

...