Updating vnic type is not working
Bug #1719268 reported by
Vasyl Saienko
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.1 |
Fix Committed
|
Undecided
|
Unassigned | |||
R3.1.1.x |
Fix Committed
|
Undecided
|
Unassigned | |||
R3.2 |
Fix Committed
|
Undecided
|
Unassigned | |||
R3.2.3.x |
Fix Committed
|
Undecided
|
Unassigned | |||
R4.0 |
Fix Committed
|
Undecided
|
Unassigned | |||
R4.1 |
Fix Committed
|
Undecided
|
Unassigned | |||
Trunk |
Fix Committed
|
Undecided
|
Unassigned | |||
OpenContrail |
New
|
Undecided
|
Unassigned |
Bug Description
Contrail blocks updating VNIC type [0], however it is a legal use case when using Ironic (baremetal provisioner) [1] due to several reasons:
1. With mixed clouds user may not know if instance will be placed on KVM or baremetal server.
2. Nova always create a ports with 'normal' vnic type, but even if it can pick vnic type dynamically we still need to update it for case when user pre-created a port (see case 1)
3. Ironic updates vnic type when trigger port binding in Neutron [1]
description: | updated |
To post a comment you must log in.
Review in progress for https:/ /review. opencontrail. org/35137
Submitter: Vasyl Saienko (<email address hidden>)