So you're look for the certs?

You can follow https://pagure.io/fedora-infra/howtos/blob/master/f/fedora_messaging_certificates.md and create them yourself, maybe using centos-odcs as service name?

So you're look for the certs?

More than certs, it seems like ODCS needs private queue on which ODCS frontend and backend talks to each other.

@kevin did the setup for Fedora ODCS deployment a while back - https://pagure.io/fedora-infra/ansible/c/c67b7dd2776c56974df115a0d368950308edc646

I have no idea about it and I also dont know how we can do the delegate_to part as CentOS infra might not know about rabbitmq fedora boxes.

So you're look for the certs?

More than certs, it seems like ODCS needs private queue on which ODCS frontend and backend talks to each other.

@kevin did the setup for Fedora ODCS deployment a while back - https://pagure.io/fedora-infra/ansible/c/c67b7dd2776c56974df115a0d368950308edc646

I have no idea about it and I also dont know how we can do the delegate_to part as CentOS infra might not know about rabbitmq fedora boxes.

We already have some users and queues being created in our ansible for things
used in the CentOS infra (for example
https://pagure.io/fedora-infra/ansible/pull-request/302 ), maybe we could do the
same here

So, our side should be all done here right? Can we close this @mohanboddu ? Or do you want to make sure it works after deploying the centos side?

I'm going to assume this is working as I see the queues and they have consumers. ;)

Please re-open if there's anything more to do...