#6553 Add the registry to status.fpo
Closed: Fixed 2 years ago Opened 2 years ago by bowlofeggs.

I noticed today that we don't have an entry for the container registry (registry.fpo) on our status.fpo page. It'd be good to add one.


It might be good to reorg it at the same time. I suggest into 3 groups/sections:

at the top:

services end users directly interact with: mirrorlists, websites, ask, paste, ipsilon, docs

next:

service that developers/contributors interact with

at the bottom:

anything else (although consider dropping it).

Metadata Update from @kevin:
- Issue priority set to: Waiting on Asignee

2 years ago

Metadata Update from @kevin:
- Issue tagged with: easyfix

2 years ago

Which repository is actual for status.fpo?

Docs referer to pagure, but it is not getting any commits for a year already https://pagure.io/fedora-status/commits/

There is Github repo that is updated for statuses https://github.com/fedora-infra/statusfpo but docs are silent about it. What version should be used?

The pagure one is the upstream, and the github one is our live copy of it. You should be able to just send it to the Github one, unless you're making changes to the actual scripts that generate the site.

Is anyone working on this ticket? It seems like the original request would call for the service to be added to statusfpo/wsgi/statuses.json file something like;

     "registry": {
            "message": "Everything seems to be working.",
            "name": "Fedora Container Registry",
            "status": "good",
            "url": "https://registry.fedoraproject.org/"
},

@kevin - you suggested splitting this into sections for End Users, Devs, Everything Else. Is something like this what you had in mind?

Users

  • Fedora Wiki
  • Fedora People
  • Zodbot IRC bot
  • Fedora pastebin service
  • ipsilon
  • Mirror List
  • Badges
  • Account System
  • Fedora Websites
  • Ask Fedora
  • COPR Build System
  • Fedora elections
  • Mailing Lists
  • FreeMedia?

Devs

  • Koji Builds
  • Darkserver
  • Tagger
  • BlockerBugs
  • MirrorManager
  • Koschei CI
  • Fedora Infra Cloud
  • Pagure
  • Pkg Maintainers Git Repos
  • Fedora Packages App
  • Fedora Messaging Bus
  • Fedora Calendar
  • Kerberos

???
- FedoraHosted.org

Is anyone working on this ticket? It seems like the original request would call for the service to be added to statusfpo/wsgi/statuses.json file something like;
"registry": {
"message": "Everything seems to be working.",
"name": "Fedora Container Registry",
"status": "good",
"url": "https://registry.fedoraproject.org/"
},

I don't know, but if so, they can chime in.

@kevin - you suggested splitting this into sections for End Users, Devs, Everything Else. Is something like this what you had in mind?

Well, that was a while back, I think now it might make sense to split them by SLE (service level expectation). Those docs @smooge is going to land soon. But we can do that later once they have landed.

Also note: ask fedora, freemedia, darkserver, and fedora hosted can all be removed now.

So, if you want to submit a PR to the github repo adding the registery and removing those above we could just do that now and sort this later.

PR submitted to gh repo . If someone can assign this ticket to me, I will follow the PR and update status.

Metadata Update from @kevin:
- Issue assigned to aikidouke

2 years ago

PR merged - will ask someone to run the status script

After merging PR generate.py script crashes because some services were removed:

$ python generate.py rss ../generated/changes.rss
Traceback (most recent call last):
  File "generate.py", line 120, in <module>
    generated = minify(generateFeed('rss'), args.no_minify)
  File "generate.py", line 80, in generateFeed
    return generateFeedPage(feedtype + '.html', getInfo('changes.json'), getInfo('statuses.json'))
  File "generate.py", line 54, in generateFeedPage
    change['serviceNames'].append(statuses['services'][srv]['name'])
KeyError: u'ask'

@aikidouke Can you fix this?

Yep - looking at it now.

I've cleaned change history as @puiterwijk suggested and pushed the change to AWS.

Metadata Update from @mizdebsk:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata