yahoo-eng-team team mailing list archive

[OpenStack Infra <1522677@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/253330
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=5160d4e2ae285c62ab52c9dfc61121f8ca4ecd57
Submitter: Jenkins
Branch:    master

commit 5160d4e2ae285c62ab52c9dfc61121f8ca4ecd57
Author: Hong Hui Xiao <xiaohhui@xxxxxxxxxx>
Date:   Fri Dec 4 00:19:00 2015 -0500

    Make sure AZAwareWeightScheduler base on weight of agent
    
    Problem details can be found in bug description. AZ here stands
    available zone.
    
    heapq.heapify() will sort tuple according to the first element. If
    the first element is equal, then the second element is used. When
    creating a new network, each AZ doesn't hold the network. So, the
    AZ handling list is actually a name ordered list. As a consequence,
    when creating a new network, a certain AZ will always be used,
    for example, 'nova1' in ['nova1', 'nova2', 'nova3'].
    
    This patch will sort the resource_hostable_agents firstly, so that
    the AZ that holds dhcp-agent with least load comes first. Then use
    min() to get the first AZ.
    
    Change-Id: Id57b4656337ab8f1bd2dc3e8bd679a23778a2dea
    Closes-Bug: #1522677


** 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/1522677

Title:
  AZAwareWeightScheduler is not totally based on weight

Status in neutron:
  Fix Released

Bug description:
  The AZ(available zone) for network has been enable with the merging of
  [1]. I try in local devstack with latest code.

  1) I deploy 3 dhcp-agent in 3 AZs (nova1, nova2, nova3).

  2) set the dhcp_agent_per_network=1, don't set
  default_availability_zones, and set network_scheduler_driver =
  neutron.scheduler.dhcp_agent_scheduler.AZAwareWeightScheduler

  3) create 10 networks without specifying the availability_zone_hints

  10 networks all go to nova1. It is not a reasonable result.

  [1] https://review.openstack.org/#/c/204436/

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