Hey folks. I thought I would open a discussion about fedoraplanet and
possibly some plans for it.
fedoraplanet.org runs on people02.fedoraproject.org (aka fedorapeople).
To add a blog/rss feed you have to login there and edit your .planet
file, then scripting pulls all those .planet files and tries to fetch
all the feeds and then serves them up at http://fedoraplanet.org.
It uses a app called 'venus' to do this. venus is written in very old
python2 and very very dead upstream.
We run into the following problems with it:
* Sometimes it gets stuck and just stops processing until it's killed.
* It's serving on a http site, which causes people to ask us to make it
https, but that would just change the errors because many feeds it pulls
are still http since they were added back before letsencrypt existed.
* We have a handy 'website' field in our new account system, but aren't
using it at all.
* The .planet parsing is poor, any number of things can cause it to
We have two open tickets on it:
- https://pagure.io/fedora-infrastructure/issue/10383 (upgrade to pluto,
a ruby based, but maintained thing)
( planet not served via ssl) Which I am just going to close now.
So, I can think of a number of options and would love everyone who has
thoughts on it to chime in:
1. Do nothing. Venus "works" and .planet files are cool and retro.
2. Switch to pluto and use account system 'website' fields of
contributors. We could likely shove it in openshift and serve it
directly from there to avoid fedorapeople entirely.
(This would likely break anyone who has multiple feeds in there)
3. Switch to something better/bigger. I would think (although I don't
know) that there might be something that would not only aggregate rss
feeds for contributors, but perhaps mastodon/twitter/whatever also.
4. Planets are old and tired, just drop the entire thing. People can
maintain their own rss lists.
5. Planets are old and tired, just drop the entire thing.
But also, get our social media people to maintain contributor /
interesting lists. ie, the fedoraproject twitter account could maintain
a list of 'fedora contributors' and 'fedora packagers' or whatever.
6. Switch to pluto as in 2, but also setup some curators. Have a
'firehose' of all feeds, but the main fedora planet would be just
curated things that are known to be related to fedora and not off topic
6. Get someones (not it!) to take in all the
twitter/facebook/mastodon/blog posts/rss feeds and post some kind of
curated round up every week or something.
7. Your brilliant idea here!
So, thoughts? this is not at all urgent, but we should end up doing
something with it sometime. :)
we are now in the infrastructure freeze leading up to the Fedora 37
Final release. This is a final release freeze.
We do this to ensure that our infrastructure is stable and ready to
release Fedora 37 when it's available.
You can see a list of hosts that do not freeze by checking out the
ansible repo and running the freezelist script:
ansible/scripts/freezelist -i inventory
Any hosts listed as freezes is frozen until 2022-10-18 (or later if
release slips). Frozen hosts should have no changes made to them without
a sign-off on the change from at least 2 sysadmin-main or rel-eng
members, along with (in most cases) a patch of the exact change to be
made to this list.
So, yesterday we managed to get the python3 version of fmn working in
staging seemingly well, so I stupidly decided to try and migrate
production to it. This has been fraught with peril. ;(
First, only the notifs-backend01 ip is allowed to reach out to IRC, so
after saving off the notifs-backend01 (python2) fmn disk and vm xml I
tried to get notifs-backend02 to use 01's ip. That works, but made
things like IPA mad, since the hostname/ip was mismatched.
So, I just redeployed a new notifs-backend01 with the python3 version.
Sadly, the IRC part which we hadn't been able to test in staging, wasn't
working right at all. So, I went back to the old notifs-backend01.
Unfortunately, that vm is now not processing correctly either.
(Even though it's the same exact VM that was there before). :(
With help from pingou, we cleaned up some errors, but it's still not
seeming to be sending out things. It may be that it's just loading
caches and such and will start working here soon.
So, here's my plan:
* Leave the current python2 one alone for a while and hope it starts
processing things again.
* Later in the day, I am going to save off the current python2 backend01
(again) and deploy the python3 one (again).
Hopefully that gets at least emails flowing again.
* pingou is going to look at it when he gets in in the morning tomorrow
and fix issues.
Hopefully that will result in a working python3 FMN. ;(
Since we are going into freeze this morning, I'm going to treat this
work as "it's an outage, fix it" and not worry about the freeze for it.
So, sorry for the lack of notifications last night and today,
I wish things had gone smoother.
Good Morning Everyone,
Our infrastructure is mostly a python store, meaning almost all our apps are
written in python and most using wsgi.
However in python we are using a number of framework:
* flask for most
* pyramid for some of the biggest (bodhi, FAS3)
* Django (askbot, Hyperkitty)
* TurboGears2 (fedora-packages)
* aiohttp (python3, async app: mdapi)
While this makes sometime things difficult, these are fairly standard framework
and most of our developers are able to help on all.
However, as I see us starting to look at JS for some of our apps (fedora-hubs,
wartaa...), I wonder if we could start the discussion early about the different
framework and eventually see if we can unify around one.
This would also allow those of us not familiar with any JS framework to look at
the recommended one instead of picking one up semi-randomly.
So has anyone experience with one or more JS framework? Do you have one that
would you recommend? Why?
Thanks for your inputs,
I am a systems administrator at Google, and long term Fedora user. I want to become involved with Fedora, and it seems like this is the correct place to start. I look forward to attending IRC meetings -- my IRC username is astrognome.
I've been reading through the documentation, and have checked out the fedora-infrastructure git repo. I would like to commit to at least 10-hours a week of volunteer time.
I have experience with Ansible, Puppet, Chef, Python, Nagios, Terraform, Jenkins, Docker, k8s.
What I would like to learn: Two things really, a) how to contribute to an open source project, and b) gain more experience with CI/CD pipelines.
Sent with Proton Mail secure email.