#6441: need a way to send messages to a stg messagebus
------------------------------+-----------------------
Reporter: lkocman | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 25 Alpha | Component: other
Resolution: | Keywords:
Blocked By: | Blocking:
------------------------------+-----------------------
Comment (by ralph):
OK, lkocman told me:
1) they *do* need messages from
modularity.fedorainfracloud.org to be
received on composer.stg
2) they *do* need messages from composer.stg to be received on
modularity.fedorainfracloud.org
Here's my recommendation:
For the first part,
1) we run a fedmsg-relay on
modularity.fedorainfracloud.org port 4001.
This effectively gives it its own "bus", kind of like debian's bus.
2) we then add an entry to the endpoints.py file for composer.stg only so
that it subscribes to this "external" bus, and will get messages from
there.
3) they won't be signed, so we'll need to also disable message signature
validation on composer.stg
4) that should do it.
on the second part
1) pungi running on composer.stg needs to sign and send messages, so I'll
create a new cert, just for this dev work, only in staging, and have the
key owned by the modularity-wg group.
2) that will allow dev users on the box to sign messages as their own
users without having to have any sudo rights.
3) those messages from pungi on composer.stg will make it onto the stg-
wide stg bus and will be published externally at
tcp://stg.fedoraproject.org:9940, signed with valid (for staging) certs.
4) whatever needs to listen to that, can listen to that.
--
Ticket URL: <
https://fedorahosted.org/rel-eng/ticket/6441#comment:3>
Fedora Release Engineering <
http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project