so, after thinking more of the problem, I just feel that the current
codepath is making promises that it can't sustain. To be clear, NIC
ordering on a VM can sometimes be undeterministic depending on the OS.
For that precise reason, a new feature recently merged in Newton about allowing
NICs to b
My fault, one just pointed me out that we actually try to preserve NIC
ordering when calling Neutron :
https://github.com/openstack/nova/blob/286cb904055eec3525fb61b2a0f93b14448bdd3e/nova/network/neutronv2/api.py#L2522
Looks to me like a legit bug by the fact that when the user provides a
port in
We don't really support the NIC ordering in Nova AFAIK.
If you look at
https://developer.openstack.org/api-ref/compute/?expanded=create-server-detail#create-server
we just say for the 'networks' attribute that it's possible to pass multiple
UUIDs, either as ports or network IDs but we don't expl
3 matches
Mail list logo
