Hello.

Please add next new clients to RabbitMQ:

RabbitMQ client name:

osci-pipelines

At this moment we have access to RabbitMQ client with name centos-ci. Strictly speaking that credentials was given by centos team only for testing purposes. While centos-ci client can be used by centos team, it is better to have distinct users, that we do not collide.

In certificate requests they have: Subject: CN = osci-pipelines

Please create next RabbitMQ queues with name and allow access to them for osci-pipelines :

osci-pipelines-queue-0
osci-pipelines-queue-1
osci-pipelines-queue-2
osci-pipelines-queue-3
osci-pipelines-queue-4
osci-pipelines-queue-5
osci-pipelines-queue-6
osci-pipelines-queue-7
osci-pipelines-queue-8
osci-pipelines-queue-9
osci-pipelines-queue-10
osci-pipelines-queue-11
osci-pipelines-queue-12
osci-pipelines-queue-13
osci-pipelines-queue-14
osci-pipelines-queue-15

Q: Why so many?
A: Background: https://pagure.io/fedora-infrastructure/issue/8846
According to this discussion 1 client can listen to many queues.
1 queue can be subscribed to different topics.
We have at least 4 pipelines: standard-test-interface/installability/rpmdeplint/composes/more-to-come.
All these pipelines listen to the same topics.
While we want to keep:

simple logic
and make pipelines independent
ability to run simultaneously at different places (AWS/Communshift)

All of them need to listen to topics that have common set. For 4 pipelines we need already 8 queues + 2 for experimenting/future needs.

Turned out there is policy:

- name: Validate parameters
  assert:
    that:
    - "queue_name.startswith(username)"
    fail_msg: "Your queue name must be prefixed with your username"

I created a certificate requests for client. I will attach certificate to this tickets.

When do you need this to be done by? (YYYY/MM/DD)

This would help us to allow deploy pipelines.

Thank you.