© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
If I understand it correctly, it's a normal use-case when booting a new SR-IOV interface (like NFV) to not attach any IPs to that machine, i.e. create a VM which is connected to a network (that network might not have any subnets) and logically connect the VMs' to the needed endpoint. In this case the interface doesn't need to have an IP address (they might be able to communicate using some L2 protocol). In this case, the tenant must know the 'port' concept (or his setup is useless).
In this use case, it might be a good idea to allow non-admin tenants to create new IP-less ports using Horizon. In regard to clutter, if it is indeed only an addition of another checkbox/button (didn't check to see), it shouldn't be too bad IMO, and if anything it provides a unified interface for both admin and non-admin users.
Do note that I'm not overly expert in NFV - Itzik, can you have someone who actually works on NFV and SR-IOV in the Neutorn side to post their inputs on this subject?