This commit fixes incorrect way for choosing VF in
SR-IOV binding driver.
Previously sriov-device-plugin has choosen device
by it's own way while CNI choosed first available VF.
This entities did not know anything about each other's
choice.
Now SR-IOV binding driver gets a list of used by
kubelet devices with help of Pod Resources Client, then
chooses device from this list which is not used by pod
yet and passes an appropriate VF into container's
network namespace.
Also this commit contains tools for cluster upgrade.
Reviewed: https:/ /review. opendev. org/656482 /git.openstack. org/cgit/ openstack/ kuryr-kubernete s/commit/ ?id=5206717f084 180c2d3cc994775 f36f05f5475315
Committed: https:/
Submitter: Zuul
Branch: master
commit 5206717f084180c 2d3cc994775f36f 05f5475315
Author: Danil Golov <email address hidden>
Date: Mon Apr 29 17:29:25 2019 +0300
Provide a proper way to choose VF in CNI
This commit fixes incorrect way for choosing VF in
SR-IOV binding driver.
Previously sriov-device-plugin has choosen device
by it's own way while CNI choosed first available VF.
This entities did not know anything about each other's
choice.
Now SR-IOV binding driver gets a list of used by
kubelet devices with help of Pod Resources Client, then
chooses device from this list which is not used by pod
yet and passes an appropriate VF into container's
network namespace.
Also this commit contains tools for cluster upgrade.
Change-Id: I5b24981f715966 369b05b8ab157f8 bfe02afc2d4
Closes-Bug: 1826865
Signed-off-by: Danil Golov <email address hidden>