This removes (almost) all the Nagios config for Rabbit, including the
templates in the Rabbit role(s).
It leaves the nagios user, because Zabbix is also using it.
It also adds a Matrix-level notification for high queues, above the one
that goes to the UI.
Signed-off-by: Greg Sutcliffe <fedora@emeraldreverie.org>
This was useful when we had clusters in iad2 and rdu3, but it didn't
actually quite work then and it definitely doesn't now. :)
Datacenters like 'aws' do not have their own clusters, they use the one
in rdu3. So, just switch it back to hard coding.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This will unify all the handlers to use first uppercase letter for
ansible-lint to stop complaining.
I went through all `notify:` occurrences and fixed them by running
```
set TEXT "text_to_replace"; set REPLACEMENT "replacement_text"; git grep
-rlz "$TEXT" . | xargs -0 sed -i "s/$TEXT/$REPLACEMENT/g"
```
Then I went through all the changes and removed the ones that wasn't
expected to be changed.
Fixes https://pagure.io/fedora-infrastructure/issue/12391
Signed-off-by: Michal Konecny <mkonecny@redhat.com>
ansible-lint requires that variables for roles are prefixed with the
name of the role. This commit prefixes the variables for the
rabbit/user role with user_ as required by ansible-lint
Signed-off-by: Ryan Lerch <rlerch@redhat.com>
Only a few apps have topic permissions, if this works well we'll have to
generalize it.
Fixes: #8167
Signed-off-by: Aurélien Bompard <aurelien@bompard.org>
The osci queue's have changed since this playbook last completed.
The ttl changed and the routing keys have changed.
The ansible rabbitmq module can't change these things on already created
queues because the api doesn't allow it. This makes this playbook fail
with:
"RabbitMQ RESTAPI doesn't support attribute changes for existing
queues"
So, for now, set the ttl to what it already is, and don't change the
routing keys at all. Hopefully this will get it to complete and osci can
manage at least routing keys themseleves wherever they do that.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
When creating a queue, the user is automatically created, but
there is no control over what queues the user can write to. A
user might need to write to queues other than ones prefixed with
their name (e.g. some users need to write to 'ci.*' queues).
This makes it possible to specify additional custom prefixes of
queues the user will be permitted to write to.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
