yahoo-eng-team team mailing list archive

[OpenStack Infra <1547380@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/282942
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=635581912f2da69ac178a8779c2374619801dd19
Submitter: Jenkins
Branch:    master

commit 635581912f2da69ac178a8779c2374619801dd19
Author: Hong Hui Xiao <xiaohhui@xxxxxxxxxx>
Date:   Sun Feb 21 22:18:39 2016 -0500

    Correlate address scope with network
    
    With address scope being enabled, networks now are in one ipv4
    address scope and one ipv6 address scope.
    
    This patch adds derived attributes to the network as part of the
    address scopes extension that will show related address scopes
    when viewing a network through the API.
    
    APIImpact
    
    Change-Id: Ib1657636033ad2c0009d50ebe7c5ae4f72f6b175
    Closes-Bug: #1547380


** Changed in: neutron
       Status: In Progress => Fix Released

-- 
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:
  Fix Released

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