Test new Fedora Planet
by Pedro Moura
Hello everyone,
I would like to inform you that the new Fedora Planet has been deployed on
the OCP (OpenShift Container Platform) and is now running on the following
sites:
- Production: https://planet.apps.ocp.fedoraproject.org/
- Staging: https://planet.apps.ocp.stg.fedoraproject.org/
The application has been containerized, and we have migrated the feed
reader from Venus to Pluto. Now, it just needs users to input their blogs
into their accounts on Fedora Accounts <https://accounts.fedoraproject.org/>.
This information will be used to build Fedora Planet at specific intervals
using cron.
We plan to announce the new application and give users some time to add
their blogs to their accounts.fedoraproject.org accounts. After that, we
will set a date to retire the old planet and move the new application to
fedoraplanet.org.
So, we'd like to invite all of you to test the new Fedora Planet at the
provided links above to identify any potential issues before we finalize
the transition.
Regards,
Pedro Moura
he/him/his
Software Engineer
Red Hat <https://www.redhat.com>
pmoura(a)redhat.com
<https://www.redhat.com>
3 weeks, 3 days
new sigul rolled out
by Kevin Fenzi
Hey folks.
Just a heads up that I have migrated sigul to the new 1.2 version with
rhel9 vault/bridge.
Please let me know if you see any signing issues in the coming days.
It seems to be processing as expected, so hopefully everything will be
transparent to everyone, and look for some nice improvements to
hopefully be enabled in coming weeks.
See:
https://pagure.io/fedora-infrastructure/issue/11505
for more info.
kevin
1 month
Re: Deleting old AMIs in AWS
by Miroslav Suchý
Dne 04. 04. 24 v 4:06 dop. Dusty Mabe napsal(a):
> If you don't mind let me try to get the FedoraGroup tag added to our CoreOS AMIs first.
>
> I'll try to set up something to get that done this week.
Sure. I pause any deletion till end of the current freeze (scheduled to 2024-04-16).
--
Miroslav Suchy, RHCA
Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys
1 month
Meeting Agenda Item: Introduction Paul Maconi
by Paul Maconi
Hello everyone! My name is Paul Maconi, aka @aggraxis on matrix, across
the FAS, and a bunch of other places. I attended the meeting earlier
today. Thank you again for the warm welcome.
I'm currently employed by a defense contractor providing support in the
US. I lead the contractor team supporting the customer organization,
and I serve as one of the senior architects for their test enclaves.
We work with RHEL (7, 8, and 9) as well as Windows and a little bit of
Ubuntu. I have experience working with NetApp storage arrays and VMware
virtualization products in the workplace. At home I have a small lab
where I just converted everything over to Proxmox as an educational/
fun exercise.
I'm not a strong programmer. I took C, C++, and Java in college some
20+ years ago, but I couldn't see myself making that kind of
professional life for myself at the time. I did find an interest in
Python after I started experimenting with Ansible in the workplace. I
*love* writing Ansible playbooks, and running through a bunch of the
self-paced materials over at pybit.es was a lot of fun for me. So I
know enough Python to be dangerous, but I can't write you the next gee
whiz application from scratch. I have a working knowledge of Powershell
as well, but I'm hoping we won't need that here.
I currently hold a CompTIA Advanced Security Practitioner (CASP+)
certification, mostly because my job requires it. I spend a lot of time
assessing and remediating security controls as part of my work life,
which is the initial driver for learning Ansible at the time.
I also spent 7 years working as a Cisco Certified Network Administrator
(CCNA) back in the early 2000s, so I do have a background slinging
packets.
Honestly, I'm just a computer nerd who grew up to be a computer nerd.
I love learning things and solving problems. I will say that I was a
little intimidated at first by the outstanding issues. Even some of
the Eaxyfix items looked kind of wild from the newcomer point of view.
Still, I'm excited for the opportunity to come learn, grow, and create
with you all.
1 month
Fedora 40 Final Freeze now in effect!
by Kevin Fenzi
Greetings.
we are now in the infrastructure freeze leading up to the Fedora 40
Final release. This is a final release freeze.
We do this to ensure that our infrastructure is stable and ready to
release Fedora 40 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:
git clone
https://infrastructure.fedoraproject.org/infra/ansible.git
ansible/scripts/freezelist -i inventory
Any hosts listed as freezes is frozen until 2024-04-16 (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 and/or a pull-request to the infra/ansible repo.
Thanks,
kevin
1 month, 1 week
Freeze break request: add zabbix_agent role to logger systems
by David Kirwan
Hi all.
I want to add the Zabbix agent to the systems in the ansible group:
`logger`. Requesting a freeze break, to make this change and then run the
playbook: `groups/logserver.yml`
Its not urgent, so if you'd prefer to wait till after freeze thats ok!
cheers,
David
--
David Kirwan
Senior Software Engineer
Community Platform Engineering @ Red Hat
T: +(353) 86-8624108
1 month, 1 week
Freeze break request: proxy update to point badges.fp.o at Openshift
by Aurélien Bompard
Hey folks,
With Ryan we have deployed the refreshed badges stack in prod openshift,
as the badges components are not frozen. However, the proxies are, and
we need to update them to point at openshift instead of VMs.
I'll run the proxies playbook with the "-t badges" argument, that should
only update the badges pieces.
WDYT?
A.
1 month, 1 week
Freeze break request: koji update on builders
by Kevin Fenzi
In the run up to f40 final we were using a koji with a patch to _not_
enable the builroot repo when making containers via kiwi plugin.
This was to fix the fact that pulling from the buildroot repo pulls
unsigned rpms, making all the rpms installed in the container unsigned.
Foolishly, I pulled a newer/expansion of that patch from upstream in in
the last round of updates, but something in it's defaults/logic causes
it to not disable the buildroot repo, and again containers have unsigned
rpms. ;(
So, what I would like to do is go back to the previous patch we had that
just has the 'only enable buildroot when no repos are passed' patch.
Ideally we would do this today so the last f40 nightly would be right.
If not tho, we could land it anytime and then the nightly container
builds would be fixed.
Can I get +1s for this plan?
Thanks,
kevin
1 month, 1 week
Freeze break request: update koji package on builders
by Kevin Fenzi
When I did the updates before final freeze, I missed updating the
builders with the latest koji package from the f39-infra tag.
At the time for some reason I thought it didn't matter, because the
patches were all hub related, but turns out thats not the case.
2 of the patches affect builders:
* One adding --debug to kiwi builds so we can see whats going on.
* One changing it so kiwi build tasks don't use the koji buildroot for
packages. When they do this they get unsigned packages and it shows up
in the containers made with kiwi.
So, I'd like to update all the builders to the latest f39-infra koji
package with these patches and restart kojid on them.
+1s?
kevin
1 month, 3 weeks
