yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxxxxxxxxxx>]

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


** Changed in: nova
   Importance: Medium => Undecided

** Changed in: nova
       Status: Confirmed => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1284559

Title:
  VMware: Openstack can not adopt more than one existing port groups in
  vCenter

Status in OpenStack Compute (nova):
  Expired

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1284559/+subscriptions