Bug 1030658
| Summary: | RHOS should use impl_qpid v2 by default | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Alvaro Lopez Ortega <aortega> | |
| Component: | openstack-nova | Assignee: | Xavier Queralt <xqueralt> | |
| Status: | CLOSED ERRATA | QA Contact: | Ami Jeain <ajeain> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 4.0 | CC: | ajeain, aortega, apevec, breeler, dallan, ddomingo, derekh, eglynn, fpercoco, hateya, jlibosva, ndipanov, xqueralt, yeylon | |
| Target Milestone: | rc | |||
| Target Release: | 4.0 | |||
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | openstack-nova-2013.2-5.el6ost | Doc Type: | Bug Fix | |
| Doc Text: |
The QPID driver's v2 topology was introduced to specifically address the slow growth of orphaned direct exchanges over time. By default, however, services still use the original v1 topology of the QPID driver; the v2 topology has to be explicitly configured via the 'qpid_topology_version = 2' parameter.
With this fix, the Compute service's distribution configuration file (/usr/share/nova/nova-dist.conf) now contains the 'qpid_topology_version = 2' parameter. This effectively sets the QPID driver's v2 topology as the default.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1030664 1031022 1031023 1031025 1031027 (view as bug list) | Environment: | ||
| Last Closed: | 2013-12-20 00:35:49 UTC | Type: | Bug | |
| 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: | 1030664, 1031022, 1031023, 1031025, 1031027 | |||
|
Description
Alvaro Lopez Ortega
2013-11-14 21:22:44 UTC
Based on a comment russellb made earlier regarding a different but related issue... should we not just change this in the dist conf files for each of these projects? That would make this less of a packstack issue perhaps and just a single bug on each of the projects (nova, heat, ceilometer, cinder) to change the default dist conf @pmyers: I agree. It sounds like a much more sane approach. Oops! I meant to reassign it to Nova. Sorry for that. failed QA: # grep -R qpid_topology_version /etc grep: /etc/httpd/run/wsgi.26690.1.1.sock: No such device or address /etc/ceilometer/ceilometer.conf:#qpid_topology_version=1 /etc/heat/heat.conf.bak:#qpid_topology_version=1 /etc/heat/heat.conf:#qpid_topology_version=1 /etc/nova/nova.conf:#qpid_topology_version=1 /etc/cinder/cinder.conf:#qpid_topology_version=1 # rpm -qa |grep openstack-nova openstack-nova-api-2013.2-5.el6ost.noarch openstack-nova-console-2013.2-5.el6ost.noarch openstack-nova-compute-2013.2-5.el6ost.noarch openstack-nova-scheduler-2013.2-5.el6ost.noarch openstack-nova-common-2013.2-5.el6ost.noarch @Ami, the key is set in the nova-dist.conf file under /usr/share/nova. Sorry for not mentioning this before. [root@rhos1 ~]# rpm -qa openstack-nova-common openstack-nova-common-2013.2-5.el6ost.noarch [root@rhos1 ~]# grep -R qpid_topology_version /usr/share/nova/ /usr/share/nova/nova-dist.conf:qpid_topology_version=2 verified: # rpm -qa openstack-nova-common openstack-nova-common-2013.2-5.el6ost.noarch # grep -R qpid_topology_version /usr/share/nova/ /usr/share/nova/nova-dist.conf:qpid_topology_version=2 (In reply to Xavier Queralt from comment #7) > @Ami, the key is set in the nova-dist.conf file under /usr/share/nova. Sorry > for not mentioning this before. But commented default in nova.conf should be changed too to reflect dist.conf default! (In reply to Alan Pevec from comment #9) > (In reply to Xavier Queralt from comment #7) > > @Ami, the key is set in the nova-dist.conf file under /usr/share/nova. Sorry > > for not mentioning this before. > > But commented default in nova.conf should be changed too to reflect > dist.conf default! Argh, I forgot to update this. I will do it for the async release. 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-2013-1859.html *** Bug 1030664 has been marked as a duplicate of this bug. *** |