We actually intentionally did not implement this in the code, as we have another model for doing the same thing: rather than telling nova all of the network config you want, you create a quantum port with a particular config (e.g., IP address, etc.), and then pass that port in when booting a VM using --nic port=id=XYZ. The goal here is that we didn't want the set of options that you pass to --nic to explode to include everything that quantum will support in the future. That would be a mess for the nova folks.
Given that nova already supported to the v4-fixed-ip flag pre-quantum, there's a reasonable argument that we should try and support that flag just for backward compat.
Yes, this should work.
We actually intentionally did not implement this in the code, as we have another model for doing the same thing: rather than telling nova all of the network config you want, you create a quantum port with a particular config (e.g., IP address, etc.), and then pass that port in when booting a VM using --nic port=id=XYZ. The goal here is that we didn't want the set of options that you pass to --nic to explode to include everything that quantum will support in the future. That would be a mess for the nova folks.
Given that nova already supported to the v4-fixed-ip flag pre-quantum, there's a reasonable argument that we should try and support that flag just for backward compat.