Description
To attach a VF interface, you have to pass the pci address that is monitored to the API Call. However, VF interfaces themselves are the same. Instead of targeting VFs, the PF could be targeted, to avoid a lot of PCI addresses noise.
Given that #7671 is implemented, each VF PCI device will have its parent PF on its PCI monitoring entry. VFs with the same parent PF can be grouped to make the possible target PFs. Since each VF also has a record of whether it is assigned to a VM or not, a VF availability per PF can also be created.
Use case
Give me the first available VF from a given PF. Rather than manually selecting a VF.
Interface Changes
- In sunstone, add a new scheduling mode, where PFs are shown and their availability is displayed, alongside their eswitch mode
PFs will have a VF availability.
- In CLI
onevm nic-attach --pf $pf_name
Additional Context
Please feel free to add any other context or screenshots about the feature request here. Or any other alternative you have considered to address this new feature.
Progress Status
Description
To attach a VF interface, you have to pass the pci address that is monitored to the API Call. However, VF interfaces themselves are the same. Instead of targeting VFs, the PF could be targeted, to avoid a lot of PCI addresses noise.
Given that #7671 is implemented, each VF PCI device will have its parent PF on its PCI monitoring entry. VFs with the same parent PF can be grouped to make the possible target PFs. Since each VF also has a record of whether it is assigned to a VM or not, a VF availability per PF can also be created.
Use case
Give me the first available VF from a given PF. Rather than manually selecting a VF.
Interface Changes
PFs will have a VF availability.
onevm nic-attach --pf $pf_nameAdditional Context
Please feel free to add any other context or screenshots about the feature request here. Or any other alternative you have considered to address this new feature.
Progress Status