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.
I'm David Lefever, 35 years old, from Braine-le-comte in Belgium.
I have an 8-year-old boy and 5-year-old daughter.
My IRC handle is ledvd.
I'm a software engineer, started as Java developer, then Python (I'm
more of a backend guy, but I like ReactJS), but I always liked the infra
side as well so the last few years I naturally evolved to DevOps.
I worked on logging and monitoring using ELK and Kafka, CI/CD pipelines
(Jenkins and GitLab-CI mainly), automation (Ansible, Terraform, ...), ...
I enjoy Kubernetes (and work with OpenShift), and I use a lot of Helm,
some ArgoCD, Flux.
I like to have the big picture, and help improving the Software
Development Life Cycle and value stream using data (metrics).
I like to think of myself as a constant learner. I never really
contributed yet to OSS, but I'd like to start.
I read the GettingStarted page, and I think now I'll keep an eye open to
see what is happening here and at one point try to contribute in some way.
Have a nice day !