Separate options for --nic when creating servers
Bug #1612898 reported by
Steve Martinelli
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-openstackclient |
Fix Released
|
Medium
|
David Rabel |
Bug Description
See https:/
We should deprecate --nic in favor of listing the actual options. This would also mean adding a --network and --port option. This avoiding the key value based --nic option.
We've already had a UX bug for this very issue: https:/
Changed in python-openstackclient: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
tags: | added: network |
Changed in python-openstackclient: | |
assignee: | nobody → Ukesh (ukeshkumar) |
Changed in python-openstackclient: | |
assignee: | nobody → David Rabel (rabel-b1) |
To post a comment you must log in.
nic option in openstack server create command's syntax is, net-uuid, v4-fixed- ip=ip-addr, v6-fixed- ip=ip-addr, port-id= port-uuid>
--nic <net-id=
It can be given multiple times, to create multiple interfaces in the VM-instance.
And so, if we split it into network-id / port-id options. How the
optional parameters, 'v4-fixed-ip' and 'v6-fixed-ip' can be handled ?
Ex: if we want two nic, first nic, don't have to pass v4-fixed-ip and second one, we have to pass the fixed ip. We couldn't map in this case.
with current command, we can give as below, 5678,v4- fixed-ip= 172.2.3. 8
--nic net-id=1234 --nic net-id=
with new implementation, how can we pass the v4-fixed-ip (172.2.3.8) to the second network ?,
--network 1234 --network 5678
Please clarify...