Turn anitya cron job to service

[Zlopez]

Current cron job used by Anitya is not very reliable.

So it will be better to turn it into service probably using twisted library. This will make scheduling much easier and we could also add the ability to send e-mail when things are failing.

Here is the list of the features it should have:

• easy scheduling
• notification about high fail rate (probably through e-mail)

[cheese1]

just curious: why is it not possible to send mails from cron or because of a failing cron?

[Zlopez]

This is probably possible, I just didn't yet look into this option yet.

[abitrolly]

Does it make sense to change it to systemd job first?

[Zlopez]

No, because the systemd units aren't working in containers and the release-monitoring.org is managed in OpenShift.

[abitrolly]

In development environment anitya is a systemd service. It becomes a container in OpenShift? Then there is no logs, no auto-restart unless there is something like Kubernetes managing the lifecycle.

[Zlopez]

@abitrolly
In development the Anitya is only user systemd unit. In OpenShift it is container that is build, deployed and managed by OpenShift. It has auto-restart feature, so if running instance is down, it will try to start it again.
This is the same behavior I want to see with this cron job.

[abitrolly]

Does it provide logs, error counter and error messages?

[Zlopez]

The logs will be handled the same way as they are now. Saved to the database. Error counter must be implemented, error messages are saved to every project even now as update log.

[Zlopez]

Otherwise the log of the container is accessible in OpenShift, I can look at it there.

[TomasTomecek]

Did you consider celery?

@abitrolly OpenShift is Kubernetes.

[Zlopez]

@TomasTomecek Didn't heard about it. I will give it a try.

[TomasTomecek]

Pagure is using celery to manage tasks.

[Zlopez]

I looked at it and it's not really usable for Anitya. It needs a broker, which is not necessary in our case, because we have all the information internally available in our current database.