#8213
fedmsg -> fedora-messaging migration tracker

Opened a month ago
by kevin.
Modified 9 hours ago

We should track and finish moving everything from fedmsg to fedora-messaging.

We have at least:

releng/scripts/fedmsg-functions.sh (used by branched/rawhide composes)

roles/nagios_server/files/nagios/commands/notify.cfg (used by nagios)

and all the following playbooks still calling fedmsg/base:

playbooks/groups/autocloud-backend.yml: - fedmsg/base playbooks/groups/autocloud-web.yml: - fedmsg/base playbooks/groups/badges-backend.yml: - fedmsg/base playbooks/groups/badges-web.yml: - fedmsg/base playbooks/groups/bugyou.yml: - fedmsg/base playbooks/groups/bugzilla2fedmsg.yml: - fedmsg/base playbooks/groups/busgateway.yml: - fedmsg/base playbooks/groups/datagrepper.yml: - fedmsg/base playbooks/groups/elections.yml: - fedmsg/base playbooks/groups/fas.yml: - fedmsg/base playbooks/groups/fedimg.yml: - fedmsg/base playbooks/groups/fedocal.yml: - fedmsg/base playbooks/groups/freshmaker.yml: - fedmsg/base playbooks/groups/github2fedmsg.yml: - fedmsg/base playbooks/groups/hubs.yml: - fedmsg/base playbooks/groups/kerneltest.yml: - fedmsg/base playbooks/groups/koji-hub.yml: - fedmsg/base playbooks/groups/koschei-backend.yml: - fedmsg/base playbooks/groups/loopabull.yml: - fedmsg/base playbooks/groups/mailman.yml: - fedmsg/base playbooks/groups/mbs.yml: - fedmsg/base playbooks/groups/mdapi.yml: - fedmsg/base playbooks/groups/mirrormanager.yml: - fedmsg/base playbooks/groups/modernpaste.yml: - fedmsg/base playbooks/groups/noc.yml: - fedmsg/base playbooks/groups/notifs-backend.yml: - fedmsg/base playbooks/groups/notifs-web.yml: - fedmsg/base playbooks/groups/nuancier.yml: - fedmsg/base playbooks/groups/odcs.yml: - fedmsg/base playbooks/groups/odcs.yml: - role: fedmsg/base playbooks/groups/openqa.yml: - { role: fedmsg/base, tags: ['fedmsg_base', 'fedmsg'] } playbooks/groups/packages.yml: - fedmsg/base playbooks/groups/pdc.yml: - fedmsg/base playbooks/groups/pdc.yml: - fedmsg/base playbooks/groups/people.yml: - fedmsg/base playbooks/groups/pkgs.yml: - fedmsg/base playbooks/groups/releng-compose.yml: - fedmsg/base playbooks/groups/resultsdb.yml: - { role: fedmsg/base, playbooks/groups/retrace.yml:# - fedmsg/base playbooks/groups/sundries.yml: - role: fedmsg/base playbooks/groups/taskotron.yml: - { role: fedmsg/base } playbooks/groups/value.yml: - fedmsg/base playbooks/groups/wiki.yml: - fedmsg/base playbooks/groups/zanata2fedmsg.yml: - fedmsg/base playbooks/hosts/happinesspackets-stg.fedorainfracloud.org.yml: - fedmsg/base playbooks/hosts/happinesspackets.fedorainfracloud.org.yml: - fedmsg/base

Login to comment on this ticket.

Koschei migration from fedmsg to fedora-messaging in production is planned on 2019-09-26. Staging instance already uses fedora-messaging, eg. this message (

`"username": "amqp-bridge"`

)@karsten you were going to look at the infrastructure scripts moving right? Could you perhaps focus on/start with planet? It seems to somehow be broken right now, and I can't seem to figure out why. Moving it to fedora-messaging would hopefully fix it and get us a bit further along too at the same time. :)

It runs on people02.fedoraproject.org... the venus-planet package will need adjusting I guess: https://koji.fedoraproject.org/koji/buildinfo?buildID=942792

Or if thats not your cup o tea, we can look for someone else. :)

Also, we need a plan for notifs.

I thought that we already ported this to fedora-messaging.

As taskotron is in maintenance mode, I'm not really keen on putting time into porting the one sub-component which still uses fedmsg to fedora-messaging unless there's no other option

We did, this is likely just a clean up that we didn't do :(

Same for elections, koji-hub and pkgs I think.

Also Ansible callback plugins need to be ported:

Metadata Update from @cverna:- Issue tagged with: backlog

Metadata Update from @kevin:- Issue assigned to karsten

I'm dropping the following from the list:

autocloud retires with f29:

playbooks/groups/autocloud-backend.yml: - fedmsg/base

playbooks/groups/autocloud-web.yml: - fedmsg/base

we are giving away badges:

playbooks/groups/badges-backend.yml: - fedmsg/base

playbooks/groups/badges-web.yml: - fedmsg/base

bugyou never took off/should be retired now.

playbooks/groups/bugyou.yml: - fedmsg/base

elections we are giving away:

playbooks/groups/elections.yml: - fedmsg/base

fedocal we are giving away:

playbooks/groups/fedocal.yml: - fedmsg/base

hubs is gone.

playbooks/groups/hubs.yml: - fedmsg/base

going away:

playbooks/groups/modernpaste.yml: - fedmsg/base

playbooks/groups/nuancier.yml: - fedmsg/base

done:

playbooks/groups/koji-hub.yml: - fedmsg/base

playbooks/groups/pkgs.yml: - fedmsg/base

playbooks/groups/koschei-backend.yml: - fedmsg/base

playbooks/groups/openqa.yml: - { role: fedmsg/base, tags: ['fedmsg_base', 'fedmsg'] }

playbooks/groups/resultsdb.yml: - { role: fedmsg/base,

Unknown????????????

playbooks/groups/fedimg.yml: - fedmsg/base

playbooks/groups/freshmaker.yml: - fedmsg/base

That leaves:

playbooks/groups/bugzilla2fedmsg.yml: - fedmsg/base

playbooks/groups/busgateway.yml: - fedmsg/base

playbooks/groups/datagrepper.yml: - fedmsg/base

playbooks/groups/fas.yml: - fedmsg/base

playbooks/groups/github2fedmsg.yml: - fedmsg/base

playbooks/groups/kerneltest.yml: - fedmsg/base

playbooks/groups/loopabull.yml: - fedmsg/base

playbooks/groups/mailman.yml: - fedmsg/base

playbooks/groups/mbs.yml: - fedmsg/base

playbooks/groups/mdapi.yml: - fedmsg/base

playbooks/groups/mirrormanager.yml: - fedmsg/base

playbooks/groups/noc.yml: - fedmsg/base

playbooks/groups/notifs-backend.yml: - fedmsg/base

playbooks/groups/notifs-web.yml: - fedmsg/base

playbooks/groups/odcs.yml: - fedmsg/base

playbooks/groups/odcs.yml: - role: fedmsg/base

playbooks/groups/packages.yml: - fedmsg/base

playbooks/groups/pdc.yml: - fedmsg/base

playbooks/groups/pdc.yml: - fedmsg/base

playbooks/groups/people.yml: - fedmsg/base

playbooks/groups/releng-compose.yml: - fedmsg/base

playbooks/groups/retrace.yml:# - fedmsg/base

playbooks/groups/sundries.yml: - role: fedmsg/base

playbooks/groups/taskotron.yml: - { role: fedmsg/base }

playbooks/groups/value.yml: - fedmsg/base

playbooks/groups/wiki.yml: - fedmsg/base

playbooks/groups/zanata2fedmsg.yml: - fedmsg/base

ansible callbacks

Being ported by @abompard

going away (sooner or later :()

Being handed over to Jeremy

Ported to fedora-messaging upstream, we can migrate when we want

I think @cverna was saying yesterday that this no longer works, and thus we should be able to remove it.

Is there any sense of what should be prioritized higher in this list? Just curious for some expert opinion @kevin @pingou

There are a few angles and I don't think any good answer to this question:

Some that we could look at porting today would be:

Once these are done we'll likely ran into the more complex ones.