fedora-infra / statusfpo Goto Github PK

Pelican only generates category feeds if articles exist. The JSONGenerator class in the json_output filter works around that, but not for RSS feeds.

All of the RSS links here …:

	<link href="/ongoing.rss" type="application/rss+xml" rel="alternate" title="Fedora Infrastructure Status ongoing outages RSS Feed" />
	<link href="/planned.rss" type="application/rss+xml" rel="alternate" title="Fedora Infrastructure Status planned outages RSS Feed" />
	<link href="/resolved.rss" type="application/rss+xml" rel="alternate" title="Fedora Infrastructure Status resolved outages RSS Feed" />
	<link href="/changes.rss" type="application/rss+xml" rel="alternate" title="Fedora Infrastructure Status all outages RSS Feed" />

… return content rendered in JSON:

nils@makake:~> for category in ongoing planned resolved changes; do
    echo -n "$category: "
    curl --silent "https://status.fedoraproject.org/${category}.rss" | file -
done
ongoing: /dev/stdin: JSON text data
planned: /dev/stdin: JSON text data
resolved: /dev/stdin: JSON text data
changes: /dev/stdin: JSON text data
nils@makake:~>

The fedmenu project is not really maintained anymore and will be soon archived. We should remove fedmenu from this application.
https://github.com/fedora-infra/statusfpo/search?q=fedmenu&unscoped_q=fedmenu

Should this repo move to https://pagure.io/fedora-status ?

https://pagure.io/fedora-infrastructure/issue/6553#comment-509776

If no ticket is defined in the text file, the status app gives an empty ticket number and a bare link to the issues page.

The links that show up in RSS (e.g. on Fedora Planet) when outages are added result in an S3 permission error when someone tries to view them. For example https://status.fedoraproject.org/20210824-network-issues.html results in

<Error>
  <Code>AccessDenied</Code>
  <Message>Access Denied</Message>
  <RequestId>KR2NGKHBW89TJJCS</RequestId>
  <HostId>7CICEjmrOavdw7gd2J9t61CqKyRCDW4jQbeGIt/hce25TMxt7dLv7olcZEfom0gvOY5biueYgJI=</HostId>
</Error>

Am I right that https://status.fedoraproject.org/ is a web site with no automatic checks to test the malfunctioning of the services? In other words, there is no monitoring for Fedora services that is reflected here?

Currently if there are no upcoming outages, the status states "0 Upcoming Outage" -- we should make it read "0 Upcoming Outages".

Additionally, The blue "primary" header is also a little bright and bold for when there are no upcoming outages -- it would probably work better to be grey when there are 0 upcoming outages.

Currently, the status page isn't responsive at all.

If you want, I can make a PR ?

Currently, we sort planned outages with the most recent date first, for example:

• 1 June 2021
• 5 May 2021

we should reverse this order, so the planned outage that is going to occur first is at the top of the list.,