Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/lessrouter-scheduler. Description: Currently, we only have one scheduler called "Chance" which schedules virtual routers randomly. The idea of this blueprint is to bring a new scheduler which schedules virtual routers on the Neutron L3 agent node which hosts the less virtual routers number. Specification URL (additional information): None
Moving to POST based on upstream status (Implemented).
please review test plan https://tcms.engineering.redhat.com/cases/printable/?plan=12307
Reviewed.
verified RDO-Icehouse on RHEL6.5 Topology controller with EXTRA l3-node (l3 contains l3- and metadata- agents) # rpm -qa | grep -E "neutron|packstack" openstack-neutron-2014.1-0.5.b2.el6.noarch python-neutron-2014.1-0.5.b2.el6.noarch python-neutronclient-2.3.4-1.el6.noarch openstack-neutron-openvswitch-2014.1-0.5.b2.el6.noarch openstack-packstack-2013.2.1-0.29.dev956.el6.noarch Test Plan: https://tcms.engineering.redhat.com/plan/12307/multiple-l3-nodes
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2014-0848.html