VMware: Openstack can not adopt more than one existing port groups in vCenter
Bug #1284559 reported by
Lijun Jiang
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
When booting an instance via Openstack, the network bridge used by nova comes from the attribute integration_bridge in nova.conf (networks are managed via neutron, nova-network will be deprecated). integration_bridge can only specify one bridge name and there is no way to give more than one bridges.
vCenter allows more than one port-groups to be created. If vCenter is controlled by openstack, Openstack can not make all port-groups in vCenter able used via openstack.
| Changed in nova: | |
| assignee: | nobody → Lijun Jiang (lijunjbj) |
| tags: | added: vmware |
| Changed in nova: | |
| status: | New → Incomplete |
| status: | Incomplete → Confirmed |
| importance: | Undecided → Medium |
| Changed in nova: | |
| status: | Confirmed → In Progress |
| Changed in nova: | |
| status: | In Progress → Confirmed |
| assignee: | Lijun Jiang (lijunjbj) → nobody |
Revision history for this message
| Markus Zoeller (markus_z) (mzoeller) wrote Cleanup EOL bug report | #1 |
| Changed in nova: | |
| importance: | Medium → Undecided |
| status: | Confirmed → Expired |
To post a comment you must log in.
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
Valid example: CONFIRMED FOR: LIBERTY