infrastructure
/
meta
7
0
Issues 51 Pull Requests Projects 5 Releases Activity

[Infrastructure]: Investigate a brand new MQ system #70

New Issue
Open
opened 2024-03-27 00:43:04 +00:00 by label · 1 comment
label commented 2024-03-27 00:43:04 +00:00
Owner
Copy Link

Current RabbitMQ infrastructure is dedicated to Module Build Service for Rocky Linux 8. We would like a dedicated queue for Rocky Linux and other projects.

Ideally, we would like projects and consumers outside of the RESF (such as end users) to be able to subscribe/monitor to the queues. Projects should also have the ability to send messages to the bus. There should also be an available frontend, like datagrepper that can show historic messages ingested from something like datanommer.

Checklist

To be filled.

Current RabbitMQ infrastructure is dedicated to Module Build Service for Rocky Linux 8. We would like a dedicated queue for Rocky Linux and other projects. Ideally, we would like projects and consumers outside of the RESF (such as end users) to be able to subscribe/monitor to the queues. Projects should also have the ability to send messages to the bus. There should also be an available frontend, like [datagrepper](https://github.com/fedora-infra/datagrepper) that can show historic messages ingested from something like [datanommer](https://github.com/fedora-infra/datanommer/). ## Checklist To be filled. <!-- If applicable, put a checklist here. Otherwise, remove this section. -->
label added the
needinfo
enhancement
task
priority
medium
 labels 2024-03-27 00:43:04 +00:00
label added this to the RESF Infrastructure Automation Modernization project 2024-03-27 15:23:14 +00:00
label added this to the RabbitMQ Cluster(s) Running milestone 2024-03-27 15:23:54 +00:00
label added the
gain
high
effort
high
 labels 2024-03-27 18:24:32 +00:00
label commented 2024-04-02 19:04:59 +00:00
Author
Owner
Copy Link

bc747aa564
a3c96b897c
47573d1181

https://git.resf.org/infrastructure/ansible-ops-management/commit/bc747aa564537027a340d29903a0eecd1a1a1bb0 https://git.resf.org/infrastructure/ansible-ops-management/commit/a3c96b897c8ac2b28b5f643d620ed84b27d94f14 https://git.resf.org/infrastructure/ansible-ops-management/commit/47573d11816362cb017839c36f5c608da1b4865a
Sign in to join this conversation.
main
Branches Tags
Clear current reference
main
Clear current reference
Labels
Clear labels   
bug

Something is not working

  
component/ansible

   
component/git

   
component/idm

   
component/mattermost

   
component/mirrors

   
duplicate

This issue or pull request already exists

  
effort
high

  
effort
low

  
effort
medium

  
enhancement

New feature

  
gain
high

  
gain
low

  
gain
medium

  
help wanted

Need some help

  
invalid

Something is wrong

  
issue

   
needinfo

More information is needed

  
permissions
  
priority
high

  
priority
low

  
priority
medium

  
task

   
wontfix

This won't be fixed

No Label
bug
component/ansible
component/git
component/idm
component/mattermost
component/mirrors
duplicate
effort
high
effort
low
effort
medium
enhancement
gain
high
gain
low
gain
medium
help wanted
invalid
issue
needinfo
permissions
priority
high
priority
low
priority
medium
task
wontfix
Milestone
Clear milestone
No items
No Milestone
RabbitMQ Cluster(s) Running
Projects
Clear projects
No project
RESF Infrastructure Automation Modernization
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: infrastructure/meta#70
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?