fedora-infrastructure

#12998 redirect languages.fedoraproject.org to communityhealth.languages-in-floss.eu
Closed: Fixed by zlopez. Opened by jibecfed.

Closed: Fixed
Reopen Issue

the website https://languages.fedoraproject.org is broken for one or two years
same for https://languages.stg.fedoraproject.org

Infrastructure is hosted by https://console-openshift-console.apps.ocp.fedoraproject.org/ and https://console-openshift-console.apps.ocp.stg.fedoraproject.org
Infrastructure code is in https://pagure.io/fedora-infra/ansible/blob/main/f/roles/openshift-apps/languages

the way to produce these statistics is changing, and not stable enough to worth the effort to fix the ansible/openshift pipelines.

I improved the scripts and published an up to date content there: https://communityhealth.languages-in-floss.eu

could you please:

  • redirect https://languages.fedoraproject.org requests to https://communityhealth.languages-in-floss.eu
  • redirect https://languages.stg.fedoraproject.org requests to https://communityhealth.languages-in-floss.eu
  • deactivate (or remove) the automation in ansible and openshift clusters?

once the code is more stable, I'll open a new ticket to request some help to put it back to Fedora infrastructure.
In the meanwhile, it'll runs on my computer

Metadata Update from @james:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: low-gain, low-trouble

Might be worth pinging someone in matrix if this is till open after mid. Jan.

Metadata Update from @zlopez:
- Issue assigned to zlopez

I implemented the redirect in https://pagure.io/fedora-infra/ansible/pull-request/3018, https://pagure.io/fedora-infra/ansible/pull-request/3019 and I'm running proxies playbook right now, but I'm not sure if that will fix the reverse proxy part. Will check that tomorrow.

Also do we want to delete the openshift project as well? It doesn't make much sense to keep it if the redirection is in place.

What I know: the whole processing is evolving (commands changed, filesystem organization too, output is the same, containers and database are coming

if there is no items to reuse in the future (I have no knowledge in openshift), I assume deleting it is fine

The redirect is now in place. The config file wasn't removed by ansible playbook as it didn't know about it anymore. So I did that manually today.

Metadata Update from @zlopez:
- Issue tagged with: sprint-0

It may be useful to keep around the ansible setup for the old app to help us when we redeploy. We could perhaps just set it to scale to 0 in the playbook for now so it doesn't use any resources?

In that case, let's just scale it to 0 and close the ticket.

Set the replica to 0 and suspended the cronjobs. Closing this as fixed. @jibecfed feel free to re-open it if something isn't working as expected.

Metadata Update from @zlopez:
- Issue untagged with: sprint-0
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata

low-gain low-trouble

None
None
Normal
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.