As pointed out by the examples in the other replies, you would essentially
have to support every possible parameter to "neutron port-create" in "nova
boot". That's creating unnecessary knowledge of neutron in nova. If you had
to eliminate one of the two, the second workflow should actually be the o
>There seemed to be two ways to create a VM via cli:
>
>1) use neutron command to create a port first and then use nova command to
>attach the vm to that port(neutron port-create.. >followed by nova boot --nic
>port-id=)
>2)Just use nova command and a port will implicitly be created for you(nova
Hi
When you create a port separately, you can specify additional fixed IPs,
extra DHCP options. But with 'nova boot' you cannot.
Also if you need an instance with several nics, and you want that each nic
has its own set of security groups, you should create ports separately.
Because 'nova boot --s
There seemed to be two ways to create a VM via cli:
1) use neutron command to create a port first and then use nova command to
attach the vm to that port(neutron port-create.. followed by nova boot --nic
port-id=)2)Just use nova command and a port will implicitly be created for
you(nova boot --n
