planet
by Kevin Fenzi
Hey folks. I thought I would open a discussion about fedoraplanet and
possibly some plans for it.
Right now:
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
break.
We have two open tickets on it:
- https://pagure.io/fedora-infrastructure/issue/10383 (upgrade to pluto,
a ruby based, but maintained thing)
- https://pagure.io/fedora-infrastructure/issue/10490
( 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
or unrelated.
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. :)
kevin
7 months, 3 weeks
About JS framework
by Pierre-Yves Chibon
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,
Pierre
1 year, 1 month
RHEL9 migration
by Kevin Fenzi
Here's my thoughts on rhel9 upgrades.
We have 188 RHEL7 or RHEL8 instances (counting both vm's and bare hardware).
Some of them I think we can reinstall anytime:
backup01.iad2.fedoraproject.org
batcave13.iad2.fedoraproject.org
cloud-noc-os01.rdu-cc.fedoraproject.org
dl01.iad2.fedoraproject.org
dl02.iad2.fedoraproject.org
dl03.iad2.fedoraproject.org
dl04.iad2.fedoraproject.org
dl05.iad2.fedoraproject.org
download-ib01.fedoraproject.org
download-rdu-cc01.fedoraproject.org
dedicationsolutions01.iad2.fedoraproject.org
ibiblio01.iad2.fedoraproject.org
ibiblio05.iad2.fedoraproject.org
memcached01.iad2.fedoraproject.org
noc01.iad2.fedoraproject.org
noc02.fedoraproject.org
ns01.iad2.fedoraproject.org
ns02.iad2.fedoraproject.org
ns02.fedoraproject.org
ns13.rdu2.fedoraproject.org
osuosl01.fedoraproject.org
secondary01.iad2.fedoraproject.org
smtp-mm-ib01.fedoraproject.org
smtp-mm-osuosl01.fedoraproject.org
smtp-mm-cc-rdu01.fedoraproject.org
storinator01.rdu-cc.fedoraproject.org
sundries01.iad2.fedoraproject.org
sundries02.iad2.fedoraproject.org
tang01.iad2.fedoraproject.org
tang02.iad2.fedoraproject.org
torrent02.fedoraproject.org
unbound-cc-rdu01.fedoraproject.org
unbound-cc-rdu01.fedoraproject.org
Some of them we can do, but we will need an outage for them:
bastion01.iad2.fedoraproject.org
bastion02.iad2.fedoraproject.org
bastion13.iad2.fedoraproject.org
people02.fedoraproject.org
db01.iad2.fedoraproject.org
db03.iad2.fedoraproject.org
db-datanommer.iad2.fedoraproject.org
db-koji.iad2.fedoraproject.org
db-openq.iad2.fedoraproject.org
(we can see how long the upgrade takes in stg on the various db servers)
Some of them need applications/packages built for rhel9 and we can't do them until
that is sorted out:
badges (hopefully now ongoing?)
notifs (ongoing)
mm- (is mirrormanager2 ready to branch/build for rhel9?)
pagure (how about pagure?)
pkgs (also need pagure)
sign (needs the new sigul. I'll ping patrick about it again)
value* - needs limnoria in epel9 and fedmsg-irc replacement somehow. The zodbot part perhaps could be moved to openshift.
Some we need to carefully save local data and restore after reinstall:
batcave01.iad2.fedoraproject.org
log01.iad2.fedoraproject.org
The vmhosts need some investigation to see if we can reinstall and keep the
vm data around. Otherwise we need to migrate vm's off and back on.
I tried this in a early 9.0 install and it didn't seem to work on the host
I was testing with, but should try again.
qvmhost
bvmhost
vmhost*
Some, we need to talk about:
db-fas01 - this used to have the fas db on it to be more secure (seperate from db01),
now all it has is the ipsilon db. I guess we could rename it db-ipsilon01?
or fold it into db01?
ipa - I think, but want to confirm we can just reinstall one replica with rhel9, get it
all synced and then do another and another until the entire cluster is rhel9.
rabbitmq - currently we are using rhel8 + openstack 16 repo. I suppose we can just go to
rhel9 + openstack 17 repo.
Some will just not move anytime soon:
busgateway - needs fedmsg, only in epel7
fedimg - needs fedmsg. will be replaced by some other solution
github2fedmsg - needs fedmsg, only in epel7
mailman01 - needs fedmsg
nuancer - needs fedmsg
osbs - needs new container build system
pdc - needs to be retired
Finally, some I am not sure about and would like input:
mbs - is this ready for rhel9? Should we move to Fedora instead?
odcs - how about this?
So, as far as help goes, getting mirrormanager2 and pagure all in epel9 would be great...
coming up with a fedmsg-irc replacement, and getting limnoria in epel9 seem to be the best ways right now.
I can start on the easier reinstalls.
kevin
1 year, 2 months
Planned Outage - networking work - 2022-09-26 21:00 UTC and
2022-09-27 21:00 UTC
by Kevin Fenzi
There will be an outage starting at 2022-09-26/2022-09-27 21:00 UTC,
which will last approximately 4 hours on 2022-09-26 and 5 hours on 2022-09-27.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2022-09-26 21:00UTC'
date -d '2022-09-27 21:00UTC'
Reason for outage:
On 2022-09-26 internet edge routers and switches will be upgraded. During this time period various
Fedora services will be down as switches and routers are rebooted.
On 2022-09-27 1gb internal switches will be upgraded. a 30min outage is likely during this time period.
Affected Services:
All services at the IAD2 datacenter
Ticket Link:
https://pagure.io/fedora-infrastructure/issue/10915
Please join #fedora-admin or #fedora-noc on irc.libera.chat
or add comments to the ticket for this outage above.
1 year, 2 months
Meeting Agenda Item: Introduction Erol Keskin
by Erol Keskin
Hi Dear Fedora Folks,
My name is Erol Keskin. I'm 25 years old and i'm from Istanbul / Turkiye.
Some of you folks might recognize me from projects such as anitya,
fedora-messaging or noggin. I've been trying my best to contribute to
fedora-infrastructure projects on a weekly basis for about 3 months. To
this day, I've worked with languages such as Golang, Python, C#, C, NodeJS.
I guess I could say that I have good knowledge about Docker, Podman,
Kubernetes in containers generally. Besides all of that, I've been a long
time user of Linux systems. I've been using them for about 10 years to this
point. I should say that I've been using Fedora Linux for about 1 year till
now, but in my opinion I can say that this is the best distribution that
can be imagined. Because of my general workflow on Linux machines, i'm used
to do Bash Scripting.
To be honest, I do love working on fedora-infrastructure projects. I'm
very interested in working on these projects, and I would love to be a part
of this great team! I can get to use this on-edge reliable distribution
thanks to many contributors behind it, i can't wait to be a one of them.
I want to improve myself in topics Zuul and Ansible. I think this is a
great place to work on those skills.
I hope you all have a great day.
GitHub Handle: https://github.com/erolkskn
My IRC handle on Libera: erolkskn
1 year, 2 months
