Comment 0 for bug 2013228
Revision history for this message
| John Garbutt (johngarbutt) wrote Non-admin users unable to create SR-IOV switch dev ports | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
9199653
demo site
(Get the code!)
Currently only admin users can create SR-IOV direct ports that are marked as switch_dev, i.e. the ones that do OVS hardware offload.
From and end user, the direct nic, hardware offloaded or not, by ovs ml2 or ovn, all appear the same. Its operator internal setup details on what happens. Why do we expose this to the end user in this way?
Example operator deployments we work with:
* all SR-IOV direct ports are offloaded using ovn
* all SR-IOV direct ports are offloaded using ovs ml2
* all SR-IOV direct ports created using legacy SR-IOV
* (not a use case I have, but theoretically its possible) some mix of the above
Ideally the user doesn't care between these, and the neutron API is able to extract away the implementation details of getting a direct type of vnic.