I'd like to set up one staging and one prod VM for zanata2fedmsg.
The purpose of the service is to accept HTTP POSTs from zanata.fedora.org webhooks and to re-publish them on to our fedmsg bus.
Architecturally, it is similar to github2fedmsg, but is simpler. Where github2fedmsg has a self-service UI and a db that maps what projects should have the hook installed, zanata2fedmsg will have no database at all and a single simple flask endpoint.
No need for backups, as there will be no db. All configuration will be managed in ansible.
We will need a python script (not yet written) which will log in to the fedora.zanata.org interface (or API) and ensure that our webhook is installed correctly on all of the existing projects. We should run this script as a cron job once a day.
Note that the zanata2fedmsg app is up for package review currently.
It currently verifies the signature of the zanata server by validating a HMAC secret in the url. That will be replaced (shortly) by validation of an HMAC secret in the X-Zanata-Webhook header: https://github.com/fedora-infra/zanata2fedmsg/blob/develop/zanata2fedmsg.py#L55-L61
I'll sponsor my own ticket, if that is acceptable. I filed it here so we have something we can track later down the line (at puiterwijk's request per devconf conversations).
Status update: I'm partway through setting this up. The hosts are provisioned, but I need to work out all of the app configuration and monitoring still.
Status update: The app is "up" in stg. I've revised the webhook validation code upstream and will cut a new release with that before going to prod. Before I do that, I'm going to write the cronjob which will scan fedora.zanata.org for new projects and install our webhook there. I've only just begun to stub that out here: https://github.com/fedora-infra/zanata2fedmsg/blob/develop/zanata2fedmsg-sync.py
Hows this looking? Production soon?
@ralph Where is this RFR? Looks like we still need to finish pushing it to production?
Yes, it's up in staging: https://apps.stg.fedoraproject.org/zanata2fedmsg but not yet prod.
The last, kinda complicated part is that we have to write a script that goes through all of the projects in https://fedora.zanata.org and installs the webhook to ping back to https://apps.fedoraproject.org/zanata2fedmsg/webhook/<project_name>.
https://apps.fedoraproject.org/zanata2fedmsg/webhook/<project_name>
Yes, it's up in staging: https://apps.stg.fedoraproject.org/zanata2fedmsg but not yet prod. The last, kinda complicated part is that we have to write a script that goes through all of the projects in https://fedora.zanata.org and installs the webhook to ping back to https://apps.fedoraproject.org/zanata2fedmsg/webhook/<project_name>.
Does it mean that for new projects, maintainer or Zanata admin will have a add it manually for each new project ? Or will this script be automatically run at periodic time ?
I am not sure if @aeng is already in CC for this ticket, hence just trying to get his attention here.
@pnemade Thanks for letting me know. The webhook settings will be on per project based. The initial idea was to get tier 1 project setup and trial. The webhook will feed into the message queue for whichever system that will consume it (Fedora hub). I will provision the configuration when I got the details for the message bus url and key.
It's been a year now, whats the status here?
@ralph can you still drive this forward to prod?
Any status here? We are waiting for the hooks before moving to prod?
Metadata Update from @kevin: - Issue priority set to: Waiting on External
Metadata Update from @kevin: - Issue priority set to: Next Meeting (was: Waiting on External)
I missed your ping 8 months ago, @kevin... but I can't drive this one forwards anymore. :(
Current status: https://github.com/fedora-infra/zanata2fedmsg/issues/1#issuecomment-392697199
Metadata Update from @kevin: - Issue assigned to puiterwijk - Issue priority set to: Waiting on Assignee (was: Next Meeting)
So we aren't using fedmsg anymore. and I am not sure if the translation work is still going this way anymore. Is it time to close this out?
Indeed, you can close this issue=2E Thanks for asking
Metadata Update from @smooge: - Issue close_status updated to: Will Not/Can Not fix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.