I would like to reserve a fedora-messaging queue identifier for the DistroBuildSync tool so that if it crashes and remains down for an extended period, we can still resume the automatic builds. DistroBuildSync will be used to rebuild ELN from Rawhide, replacing the slow and crash-prone Jenkins implementation (as well as addressing side-tag builds for ELN).
The requested queue name is distrobuildsync-eln.
distrobuildsync-eln
2021/09/17
Additionally, while we're at it, can we also reserve distrobuildsync-eln-extras for future use?
distrobuildsync-eln-extras
FYI, This requires a FBR, can you let us know how urgent it is, can it wait until beta freeze is lifted?
Metadata Update from @mohanboddu: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-gain, low-trouble, ops
Typically we make things use their username for the cert name and the queue name so it all just matches up...
so, should we make the user just distrobuildsync-eln and get you a cert named that too?
That seems sensible to me. Thanks!
Metadata Update from @kevin: - Issue tagged with: unfreeze
Any progress on this?
Can we also get a Kerberos keytab for distrobuildsync-eln@FEDORAPROJECT.ORG (and have the user set up however bpeck/jenkins-continuous-infra.apps.ci.centos.org is set up today?
distrobuildsync-eln@FEDORAPROJECT.ORG
bpeck/jenkins-continuous-infra.apps.ci.centos.org
I was going to work on this after freeze.
2 questions (sorry for not asking sooner):
Do you want just one user (distrobuildsync-eln) that has access to both distrobuildsync-eln and distrobuildsync-eln-next queues? Or seperate distrobuildsync-eln-next user using the distrobuildsync-eln-next queue?
Do either of these queue's have routing keys? ie, subset of messages that they care about?
Oh, and if you want a keytab (or two if we do seperate users) I need you to say you will be entirely responsible for any actions taken with that keytab and will keep it safe and secure. :)
2 questions (sorry for not asking sooner): Do you want just one user (distrobuildsync-eln) that has access to both distrobuildsync-eln and distrobuildsync-eln-next queues? Or seperate distrobuildsync-eln-next user using the distrobuildsync-eln-next queue?
Just one user should be fine.
routing_keys = ["#.buildsys.repo.done", "#.buildsys.tag"]
Well, I was going to post it on my blog, but since you asked so nicely, yes we will keep it secure. Please send it to me via GPG encrypted mail, using my 850A9DD1DBF2ACCC6FC4949145DB85A568286D11 public key (you can retrieve it from the key servers with sgallagh@redhat(dot)com .
ok.
I have created the users and queues. I have put the certs for prod (did you want stg?) into your homedir on batcave01. I have created a keytab for that service and put that also in your homedir on batcave01.
The rabbitmq playbook is running now, should be done in a few. :)
Please let us know if you need anything further or if there's any problems...
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.