The new messaging infrastructure uses AMQP (see issue #7107). As part of the migration plan, bridges from ZMQ to AMQP and AMQP back to ZMQ need to be run so consumers and producers on both sides see all messages. Additionally, a service has been written to compare messages from both AMQP and ZMQ to ensure the bridges are working properly.
All these services can run under a single OpenShift project called "messaging-bridges".
When do you need this? (YYYY/MM/DD) The sooner the better, but preferably before 2018/09/07.
When is this no longer needed or useful? (YYYY/MM/DD) Hopefully never.
If we cannot complete your request, what is the impact? We won't be able to proceed with the migration to AMQP.
@abompard and @jcline will be involved in the deployment and maintenance of the resource, abompard on the longer term. If at all possible, I would like to have admin privileges (write access) to the project directly. I promise everything will get checked into Ansible.
Security officer: @puiterwijk
Phase I
amqp_to_zmq
zmq_to_amqp
verify
Phase II
Phase III
Phase IV
Only sysadmin-main members can be RFR sponsors.
Metadata Update from @mizdebsk: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: request-for-resources
I'd be happy to sponsor this.
Will work with jcline to get it going...
Metadata Update from @kevin: - Issue assigned to kevin
Hey folks, I have pushed the ansible role in the repo, can I have the permission to run rbac-playbook openshift-apps/messaging-bridges.yml please?
rbac-playbook openshift-apps/messaging-bridges.yml
I actually already set this up for 'sysadmin-web' since messaging goes accross a wide crosssection of apps, but you were not in that group.
Now you are. :)
So, this is all deployed now I think... but we need a few things to close it off:
SOP on any actions or whatever we might need to do.
Monitoring?
@jcline @abompard See items in last comment... can we get SOP (if any needed) and monitoring (if any needed) closed out?
I'm afraid this is all up to @abompard as I've got too much on my plate at the moment for this. Since it is supposed to be a short-lived service (how many things aren't ported to AMQP yet?) I'm not sure how valuable either one would be when the developer of both could spend the time porting stuff so the bridge can be removed.
Sure. We do still have things needing porting. :)
Anyhow, @abompard if you think a SOP or monitoring would be good here, can you do that? If not, I guess we should just close this?
Yeah, I agree with jcline, I don't think SOP & monitoring are useful since it's a transition service.
Metadata Update from @abompard: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.