RabbitMQ/Erlang do not properly determine available RAM when running in
containerised environment, plus default value for watermark is 0.4, which is
low for nodes running RabbitMQ only.
Some additional information:
https://www.rabbitmq.com/memory.html
Change-Id: I1738c66be0e698568881b2c64d5d456db851af4d
Depends-On: Iadd0529d166ef1dad1697215bbc181104a7b926e
Depends-On: Ibc6e8b91055f411b058505d14c2d83fbc826cdd4
Depending on security.tls.enabled switch disables or enables secured
communications between RabbitMQ, etcd and the rest of the world.
Change-Id: If9d376a7808e44a4845c78d3d6e4267bfb80848b
Depends-On: I574d64082e77f49024f49aa7b30c4f2f6cc044ac
Depends-On: I3f05ce795beade0af12eb3426df759a1af8806af
Depends-On: Ib4b3ea4da7c1f641b9ab0223226348de5eac94df
According to https://www.rabbitmq.com/man/rabbitmq-env.conf.5.man.html,
rabbitmq-env.conf should contain variables without RABBITMQ_ prefix.
Prefixed version works just by an accident (as we've seen with
CTL_ERL_ARGS, where prefixed version is just ignored).
Change-Id: Ideb6967749efa8ba615cd5ab24df630d2ac526fc
The naming issue with k8s configmaps keys
already fixed: https://review.openstack.org/#/c/418946/
So, we can revert the file name back to oslo_messaging
Change-Id: I5224f93a605594a41b527ab0f549bd39545931f5
The k8s 1.5 does not support the _ in names of keys
of ConfigMaps, so the 'oslo_messaging' is invalid.
But in the same moment we cant use the "-" as
separator because the file name is used due
to importing in jinja2 like:
import 'oslo-messaging.j2' as oslo-messaging
the "oslo-messaging" is invalid jinja variable.
So, currently the only way is didn't use any
separator: "oslomessaging".
Change-Id: I5594db296d745fe57b13ea3d2cd38be1e74d4d10
Add config options to declare by default
rabbitmq as RPC and Notifications backend.
These options will be used to generate
backend-related configs of oslo messaging
and specify dependency.
Change-Id: Ib110af1b9d4feef9085a46518f629e27e8094611
With this change one will be able to set custom RabbitMQ repository and
its key, as well as specify custom autocluster location (latter seems ugly,
but unfortunately no repository for autocluster yet).
Change-Id: Ib3d6536d8c9fe8b8d7c5d13d4481772b66cc9db0
`etcd` is used as a backend for `autocluster`.
Co-Authored-By: Kirill Proskurin <kproskurin@mirantis.com>
Change-Id: I98bde66da4be517fb9e4442906620fae536d4f37
Do apt clean and /var/lib/rabbitmq state purge at
install stage
Change-Id: Ibdb3d30f2d7e92a7524778a719b5c9603072aaad
Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>
Jinja vars will be added later, since build tool is not ready yet.
Proper cluster implementation already done for mesos and will be re-wrote
for k8s as all needed tools are ready.
Change-Id: I392ffbed9b2947d09b696d613c523dd68c0a2c0d