Comment 4 for bug 1987093
Revision history for this message
| Rodolfo Alonso (rodolfo-alonso-hernandez) wrote | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Hi Sean:
Please correct me if I'm wrong. From the Neutron side, the goal of this BZ if to create an extension in the port resource (the dictionary passed to Nova) indicating if the port has "switchdev" capabilities. That will prevent Neutron (and any non-admin user) from modifying the port binding dictionary (that should be updated by Nova only). With this change, a non-admin user will be able to create a "switchdev" port without having write access to the port binding dict.
The "switchdev" does not depend on the network backend, we can have both kernel and "switchdev" ports in the same OVS instance. Via scheduling, we can decide what hosts have this kind of resource, but from Neutron we should be able to create this kind of resource (logical resource, you know Neutron does not create the L1 resources).
Regards.