yahoo-eng-team team mailing list archive

[Hong Hui Xiao <xiaohhui@xxxxxxxxxx>]

Public bug reported:

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/

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

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

** Description changed:

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

-- 
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:
  New

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