#3931 Get fedmsg messages in from secondary arch koji instances
Closed: Fixed None Opened 10 years ago by ralph.

Are we getting koji fedmsg messages published for secondary arch builds? I'm not sure we are.

If we are, then we can close this ticket.

If we aren't, then we should figure out what it will take to add them and do it up.

FWIW, the koji fedmsg plugin is kept in puppet.

This ticket was created in response to a request from the badges tracker - https://fedorahosted.org/fedora-badges/ticket/8


currently we are not. none of the secondary arch hubs are in puppet.

ausil tells me that the koji hubs for s390 and arm are on the same machines that run the compose process. ppc has a separate box.

For s390 and arm, this is a good thing. The iptables rules are already set up to allow incoming fedmsg traffic from those boxes.

We'll need to create a hacked version of the koji fedmsg plugin that knows to phone home to infrastructure instead of binding passively on a port like we having the main one doing inside infra. We should create a separate pair of certs for these boxes too so they don't share/re-use the compose certs.

ppc will take more work than that.. not sure exactly what yet.

regarding the status change from new to assigned:

Does this mean that fedmsg might be enabled for the s390 and ppc koji in the near future ?
I really would like to see that so that I could more easily monitor the rebuild process and react faster on critical build failures.

Karsten (Secondary arch maintainer ppc and s390)

karsten, can you provide links to the two koji instances?

So, s390 has the hub and composer on the same machine. To get fedmsg
messages from there we just need to:

  • Copy the plugin to /usr/lib/koji-hub-plugins/fedmsg-koji-plugin.py
    We have the plugin in puppet/configs/build/fedmsg-koji-plugin.py
    I can send it to you if you do not have access to our puppet setup.
  • Tweak the second to last line of the plugin so that it reads
    {{{ body['instance'] = 's390' }}}
  • Enable it by setting {{{ Plugins = fedmsg-koji-plugin }}} in hub.conf

For ppc, I understand that the hub is on a different machine. We'll
need to do the above steps for that machine, but also:

  • Install fedmsg
  • Copy all of /etc/fedmsg.d/ from the ppc composer to the ppc hub
  • Copy all of /etc/pki/fedmsg/ from the ppc composer to the ppc hub

I don't think I can do any of the above steps myself as I don't have access to any of those compose machines.

But, lastly I will need to:

  • Tweak an iptables entry on our infrastructure proxies to allow
    incoming connections from the ppc hub's external IP.

Once this is all set up, you should be able to test from the ppc hub
by issuing {{{ echo 'testing (YOUR_USERNAME)' | fedmsg-logger --cert-prefix bodhi }}}
and then checking to see if that message shows up in #fedora-fedmsg on
freenode.

Finally, two questions:

  • What are the external URLs of the ppc and s390 hubs? I'll need them
    to update the code that generates links back to builds and tasks for
    fedmsg messages.
  • What is the external IP of the ppc hub machine? I'll need it for
    that iptables setting.

The ppc hub URL is http://ppc.koji.fedoraproject.org/koji/ , its external IP is 209.132.181.21. (Inside of PHX it's ppc-hub.qa.fedoraproject.org)

The ppc hub is publishing messages now. Still need to get the s390 hub done.

the s390 hub URL is ​http://s390.koji.fedoraproject.org/koji/ and external IP is 209.132.181.18

s390 and ppc kojis are sending messages now.

Login to comment on this ticket.

Metadata