Page Comparison

...

Policy and OOF will use the same path to discover capabilities of K8s nodes as are done for OpenStack. We are using the same data model (OpenStack cloud-region/tenant/flavors) from AA&I. OOF will use AA&I information to home particular CNF workloads to cloud-regions which contain requested features. When K8s plugin instantiates said workloads Kubernetes will read nodeSelector preferences and place each workload on nodes which contain needed features to accelerate their function.

High Level Task Overview

• Ensure NFD (Node feature discovery - K8S CNCF project) deploy to Multicloud + K8s Plugin is working and labeling Kubernetes nodesnodes 

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key MULTICLOUD-741

• Add registrationHandler to K8s Plugin and expand K8s Plugin API to work with ESR VIM registration of K8s ClustersClusters 

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key MULTICLOUD-740

  
  
  • Use POST/DELETE/GET of http://{{MSB_IP}}:{{MSB_PORT}}/api/multicloud-k8s/v1/{{cloud-owner}}/{{cloud-region-id}}/registry 
  • Ensure registrationHandler can get K8s feature labels - (labels discovered and placed by NFD representing hardware features)
  • Ensure registrationHandler can populate A&AI cloud-region/tenant/compute flavors based on cluster under registration
    

    Jira Legacy
    server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key MULTICLOUD-739

  • Register K8s cluster internally with the K8s Plugin
• Add Node App in K8s Plugin to retrieve node labels from a cluster
• Identify and Address any gaps in policy and OOF to do match making of CNFs/VNFs using K8s Plugin
  
  

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key MULTICLOUD-742

Identify & Address Gaps in AAI/ESR Cloud Registration

Identify & Address Gaps to Policy and OOF for K8s HPA Homing

...