| 2019-09-05 10:55:55 |
James Hilling |
bug |
|
|
added bug |
| 2019-09-05 10:57:17 |
James Hilling |
description |
On many occasions, we have to set the following within the application containers for rabbitmq-server:
$ sudo rabbitmqctl set_policy -p openstack $POLICY_NAME '$QUEUE_REGEX' '{"max-length": 99 }' --apply-to queues --priority 1
We do this in order to limit the amount of messages that can exists within a specific queue.
It would be useful if there was a way to set this from the charm parameters. |
On many occasions, we have to set the following within the application containers for rabbitmq-server:
$ sudo rabbitmqctl set_policy -p openstack $POLICY_NAME '$QUEUE_REGEX' '{"max-length": $INTEGER_VALUE }' --apply-to queues --priority 1
We do this in order to limit the amount of messages that can exists within a specific queue.
It would be useful if there was a way to set this from the charm parameters. |
|
| 2019-09-05 10:59:44 |
James Hilling |
description |
On many occasions, we have to set the following within the application containers for rabbitmq-server:
$ sudo rabbitmqctl set_policy -p openstack $POLICY_NAME '$QUEUE_REGEX' '{"max-length": $INTEGER_VALUE }' --apply-to queues --priority 1
We do this in order to limit the amount of messages that can exists within a specific queue.
It would be useful if there was a way to set this from the charm parameters. |
On many occasions, we have to set the following within the application containers for rabbitmq-server:
$ sudo rabbitmqctl set_policy -p openstack $POLICY_NAME '$QUEUE_REGEX' '{"max-length": $INTEGER_VALUE }' --apply-to queues --priority 1
We do this in order to limit the amount of messages that can exists within a specific queue.
It would be useful if there was a way to set this from the charm parameters.
Example:
sudo rabbitmqctl set_policy -p openstack event-sample-overflow '^event.sample$' '{"max-length": 99 }' --apply-to queues --priority 1 |
|
| 2019-09-05 14:13:36 |
James Hilling |
bug |
|
|
added subscriber Canonical IS BootStack |
| 2019-09-05 14:18:41 |
James Hilling |
description |
On many occasions, we have to set the following within the application containers for rabbitmq-server:
$ sudo rabbitmqctl set_policy -p openstack $POLICY_NAME '$QUEUE_REGEX' '{"max-length": $INTEGER_VALUE }' --apply-to queues --priority 1
We do this in order to limit the amount of messages that can exists within a specific queue.
It would be useful if there was a way to set this from the charm parameters.
Example:
sudo rabbitmqctl set_policy -p openstack event-sample-overflow '^event.sample$' '{"max-length": 99 }' --apply-to queues --priority 1 |
On many occasions, we have to set the following within the LXD containers for rabbitmq-server:
$ sudo rabbitmqctl set_policy -p openstack $POLICY_NAME '$QUEUE_REGEX' '{"max-length": $INTEGER_VALUE }' --apply-to queues --priority 1
We do this in order to limit the amount of messages that can exists within a specific queue.
It would be useful if there was a way to set this from the charm parameters.
Example:
sudo rabbitmqctl set_policy -p openstack event-sample-overflow '^event.sample$' '{"max-length": 99 }' --apply-to queues --priority 1 |
|
| 2019-09-06 08:12:41 |
Alex Kavanagh |
rabbitmq-server (Juju Charms Collection): status |
New |
Triaged |
|
| 2019-09-06 08:12:54 |
Alex Kavanagh |
rabbitmq-server (Juju Charms Collection): importance |
Undecided |
Wishlist |
|
