AMQP retry options not exposed

Bug #1445025 reported by Jorge Niedbalski on 2015-04-16
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack nova-cloud-controller charm
Wishlist
Unassigned
nova-cloud-controller (Juju Charms Collection)
Medium
Jorge Niedbalski

Bug Description

There are a some AMQP retry options that on some environments would be required to adjust manually.

rabbit_max_retries = 0 (IntOpt) Maximum number of RabbitMQ connection retries. Default is 0 (infinite retry count).
rabbit_retry_backoff = 2 (IntOpt) How long to backoff for between retries when connecting to RabbitMQ.
rabbit_retry_interval = 1 (IntOpt) How frequently to retry connecting with RabbitMQ.

I think we should support this over our charms, and perhaps improve the openstack default values.

Tags: sts Edit Tag help

Related branches

Changed in nova-cloud-controller (Juju Charms Collection):
assignee: nobody → Jorge Niedbalski (niedbalski)
tags: added: sts
Changed in nova-cloud-controller (Juju Charms Collection):
status: New → In Progress
Liam Young (gnuoy) on 2017-01-05
Changed in nova-cloud-controller (Juju Charms Collection):
importance: Undecided → Medium
James Page (james-page) on 2017-02-23
Changed in charm-nova-cloud-controller:
assignee: nobody → Jorge Niedbalski (niedbalski)
importance: Undecided → Medium
status: New → In Progress
Changed in nova-cloud-controller (Juju Charms Collection):
status: In Progress → Invalid
Changed in charm-nova-cloud-controller:
status: In Progress → New
assignee: Jorge Niedbalski (niedbalski) → nobody
James Page (james-page) on 2017-09-27
Changed in charm-nova-cloud-controller:
status: New → Triaged
importance: Medium → Wishlist
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers