A lot of fedora services use fedmsg, which is a depreciating messaging service. Fedora-messaging schemas will be replacing current fedmsg ones in applications and adding schemas to apps & services that have none but would benefit from this work. Once all apps have been updated with fedora-messaging schemas, we can being to retire fedmsg.
This initiative is really important for maintainers and downstream users of Fedora services to be able to consume messages and stay up to date with work as currently some apps do not have the capability to receive a readable description of why a message was sent, so problems/issues are harder to diagnose.
All applications in the Fedora infrastructure that use fedmsg have fedora-messaging schemas added. All applications that have no schemas have fedora-messaging schemas added. All applications now using fedora-messaging schemas can send and receive messages Update documentation on how the messaging system works with fedora-messaging so maintainers can understand how to write and receive messages for their application(s) Consumers can receive messages in readable format
What is the minimal outcome you would like to see from this initiative to be satisfied? All of the above
What are your nice or really nice to have wishes?
All Fedora users
All Fedora applications & services that rely on fedmsg need to be updated. There may be some downtime associated with this update on some services. This work is also a prerequisite for actioning the retiring of fedmsg
People who are familiar with Fedora application stack & current messaging service
Other work that should be completed prior to this initiative? No
As soon as possible
Is this initiative under a time-constraint? Should it start or end before a certain date? It should start before FMN replacement/retiring of fedmsg work begins
Link to github board currently created for this work https://github.com/orgs/fedora-infra/projects/7
Metadata Update from @amoloney: - Issue untagged with: In Review - Issue tagged with: Accepted
Issue tagged with: To be scoped
Metadata Update from @amoloney: - Issue untagged with: 2021Q1, To be scoped - Issue tagged with: Ready for QP
Issue tagged with: 2021Q2
Metadata Update from @amoloney: - Issue untagged with: To be scoped
Metadata Update from @amoloney: - Issue set to the milestone: Fedora Messaging Overhaul
Metadata Update from @amoloney: - Issue status updated to: Closed (was: Open)
Issue status updated to: Open (was: Closed)
Metadata Update from @amoloney: - Issue untagged with: 2021Q2, Accepted, Ready for QP - Issue tagged with: Needs More Info
Issue tagged with: Accepted
This projects scope has been absorbed by the larger FMN project: ARC Investigation report https://fedora-arc.readthedocs.io/en/latest/fmn/index.html FMN Project Board https://github.com/fedora-infra/fmn
Moving to In Progress
Marking this as done as most apps that required schemas to interact with the new FMN service has them implemented. Schema template can be found here for self-service implementation https://github.com/fedora-infra/cookiecutter-message-schemas
Log in to comment on this ticket.