yahoo-eng-team team mailing list archive

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

Cleanup
=======

This bug report has the status "Incomplete" since more than 30 days
and it looks like that there are no open reviews for it. To keep
the bug list sane, I close this bug with "won't fix". This does not
mean that it is not a valid bug report, it's more to acknowledge that
no progress can be expected here anymore. You are still free to push a
new patch for this bug. If you could reproduce it on the current master
code or on a maintained stable branch, please switch it to "Confirmed".

** Changed in: nova
       Status: Incomplete => Won't Fix

-- 
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/1430521

Title:
  nova network-create is ignoring --bridge when using the VlanManager

Status in OpenStack Compute (nova):
  Won't Fix
Status in python-novaclient:
  Confirmed

Bug description:
  The `nova network-create` is *silently* ignoring the --bridge when
  using the VlanManager. The bridge name is hardcoded to "br%s" % vlan.

  https://github.com/openstack/nova/blob/stable/juno/nova/network/manager.py#L1361

  [root@jhenner-vmware ~(keystone_admin)]# nova network-create novanetwork --fixed-range-v4 192.168.32.0/22 --bridge br101 --bridge-interface br101 --uuid 874ab2f1-c57d-464a-8a3f-5dda76ac7613 --vlan 102
  [root@jhenner-vmware ~(keystone_admin)]# nova network-show novanetwork
  +---------------------+--------------------------------------+
  | Property            | Value                                |
  +---------------------+--------------------------------------+
  | bridge              | br102                                |
  | bridge_interface    | br101                                |
  | broadcast           | 192.168.35.255                       |
  | cidr                | 192.168.32.0/22                      |
  | cidr_v6             | -                                    |
  | created_at          | 2015-03-10T20:25:41.000000           |
  | deleted             | False                                |
  | deleted_at          | -                                    |
  | dhcp_server         | 192.168.32.1                         |
  | dhcp_start          | 192.168.32.3                         |
  | dns1                | 8.8.4.4                              |
  | dns2                | -                                    |
  | enable_dhcp         | True                                 |
  | gateway             | 192.168.32.1                         |
  | gateway_v6          | -                                    |
  | host                | -                                    |
  | id                  | ca6b6f02-9f40-4578-89c6-9c8ca6d29bee |
  | injected            | False                                |
  | label               | novanetwork                          |
  | mtu                 | -                                    |
  | multi_host          | True                                 |
  | netmask             | 255.255.252.0                        |
  | netmask_v6          | -                                    |
  | priority            | -                                    |
  | project_id          | -                                    |
  | rxtx_base           | -                                    |
  | share_address       | False                                |
  | updated_at          | -                                    |
  | vlan                | 102                                  |
  | vpn_private_address | 192.168.32.2                         |
  | vpn_public_address  | -                                    |
  | vpn_public_port     | 1000                                 |
  +---------------------+--------------------------------------+


  It would be good to have the bridge name configurable when using
  VlanManager because when the nova vcenter driver is used, nova is
  checking whether there is a "port group" in the vcenter of same name
  as bridge used in nova-network.

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