On Mon, 5 Sept 2022 at 03:13, Matthias Runge <mrunge@xxxxxxxxxxxxxxxxx> wrote:
On 02/09/2022 22:10, Stephen Smoogen wrote:
> This lowered the long term load average but now led to reports where the
> mailman REST daemon does not respond in time due to timeouts. Looking at
> what is going on in the logs, and reading through the forums, my guess
> was these are issues due to the old django and early mailman we are using.
>
> At this point I started to look at what would be needed to update
> mailman to a newer version which could be supported on Fedora or RHEL9.
> The main issues are setting up the django "project" and then making sure
> that the needed packages are available. The upstream 'recommended' ways
> are to use either venv or containers but I found that the solutions are
> for a) docker, b) have a lot of security vulnerabilities in the quay
> listing and c) using it looks like Debian/Ubuntu packages. There is also
> a lot of customization needed to the point it might be best to start
> from scratch on that.
>
> I am thinking it might make better sense to work out a project and
> layout in staging, get a copy of the database from db01 and try
> experiments to make it work until we either burn it all down or not.
>
I'd be curious on the django version and release issues. The way the
project is working (regular releases, release often,...) and getting
long term support does not really work well with a community-based
approach ("the community will keep the version alive", "do backports",
etc) with epel packages.
While there is a bug https://bugzilla.redhat.com/show_bug.cgi?id=2033064
to get django in EPEL, I'm not sure how much this would help you here?
Would be hosting on Fedora an alternative?
That is possible in one of the following scenarios:
1. We install into a VM and do major updates every 6 months to the next Fedora release. I think that this is more doable now than it has been in the past.
2. We make a set of containers via Fedora which can be run in openshift. Similar set of spin up and move every couple of months. There are very out of date quay.io and docker.io ones which might work as a template to start with.
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
