yahoo-eng-team team mailing list archive

[Hong Hui Xiao <xiaohhui@xxxxxxxxxx>]

Public bug reported:

With address scope being enabled, networks now are in one ipv4 address
scope and one ipv6 address scope. But now, it is difficult to  find out
the address scopes that the network is in. User have to check in this
way: network->subnet->subnet pool -> address scope.

This bug is to add a read-only, derived attribute to the network as part
of the address scopes extension that will show related address scopes
when viewing a network through the API.

** Affects: neutron
     Importance: Undecided
     Assignee: Hong Hui Xiao (xiaohhui)
         Status: New


** Tags: address-scopes l3-ipam-dhcp

** Changed in: neutron
     Assignee: (unassigned) => Hong Hui Xiao (xiaohhui)

** Tags added: l3-ipam

** Tags removed: l3-ipam
** Tags added: l3-ipam-dhcp

** Tags added: address-scopes

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1547380

Title:
  Correlate address scope with network

Status in neutron:
  New

Bug description:
  With address scope being enabled, networks now are in one ipv4 address
  scope and one ipv6 address scope. But now, it is difficult to  find
  out the address scopes that the network is in. User have to check in
  this way: network->subnet->subnet pool -> address scope.

  This bug is to add a read-only, derived attribute to the network as
  part of the address scopes extension that will show related address
  scopes when viewing a network through the API.

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