Bug 1042397
Summary: | [RFE][neutron]: leastrouter scheduler | |||
---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | RHOS Integration <rhos-integ> | |
Component: | openstack-neutron | Assignee: | Assaf Muller <amuller> | |
Status: | CLOSED ERRATA | QA Contact: | yfried | |
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | unspecified | CC: | amuller, chrisw, lpeer, markmc, nyechiel, oblaut, yeylon | |
Target Milestone: | Upstream M2 | Keywords: | FutureFeature, Triaged | |
Target Release: | 5.0 (RHEL 7) | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
URL: | https://blueprints.launchpad.net/neutron/+spec/lessrouter-scheduler | |||
Whiteboard: | upstream_milestone_icehouse-2 upstream_status_implemented upstream_definition_approved | |||
Fixed In Version: | 5.0-Beta/2014-05-15.2 | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1060966 (view as bug list) | Environment: | ||
Last Closed: | 2014-07-08 15:33:40 UTC | Type: | --- | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1003878 |
Description
RHOS Integration
2013-12-12 22:08:22 UTC
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 |